Full resolution display support #7
Closed
Conversation
This file contains 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
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 adds full resolution support, by holding the back buffer in PSRAM.
As part of this, I've switched display update to be handled by copying back buffer to display buffer instead of flipping. This allows for the back buffer to be in the slower PSRAM, and also makes use of PicoGraphics more intuitive (works like all other display products, instead of like PicoVision). This also allows partial update.
This is a draft, primarily as it depends on changes to the PSRAM setup in Micropython (see separate PR), but also it doesn't quite fit - need to determine what variables we can safely move to psram_data. There's also some corresponding changes to pimoroni-pico, currently living on https://github.com/MichaelBell/pimoroni-pico/tree/mike-dev