-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LVGL Version #2461
Comments
maybe @XuNeo could help us here! @xiaoxiang781216 what should be the next approach for this case? |
is lvgl 9.2 released? |
Yes official release is ready :-) https://github.com/lvgl/lvgl/releases/tag/v9.2.0 |
Will add in lvgl/lvgl#6789 |
Okay lets wait for LVGL 9.2.1 release, verify it, and add to NuttX 12.7.0 release, so far testing on 12.7.0-RC0 failed see apache/nuttx#13825 and apache/nuttx#13839. |
Okay the LVGL |
Summary
NuttX Apps needs to be upgraded to the newly released V9.2 to solve framebuffer render issues.
Background
As discussed here the LVGL version "bundled" with NuttX apps (v9.1) has issues with what I perceive as its misuse of the NuttX framebuffer; it makes multiple partial renders direct to the framebuffer, resulting in visible artefacts. It is deemed OK as there are some architectures/boards where this is OK because it seems they natively have two framebuffers. But - to me - it is the exception not the rule.
V9.2 now auto-detects the presence of that second native framebuffer and if its not there creates its own render buffer. It works but is perhaps a bit arcane.
NB - there is no support for an LVGL partial render buffer in the LVGL NuttX framebuffer driver, so there will be two whole frame buffers present: the /dev/fb0 buffer and LVGLs render buffer.
Other
While investigating this I needed to work with other versions of LVGL and found the following.
1a. Enable Kconfig configuration of the wanted LVGL version. Not sure this works if you need to work with LVGL master as there will be no release archive that can be downloaded.
Discuss :-)
The text was updated successfully, but these errors were encountered: