Add support for reMarkable2 firmware 3.24+ with new framebuffer format (ABGR32) #27
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
- Detect firmware version from /etc/os-release - Handle ABGR32 pixel format for firmware 3.24+ - Handle new framebuffer and offset for 3.24+
Owner
|
Thank you for this PR. It looks good to me. Could you please fix the formatting, so the pipeline passes? |
Contributor
Author
|
Great to see it live! Thanks! |
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.
Overview
reMarkable2 3.24 update changed framebuffer format from gray16 to ABGR32
Fixes #25
Changes
Testing
New features
Thanks to the new framebuffer which handles color, now the screenshots are colorful!
With the
-c/--og-colorflag, also the highlighters are visibleExample output: