cmd: pxe_utils: sysboot: add kaslr-seed generation support

[platform/kernel/u-boot.git] / doc / README.falcon

diff --git a/doc/README.falcon b/doc/README.falcon
index e9f8a75..88218d3 100644 (file)
--- a/doc/README.falcon
+++ b/doc/README.falcon
@@ -67,7 +67,9 @@ CONFIG_SYS_NAND_SPL_KERNEL_OFFS       Offset in NAND where the kernel is stored
 
 CONFIG_CMD_SPL_NAND_OFS        Offset in NAND where the parameters area was saved.
 
-CONFIG_CMD_SPL_WRITE_SIZE      Size of the parameters area to be copied
+CONFIG_CMD_SPL_NOR_OFS Offset in NOR where the parameters area was saved.
+
+CONFIG_CMD_SPL_WRITE_SIZE      Size of the parameters area to be copied
 
 CONFIG_SPL_OS_BOOT     Activate Falcon Mode.
 
@@ -87,7 +89,7 @@ Environment variables
 A board may chose to look at the environment for decisions about falcon
 mode.  In this case the following variables may be supported:
 
-boot_os :              Set to yes/Yes/true/True/1 to enable booting to OS,
+boot_os :              Set to yes/Yes/true/True/1 to enable booting to OS,
                        any other value to fall back to U-Boot (including
                        unset)
 falcon_args_file :     Filename to load as the 'args' portion of falcon mode
@@ -118,7 +120,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).