Dear Simon Glass, In message <1319519734-28704-3-git-send-email-...@chromium.org> you wrote: > This new option allows U-Boot to embed a binary device tree into its image > to allow run-time control of peripherals. This device tree is for U-Boot's > own use and is not necessarily the same one as is passed to the kernel. > > The device tree compiler output should be placed in the $(obj) > rooted tree. Since $(OBJCOPY) insists on adding the path to the > generated symbol names, to ensure consistency it should be > invoked from the directory where the .dtb file is located and > given the input file name without the path. > > This commit contains my entry for the ugliest Makefile / shell interaction > competition. > > Signed-off-by: Simon Glass <s...@chromium.org> > --- > Changes in v3: > - Move fdt files into board/<vendor>/dts > - Provide access to ARCH_CPU_DTS which is the CPU's base device tree > > Changes in v4: > - Remove unused 'clean' targets in dts/Makefile (remmove *.tmp at top-level) > - Move documentation into the first 'fdt' patch in the series > - Add note about CONFIG_ARCH_DEVICE_TREE > > Makefile | 5 ++ > README | 11 +++- > config.mk | 1 + > doc/README.fdt-control | 172 > ++++++++++++++++++++++++++++++++++++++++++++++++ > dts/Makefile | 103 +++++++++++++++++++++++++++++ > include/common.h | 1 + > 6 files changed, 291 insertions(+), 2 deletions(-) > create mode 100644 doc/README.fdt-control > create mode 100644 dts/Makefile
Applied, thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de I've got a bad feeling about this. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
