summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAnatolij Gustschin <agust@denx.de>2017-08-17 19:01:48 (GMT)
committerTom Rini <trini@konsulko.com>2017-08-26 18:56:12 (GMT)
commit767cb74a0028be337d2ffecee7450e83fa2e7bd1 (patch)
tree77f102e19cab2df9305f3d62b64e51ca0b19852a /doc
parent195dc23185400fa605d268c3d903c83286ecae37 (diff)
downloadu-boot-767cb74a0028be337d2ffecee7450e83fa2e7bd1.tar.xz
cmd: spl: provide address and size of prepared FDT in environment
Writing prepared FDT to persistent storage should be possible in scripts. Create environment variables containing address and size of the updated FDT. Scripts can use these variables after running 'spl export fdt ...' command to write the new blob to persistent storage. Signed-off-by: Anatolij Gustschin <agust@denx.de>
Diffstat (limited to 'doc')
-rw-r--r--doc/README.falcon7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/README.falcon b/doc/README.falcon
index e9f8a75..9a7f0bc 100644
--- a/doc/README.falcon
+++ b/doc/README.falcon
@@ -118,7 +118,12 @@ after each run of 'spl export'. Unfortunately the position of temporary
storage can not be predicted nor provided at commandline, it depends
highly on your system setup and your provided data (ATAGS or FDT).
However at the end of an succesful 'spl export' run it will print the
-RAM address of temporary storage.
+RAM address of temporary storage. The RAM address of FDT will also be
+set in the environment variable 'fdtargsaddr', the new length of the
+prepared FDT will be set in the environment variable 'fdtargslen'.
+These environment variables can be used in scripts for writing updated
+FDT to persistent storage.
+
Now the user have to save the generated BLOB from that printed address
to the pre-defined address in persistent storage
(CONFIG_CMD_SPL_NAND_OFS in case of NAND).