You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
David Gibson 6ef8fcd05b Rebuild libfdt shared object if versioning linker script changes 6 years ago
Documentation
libfdt libfdt: Make fdt_get_max_phandle() an inline 6 years ago
pylibfdt Use Python3 by default 6 years ago
scripts
tests libfdt: Add phandle generation helper 6 years ago
.gitignore
.travis.yml
GPL
Makefile Rebuild libfdt shared object if versioning linker script changes 6 years ago
Makefile.convert-dtsv0
Makefile.dtc
Makefile.utils
README
README.license
TODO
checks.c checks: Do not omit nodes with labels if symbol generation is requested 6 years ago
convert-dtsv0-lexer.l
data.c
dtc-lexer.l
dtc-parser.y annotations: add positions 6 years ago
dtc.c annotations: add the annotation functionality 6 years ago
dtc.h annotations: add the annotation functionality 6 years ago
dtdiff
fdtdump.c Use PRIxPTR for printing uintptr_t values 6 years ago
fdtget.c
fdtoverlay.c
fdtput.c
flattree.c annotations: add positions 6 years ago
fstree.c annotations: add positions 6 years ago
livetree.c annotations: add positions 6 years ago
srcpos.c annotations: add the annotation functionality 6 years ago
srcpos.h annotations: add the annotation functionality 6 years ago
treesource.c annotations: add the annotation functionality 6 years ago
util.c util: Add xa{v}sprintf_append functions 6 years ago
util.h util: Add xa{v}sprintf_append functions 6 years ago
yamltree.c

README

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:

David Gibson <david@gibson.dropbear.id.au>
Jon Loeliger <jdl@jdl.com>


Python library
--------------

A Python library is also available. To build this you will need to install
swig and Python development files. On Debian distributions:

sudo apt-get install swig python-dev

The library provides an Fdt class which you can use like this:

$ PYTHONPATH=../pylibfdt python
>>> import libfdt
>>> fdt = libfdt.Fdt(open('test_tree1.dtb').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=%r' % (prop.name, prop.value)
compatible=bytearray(b'subnode1\x00')
>>> print '%s=%s' % (prop.name, prop.value)
compatible=subnode1
>>> node2 = fdt.path_offset('/')
>>> print fdt.getprop(node2, 'compatible')
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
$ python -c "import libfdt; help(libfdt)"

If you add new features, please check code coverage:

$ sudo apt-get install python-pip python-pytest
$ sudo pip install coverage
$ cd tests
$ coverage run pylibfdt_tests.py
$ coverage html
# Open 'htmlcov/index.html' in your browser


To install the library via the normal setup.py method, use:

./pylibfdt/setup.py [--prefix=/path/to/install_dir]

If --prefix is not provided, the default prefix is used, typically '/usr'
or '/usr/local'. See Python's distutils documentation for details. You can
also install via the Makefile if you like, but the above is more common.

To install both libfdt and pylibfdt you can use:

make install [SETUP_PREFIX=/path/to/install_dir] \
[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.


Tests
-----

Test files are kept in the tests/ directory. Use 'make check' to build and run
all tests.

If you want to adjust a test file, be aware that tree_tree1.dts is compiled
and checked against a binary tree from assembler macros in trees.S. So
if you change that file you must change tree.S also.


Mailing list
------------
The following list is for discussion about dtc and libfdt implementation
mailto:devicetree-compiler@vger.kernel.org

Core device tree bindings are discussed on the devicetree-spec list:
mailto:devicetree-spec@vger.kernel.org