Carlos Diaz

I already have a branch with v8 support, it might be matter of making sure we follow the same naming convention. I will wait for @tore-espressif opinion.

Nice, should we support the latest LVGL v7 release on the v7 branch and track the latest v8 on the v8 branch? Should we have a branch per LVGL release...

Can we use tags for that? On the drivers repo I mean. Or maybe start soon and figure out what to do when we face that issue.

That's true, I didn't see that case. Should we create a new branch per release or just when we need a change?

I see, we can try that. For having the drivers in the lvgl repo i think we still need some time to mature it.

I don't know how many people depend on this repo, I think it's better to cleanup the code base as we go. A personal preference is move fast, maybe break...

Hi, You're right, the drivers code were developed without taking in consideration the `rotated` field. We're about to move the drivers code into its own repository. You can find it...

Hi @zladay, The initial work is already done on the [lv_port_esp32](https://github.com/lvgl/lv_port_esp32) repo, we will copy the lvgl_esp32_drivers directory into here, so users can use the drivers without needing to use...

I can upload the existing code here and you take over with your improvements, I'm sure there's a lot to be done with the existing code on the lv_port_esp32 display...

Hi, ~For start you can only show a label in the display, once it's working we can work on showing any of the lv_example demos.~ Maybe we can use your...