Adding Byte-Per-Pixel Memory model option to memlcd #10640
Merged
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
jturnsek
force-pushed
the
feature/memlcd_byte_per_pixel
branch
from
096ed63
to
a9fa6dc
Compare
jturnsek
force-pushed
the
feature/memlcd_byte_per_pixel
branch
from
a9fa6dc
to
cb0c803
Compare
xiaoxiang781216
approved these changes
Sep 16, 2023
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.
Summary
LVGL uses Byte-Per-Pixel Memory model for monochromatic displays. This option enables memlcd driver to be used with LVGL.
Impact
memlcd driver
Testing
LVGL with Sharp MEMLCD.