TimJTi commented on PR #12733: URL: https://github.com/apache/nuttx/pull/12733#issuecomment-2241064040
Hi. If you look at the latest updates to the LVGL issue you linked to, you will see that I am 99% sure LVGL is rendering DIRECTLY to the framebuffer which, if I am right, is WRONG. I have implemented a variant (a link to my fork is in that issue) that uses LVGL Linux-type framebuffer code, with dedicated buffer(s) that lvgl can render to that are only flushed to the real hardware framebuffer via the flush callback - but it still has issues and I included a video of them. This suggests lvgl is calling a flush BEFORE it has completely finished rendering. If I am right with that, then it is also WRONG!! I have tried partial mode but, to be fair, not before I did the linux-style framebuffer driver. If the declaration of the buffer as PARTIAL rather than DIRECT is a trigger for lvgl to only call the flush after rendering is definitely complete, it would be useful to know, and I will try it when I get a moment. But, for now, LVGL V9 is broken when it comes to using a framebuffer rather than arch or board-specfic device driver. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
