You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing different Linux display drivers I noticed that the legacy framebuffer one was working, but the DRM/KMS got stuck and didn't render anything besides the initial screen.
Issue seems to be the lv_tick_set_cb call being present on the legacy framebuffer option, but not on the DRM/KMS one.
Issue is not present if that call is done by the user.
For consistency both should have the tick call, or maybe neither..?
How to reproduce?
No response
The text was updated successfully, but these errors were encountered:
kisvegabor
added a commit
to kisvegabor/lvgl_upstream
that referenced
this issue
May 30, 2024
LVGL version
v9.1.0-182
What happened?
When testing different Linux display drivers I noticed that the legacy framebuffer one was working, but the DRM/KMS got stuck and didn't render anything besides the initial screen.
Issue seems to be the
lv_tick_set_cb
call being present on the legacy framebuffer option, but not on the DRM/KMS one.Issue is not present if that call is done by the user.
For consistency both should have the tick call, or maybe neither..?
How to reproduce?
No response
The text was updated successfully, but these errors were encountered: