-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Demo for the OSAL #6049
Comments
Hi, Just to be sure I understand correctly: in a demo or example we should create a few mutexes and threads with printf-s to demonstrate that OS layer is working well. If so, I think it should be rather an example which could be also a good starting point for anyone using LVGL with an OS. (E.g. show that
Besides the example - as you have mentioned - there should be a test too at least for pthread, but I think it's simpler as we can write any complicated code. |
We need some feedback on this issue. Now we mark this as "stale" because there was no activity here for 14 days. Remove the "stale" label or comment else this will be closed in 7 days. |
Sorry for not responding. GitHub doesn't send notification about reactions and I didn't notice the 👍 We will work on it! |
Hey @kisvegabor 😃, no worries. Maybe I'll find some time to work on this :^) |
Adds a demo demonstrating the use of the OSAL. Resolves: lvgl#6049
Adds a demo demonstrating the use of the OSAL. Resolves: lvgl#6049
Adds a example demonstrating the use of the OSAL. Resolves: lvgl#6049
Adds a example demonstrating the use of the OSAL. Resolves: lvgl#6049
Adds a example demonstrating the use of the OSAL. Resolves: lvgl#6049
Adds a example demonstrating the use of the OSAL. Resolves: lvgl#6049
Problem to solve
During development of LVGL integrations one task with the new release is the support of the OSAL. It would be very useful to have tests of some sort that integrators could refer to to verify their implementation.
Success criteria
LVGL integrators have a convenient way of verifying their OSAL implementation
Solution outline
I would propose this to be a demo rather then a feature though, because there might be customer preferences as to what framework to use. A demo could be vendor neutral way to provide the results by using print statements and
LV_ASSERT
etc.Rabbit holes
None that I know of.
Testing
Running integrations tests (at least for a linux pthread osal) within the pipeline.
Teaching
Adding a note to the OS porting section and of course to the demos.
Considerations
No response
The text was updated successfully, but these errors were encountered: