From patchwork Sat Jan 5 01:51:55 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [U-Boot,RFC,26/44] Add minor updates to README.fdt-control Date: Fri, 04 Jan 2013 15:51:55 -0000 From: Simon Glass X-Patchwork-Id: 209605 Message-Id: <1357350734-13737-27-git-send-email-sjg@chromium.org> To: U-Boot Mailing List Cc: Joel A Fernandes , Tom Rini , Vadim Bendebury , =?UTF-8?q?Andreas=20B=C3=A4ck?= A few things have changed since this doc was written, so update it to match the current state of things. Signed-off-by: Simon Glass --- doc/README.fdt-control | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/doc/README.fdt-control b/doc/README.fdt-control index 69c69de..ba17879 100644 --- a/doc/README.fdt-control +++ b/doc/README.fdt-control @@ -49,6 +49,10 @@ the features of each board in the device tree file, and have a single generic source base. To enable this feature, add CONFIG_OF_CONTROL to your board config file. +It is currently supported on ARM, x86 and Microblaze - other architectures +will need to add code to their arch/xxx/lib/board.c file to locate the +FDT, at least until generic board support is complete. For ARM, Tegra and +Exynos5 have device trees available for common devices. What is a Flat Device Tree? @@ -99,7 +103,8 @@ Then run the compiler (your version will vary): * Bad configuration: 0 * Strange test result: 0 -You will also find a useful ftdump utility for decoding a binary file. +You will also find a useful fdtdump utility for decoding a binary file, as +well as fdtget/fdtput for reading and writing properties in a binary file. Where do I get an fdt file for my board?