-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document the CBM kernal routines #83
Comments
What do we consider "good" existing reference material for the CBM kernal routines? Personally I have a couple of bookmarks I return to all the time: http://sta.c64.org/cbmdocs.html, most notably http://sta.c64.org/cbm64krnfunc.html Here's some more, courtesy of @JimmyDansbo : Maybe less useful on the x16: |
Is it just referring to kernel calls or in general? It's a bit discounted but I like: http://6502.org/tutorials/6502opcodes.html Also I've volunteered to take that 2nd bullet point. |
Just the kernal calls for now, other types of documentation or changes should get its own issue IMO (including the FP routines which already have their own separate chapter) |
Started work on task 2 via this PR: https://github.com/X16Community/x16-docs/pull/84/files |
I think for begginers, there should be the creation of examples of code using the kernal routines to further improve the teaching and learning of the 6502 assembler coding. This would be useful for the education sector in promoting future computer programmers. |
Sure, examples and tutorials are needed too, but this item is only about reference documentation. Let's talk about other kinds of documentation elsewhere. |
I'll update the task list soon as some work has been done :) |
Documentation for several kernal routines is missing / incomplete.
This issue is for the CBM kernal routines that the X16 inherited from the CBM/C64 kernal rom.
These are documented elsewhere on the internet, but should be documented here as well.
Note that the Floating Point routines are excluded from this as well, they already have their own page.
The text was updated successfully, but these errors were encountered: