docs: Typo fixes

Signed-off-by: Atish Patra <atish.patra@wdc.com>
This commit is contained in:
Atish Patra authored and Anup Patel committed 2019-01-29 07:17:14 +05:30
1 parent d70f8aab45
commit 3211b6c542
4 files changed
+10 -9

No files matched your search

+2 -2
View File
@@ -14,7 +14,7 @@ the booting stage binary to follow OpenSBI firmware.
A platform *FW_JUMP* firmware can be enabled by any of the following methods.
1. Spedifying `FW_JUMP=y` on the top level `make` command line.
1. Specifying `FW_JUMP=y` on the top level `make` command line.
2. Specifying `FW_JUMP=y` in the target platform *config.mk* configuration file.
The compiled *FW_JUMP* firmware ELF file is named *fw_jump.elf*. Its expanded
@@ -37,7 +37,7 @@ 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 OpenSBI firmware. If this option is not provided
the booting stage following OpenSBI firmware. If this option is not provided,
then OpenSBI firmware will pass zero as the FDT address to the following
booting stage.
+1 -1
View File
@@ -72,7 +72,7 @@ file. The parameters currently defined are as follows.
* **FW_PAYLOAD_FDT_ADDR** - Address where the FDT passed by the prior booting
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
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.
*FW_PAYLOAD* Example