8000 Update README.md · wired8/lv_binding_micropython@f5b509d · GitHub
[go: up one dir, main page]

Skip to content

Commit f5b509d

Browse files
authored
Update README.md
1 parent 9c591da commit f5b509d

File tree

1 file changed

+11
-1
lines changed

1 file changed

+11
-1
lines changed

README.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,17 @@ Currently supported drivers for Micropyton are
193193
Driver code is under `/driver` directory.
194194

195195
Drivers can also be implemented in pure Micropython, by providing callbacks (`disp_drv.flush_cb`, `indev_drv.read_cb` etc.)
196-
Currently the supported ILI9341, FT6X36 and XPT2046 are pure micropython drivers
196+
Currently the supported ILI9341, FT6X36 and XPT2046 are pure micropython drivers.
197+
198+
### Where are the drivers?
199+
200+
LVGL C drivers and Micropython drivers (either C or Python) are **separate and independent** from each other.
201+
The main reason is configuration:
202+
- The C driver is usually configured with C macros (which pins it uses, frequency, etc.)
203+
Any configuration change requires rebuilding the firmware but that's understandable since any change in the application requires rebuilding the firmware anyway.
204+
- In Micropython the driver is built once with Micropython firmware (if it's a C driver) or not built at all (if it's pure Python driver). On runtime the user initializes the driver and configures it. If the user switches SPI pins or some other configuration, there is no need to rebuild the firmware, just change the Python script and initialize the driver differently **on runtime**.
205+
206+
So the location for Micropython drivers is https://github.com/lvgl/lv_binding_micropython/tree/master/driver and is unrelated to https://github.com/lvgl/lv_drivers.
197207

198208
### The Event Loop
199209

0 commit comments

Comments
 (0)
0