Optimize buffer layout #264
Open
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
This commit puts the framebuffer management in specific framebuffer files. The framebuffer is now written to in a way optimised for sending it. It also adds support for bit-banding if macro CONFIG_BIT_BANDING is defined. Framebuffer is also not passed as an argument to display functions anymore.
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 pull-request puts the framebuffer management in specific framebuffer files. The framebuffer is now written to in a way that can be optimised for sending it. It also adds support for bit-banding if macro CONFIG_BIT_BANDING is defined. Framebuffer is also not passed as an argument to display functions anymore.
This feature was added because I suspect an issue with Module17 (revision 1.0) in which I believe the screen processing might take too much time. This does fix the issue.