docs: Improve docs for FDT address passing

This patch updates FW_JUMP and FW_PAYLOAD documentation for the
case where FW_xyz_FDT_ADDR is not specified.

Signed-off-by: Liu Yibin <yibin_liu@c-sky.com>
Reviewed-by: Anup Patel <anup.patel@wdc.com>

diff --git a/docs/firmware/fw_jump.md b/docs/firmware/fw_jump.md
index 7fdeeb4..21161b0 100644 (file)
--- a/docs/firmware/fw_jump.md
+++ b/docs/firmware/fw_jump.md
@@ -38,8 +38,8 @@ follows:
 * **FW_JUMP_FDT_ADDR** - Address where the *flattened device tree (FDT file)*
   passed by the prior booting stage will be placed in memory before executing
   the booting stage following the OpenSBI firmware. If this option is not
-  provided, then the OpenSBI firmware will pass zero as the FDT address to the
-  following booting stage.
+  provided, then the OpenSBI firmware will pass the FDT address passed by the
+  previous booting stage to the next booting stage.
 
 *FW_JUMP* Example
 -----------------

diff --git a/docs/firmware/fw_payload.md b/docs/firmware/fw_payload.md
index c9a9ad8..1efe765 100644 (file)
--- a/docs/firmware/fw_payload.md
+++ b/docs/firmware/fw_payload.md
@@ -73,7 +73,8 @@ file. The parameters currently defined are as follows:
   stage or specified by the *FW_PAYLOAD_FDT_PATH* parameter and embedded in
   the *.text* section will be placed before executing the next booting stage,
   that is, the payload firmware. If this option is not provided, then the
-  firmware will pass zero as the FDT address to the next booting stage.
+  firmware will pass the FDT address passed by the previous booting stage
+  to the next booting stage.
 
 *FW_PAYLOAD* Example
 --------------------