Android 14.0.0 release 29 # -----BEGIN PGP SIGNATURE----- # # iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZeZWyQAKCRDorT+BmrEO # eCurAKCMOLzC9jKbJRZe0b/ZNoNv9wlE3ACeO6DTK0llqb4qNN+/W1JFTPbTBro= # =/Jha # -----END PGP SIGNATURE----- # gpg: Signature made Tue Mar 5 01:18:33 2024 EET # gpg: using DSA key 4340D13570EF945E83810964E8AD3F819AB10E78 # gpg: Good signature from "The Android Open Source Project <initial-contribution@android.com>" [marginal] # gpg: initial-contribution@android.com: Verified 2339 signatures in the past # 2 years. Encrypted 4 messages in the past 2 years. # gpg: WARNING: This key is not certified with sufficiently trusted signatures! # gpg: It is not certain that the signature belongs to the owner. # Primary key fingerprint: 4340 D135 70EF 945E 8381 0964 E8AD 3F81 9AB1 0E78 # By Pierre-Clément Tosi (12) and others # Via Automerger Merge Worker (50) and others * tag 'android-14.0.0_r29': ANDROID: Generate version_gen.h in Soong and Bazel FROMGIT: libfdt: fdt_get_alias_namelen: Validate aliases FROMGIT: use fdt_path_getprop_namelen() in fdt_get_alias_namelen() FROMGIT: add fdt_path_getprop_namelen() helper ANDROID: Revert "libfdt: Validate alias property value is a valid string." FROMLIST: libdft: fdt_next_tag: Harden offset overflow check FROMGIT: libfdt: prevent integer overflow in fdt_next_tag ANDROID: Revert "Fix integer wrap sanitisation." FROMGIT: libfdt: fdt_path_offset_namelen: Reject empty path ANDROID: Revert "libfdt: fdt_path_offset_namelen: Reject empty paths" ANDROID: bazel: Clean up lexer and parser rules ANDROID: bazel: Fix dtc header dependencies ANDROID: Use -Wall and more when building libfdt ANDROID: Use -Wno-macro-redefined for DTC tools ANDROID: De-dup fdt_path_offset_namelen check build: Add BUILD.bazel file Change-Id: Id735f73688acfa3758902473383abd9eea6e8f5a
Device Tree Compiler and libfdt
The source tree contains the Device Tree Compiler (dtc) toolchain for working with device tree source and binary files and also libfdt, a utility library for reading and manipulating the binary format.
dtc and libfdt are maintained by:
Python library
A Python library wrapping libfdt is also available. To build this you
will need to install swig and Python development files. On Debian
distributions:
$ sudo apt-get install swig python3-dev
The library provides an Fdt class which you can use like this:
$ PYTHONPATH=../pylibfdt python3
>>> import libfdt
>>> fdt = libfdt.Fdt(open('test_tree1.dtb', mode='rb').read())
>>> node = fdt.path_offset('/subnode@1')
>>> print(node)
124
>>> prop_offset = fdt.first_property_offset(node)
>>> prop = fdt.get_property_by_offset(prop_offset)
>>> print('%s=%s' % (prop.name, prop.as_str()))
compatible=subnode1
>>> node2 = fdt.path_offset('/')
>>> print(fdt.getprop(node2, 'compatible').as_str())
test_tree1
You will find tests in tests/pylibfdt_tests.py showing how to use each
method. Help is available using the Python help command, e.g.:
$ cd pylibfdt
$ python3 -c "import libfdt; help(libfdt)"
If you add new features, please check code coverage:
$ sudo apt-get install python3-coverage
$ cd tests
# It's just 'coverage' on most other distributions
$ python3-coverage run pylibfdt_tests.py
$ python3-coverage html
# Open 'htmlcov/index.html' in your browser
The library can be installed with pip from a local source tree:
$ pip install . [--user|--prefix=/path/to/install_dir]
Or directly from a remote git repo:
$ pip install git+git://git.kernel.org/pub/scm/utils/dtc/dtc.git@main
The install depends on libfdt shared library being installed on the
host system first. Generally, using --user or --prefix is not
necessary and pip will use the default location for the Python
installation which varies if the user is root or not.
You can also install everything via make if you like, but pip is recommended.
To install both libfdt and pylibfdt you can use:
$ make install [PREFIX=/path/to/install_dir]
To disable building the python library, even if swig and Python are available, use:
$ make NO_PYTHON=1
More work remains to support all of libfdt, including access to numeric values.
Mailing lists
- The devicetree-compiler list is for discussion about dtc and libfdt implementation.
- Core device tree bindings are discussed on the devicetree-spec list.