embeddedt

There shouldn't be an `lv_conf.h` either.

Hmm, I wonder if the generator is choking on `lv_fs_cbfs_init()` not having `void` in the parameter area. @amirgon Do you see any other callback conventions that might be missed in...

Honestly, I would carry on and not worry about the check; the other MicroPython platforms are passing and we can always fix it at the end.

It's intended. We had a lot of links pointing to `latest` back in the v7 days, and if we changed that symlink to v8 it would confuse v7 users. However,...

> I find it very strange why these obvious warnings was not spotted by our CI. @embeddedt do you have any ideas? It seems we [compile with this warning disabled](https://github.com/lvgl/lvgl/blob/24893c37ae18618089eff8a9bf38f604ae23b96e/tests/CMakeLists.txt#L301).

Anyone on GitHub should have permission to open a PR to `master`. Are you going to https://github.com/lvgl/lvgl/pulls? 

Are you selecting your repository as the head repository? 

Do you all think it is worth adding functionality to LVGL to oversize the buffer slightly for buggy hardware like this? From what I can tell, if the buffer were...

Has GD officially explained the reasoning behind the two-pixel backup approach? I'd be fine with adding it if the errata were clearly documented, and we had a good enough workaround,...

In that case can the backup logic be wrapped in `#if defined(GD32F450)`, or are there prior chips to it which also have the issue?