Jump to content
IGNORED

Text Minikernel


Karl G
 Share

Recommended Posts

Could you add some information about the "free" variables you used in the DPC+ kernel to the first post? Explaining the trade off could save a dev some headaches later.

 

 

DPC+ is desperately low on vars; many devs are going to see the memory map and grab those two extra variables.

Link to comment
Share on other sites

Documentation has been updated, and the Multisprite kernel example has been updated to no longer include a patched multisprite_kernel.asm file. This was needed due to a bug in the Multisprite kernel which has since been corrected in newer bB releases.

 

No code changes otherwise in this update, so no need to update to the latest version if you are already using this.

  • Thanks 1
Link to comment
Share on other sites

3 hours ago, Gemintronic said:

I thought I saw that you posted about having your own score related code in there (5 digit score topic).

 

Does this effect people who use modied score_graphics.asm?  I know I needed to modify that to include A-F and something else for RevEngs multi kernel framework.

My duplicate score code is the 6-digit routine that is normally part of the kernel (standard kernel, multisprite, or DPC+). The score_graphics.asm code is not affected, and you can use that version. I actually include a version of RevEng's score_graphics.asm modified to add a "squish" score font (less scanlines used to save CPU cycles).

  • Thanks 1
Link to comment
Share on other sites

  • 8 months later...

I was thinking if it is possible to remove all lowercase letters, and force all parameters so that the kernel does not have to check them, such as: forcing it to always not show the score, to always have a fixed text color, removing all handling for the extend text mode, and so on, in such way that the kernel could become smaller and use less cycles?

 

Maybe a minimalist version of this minikernel (for the standard kernel), where everything except the basic features are stripped ?

 

Edited by rfunes
Fixed typo
Link to comment
Share on other sites

My implementation does not use any lowercase letters - just capital letters, numbers, and some punctuation characters. Removing options and features will not reduce the cycles used by this or any other mini kernel, at any rate. That is a function of how many lines the minikernel displays. Mini kernels extend the visible screen, taking some processing time away from the overscan area where bB code runs. The text minikernel displays more lines than most, and unfortunately there is no way to avoid this. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...