kernel/dtc - dtc - PowerEL Git System

David Gibson e3c769aa9c dtc: Don't always generate __symbols__ for plugins At the moment we generate a __symbols__ node if -@ is specified OR if the dts has the /plugin/ tag. That difference in behaviour from handling base trees is unnecessary and slightly confusing. It also means it's impossible to create a plugin without symbols. Since symbols in a plugin are only useful in the case of stacked plugins - and libfdt doesn't even support merging plugin symbols as part of overlay application yet - that's a thing that might be useful. So make __symbols__ generation depend only on -@. We also remove remove the testcases that checked explicitly for this not very useful behaviour. Instead we don't use -@ for our basic overlay testcase, and check that symbols are not generated. At some point in the future we should add support for symbol merging to libfdt and add testcases for stacked overlay application. Signed-off-by: David Gibson <david@gibson.dropbear.id.au>		8 years ago
Documentation	…
libfdt	…
scripts	…
tests	…
.gitignore	…
.travis.yml	…
GPL	…
Makefile	…
Makefile.convert-dtsv0	…
Makefile.dtc	…
Makefile.utils	…
README	…
README.license	…
TODO	…
checks.c	…
convert-dtsv0-lexer.l	…
data.c	…
dtc-lexer.l	…
dtc-parser.y	…
dtc.c	…
dtc.h	…
dtdiff	…
fdtdump.c	…
fdtget.c	…
fdtput.c	…
flattree.c	…
fstree.c	…
livetree.c	…
srcpos.c	…
srcpos.h	…
treesource.c	…
util.c	…
util.h	…

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>

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