zephyr

History

Martí Bolívar ffa1515978 dtlib: fix issue which allowed invalid node names Node names are subject to the rules in table 2.1 of the devicetree specification v0.3, while properties are subject to rules in table 2.2. These rules mean that some property names are invalid node names. However, the same regular expression is being used to validate the names of nodes and properties in dtlib. This leads to invalid node names being allowed to pass. Fix this issue by moving the node name handling code to the Node constructor and checking against the characters in table 2.1. The test cases claim that the existing behavior matches dtc. I can't reproduce that. I get errors when I use invalid characters (like "?") in a node name. For example: foo.dts:3.8-11: ERROR (node_name_chars): /node?: Bad character '?' in node name Try to make the dtlib error message reminiscent of that. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>		2021-08-31 19:36:31 -04:00
..
python-devicetree	dtlib: fix issue which allowed invalid node names	2021-08-31 19:36:31 -04:00
README.txt	…
gen_defines.py	scripts: gen_defines: emit pinctrl helper macros	2021-08-25 18:09:00 -04:00
gen_dts_cmake.py	cmake: dts: import devicetree symbols into CMake	2021-08-25 20:28:26 -04:00

README.txt

This directory used to contain the edtlib.py and dtlib.py libraries
and tests, alongside the gen_defines.py script that uses them for
converting DTS to the C macros used by Zephyr.

The libraries and tests have now been moved to the 'python-devicetree'
subdirectory.

We are now in the process of extracting edtlib and dtlib into a
standalone source code library that we intend to share with other
projects.

Links related to the work making this standalone:

    https://pypi.org/project/devicetree/
    https://python-devicetree.readthedocs.io/en/latest/
    https://github.com/zephyrproject-rtos/python-devicetree

The 'python-devicetree' subdirectory you find here next to this
README.txt matches the standalone python-devicetree repository linked
above.

For now, the 'main' copy will continue to be hosted here in the zephyr
repository. We will mirror changes into the standalone repository as
needed; you can just ignore it for now.

Code in the zephyr repository which needs these libraries will import
devicetree.edtlib from now on, but the code will continue to be found
by manipulating sys.path for now.

Eventually, as APIs stabilize, the python-devicetree code in this
repository will disappear, and a standalone repository will be the
'main' one.