Enable _stage module and freeze stage library on the PyBadge #1790
Conversation
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
|
I'd rather not introduce a build variant. Why don't we just enable _stage? We have enough memory for stage and ugame. For MADCTL you can |
|
Sure, we can do that. |
deshipu
changed the title
|
I cleaned up this pull request, but it still requires #1778 for the python code to work. |
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 requires #1778
Add a variant of the pybadge board definition, that has the
_stagemodule enabled, and includes frozenstageandugamemodules, for running µGame games.Since the stage library doesn't allow rotating the screen in software, and uses RGB pixels (and not BGR), I had to modify the MADCTL register in the display initialization, in addition to adding all the required modules.