Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
python-devicetree/ | 03-Apr-2024 | - | 10,239 | 7,238 | ||
README.txt | D | 03-Apr-2024 | 1.2 KiB | 33 | 24 | |
gen_defines.py | D | 03-Apr-2024 | 41.3 KiB | 1,104 | 626 | |
gen_driver_kconfig_dts.py | D | 03-Apr-2024 | 3 KiB | 102 | 63 | |
gen_dts_cmake.py | D | 03-Apr-2024 | 5.7 KiB | 170 | 102 |
README.txt
1This directory used to contain the edtlib.py and dtlib.py libraries 2and tests, alongside the gen_defines.py script that uses them for 3converting DTS to the C macros used by Zephyr. 4 5The libraries and tests have now been moved to the 'python-devicetree' 6subdirectory. 7 8We are now in the process of extracting edtlib and dtlib into a 9standalone source code library that we intend to share with other 10projects. 11 12Links related to the work making this standalone: 13 14 https://pypi.org/project/devicetree/ 15 https://python-devicetree.readthedocs.io/en/latest/ 16 https://github.com/zephyrproject-rtos/python-devicetree 17 18The 'python-devicetree' subdirectory you find here next to this 19README.txt matches the standalone python-devicetree repository linked 20above. 21 22For now, the 'main' copy will continue to be hosted here in the zephyr 23repository. We will mirror changes into the standalone repository as 24needed; you can just ignore it for now. 25 26Code in the zephyr repository which needs these libraries will import 27devicetree.edtlib from now on, but the code will continue to be found 28by manipulating sys.path for now. 29 30Eventually, as APIs stabilize, the python-devicetree code in this 31repository will disappear, and a standalone repository will be the 32'main' one. 33