diff options
| author | Simon Glass <sjg@chromium.org> | 2013-05-07 06:11:46 +0000 |
|---|---|---|
| committer | Tom Rini <trini@ti.com> | 2013-05-14 15:37:24 -0400 |
| commit | 134a65124d1316a043b1da515abddafcb9309714 (patch) | |
| tree | f972e886f00579b0d2813e44da107884b458d6c7 /doc | |
| parent | 9602286d3d554d744f6ed2fa3c001d208a7aca23 (diff) | |
Add minor updates to README.fdt-control
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 <sjg@chromium.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.fdt-control | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/README.fdt-control b/doc/README.fdt-control index 5963f78e96..95a88a7c7b 100644 --- a/doc/README.fdt-control +++ b/doc/README.fdt-control @@ -49,6 +49,12 @@ 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. Alternatively you can enable generic board support on your board +(with CONFIG_SYS_GENERIC_BOARD) if this is available (as it is for +PowerPC). For ARM, Tegra and Exynos5 have device trees available for +common devices. What is a Flat Device Tree? @@ -99,7 +105,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? |