console: store the cache after clearing a framebuffer - #271
Merged
Conversation
This fixes a screen corruption issue on the wiimote example, where adding a call to fatInitDefault() right at the beginning of main() causes the upper 1/4 of the screen to be dirty (mostly green). To reproduce this, one needs to have a USB drive connected, formatted with NTFS: - libdvm will try to initialize the drive - it will create a cache for it (128KB) - seeing that it's NTFS and that there's no driver for the NTFS format, it will destroy the disk - the memory associated with the disk is freed, and then reused for the framebuffer
mardy
force-pushed
the
invalidate-fb-cache
branch
from
August 28, 2026 15:40
75d23c4 to
e682eb2
Compare
mardy
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fixes a screen corruption issue on the wiimote example, where
adding a call to fatInitDefault() right at the beginning of main()
causes the upper 1/4 of the screen to be dirty (mostly green).
To reproduce this, one needs to have a USB drive connected, formatted
with NTFS:
it will destroy the disk
framebuffer