diff options
Diffstat (limited to 'doc/usage')
| -rw-r--r-- | doc/usage/cmd/pstore.rst | 4 | ||||
| -rw-r--r-- | doc/usage/fit/howto.rst | 4 | ||||
| -rw-r--r-- | doc/usage/fit/overlay-fdt-boot.rst | 8 |
3 files changed, 5 insertions, 11 deletions
diff --git a/doc/usage/cmd/pstore.rst b/doc/usage/cmd/pstore.rst index 63a437135ec..b8e2a478421 100644 --- a/doc/usage/cmd/pstore.rst +++ b/doc/usage/cmd/pstore.rst @@ -80,8 +80,8 @@ For test purpose, you can generate a kernel crash by setting reboot timeout to Retrieve logs in U-Boot ~~~~~~~~~~~~~~~~~~~~~~~ -First of all, unless PStore parameters as been set during U-Boot configuration -and match kernel ramoops parameters, it needs to be set using 'pstore set', e.g.:: +First of all, unless PStore parameters have been set during U-Boot configuration +and match kernel ramoops parameters, they need to be set using 'pstore set', e.g.:: => pstore set 0x30000000 0x100000 0x2000 0x2000 diff --git a/doc/usage/fit/howto.rst b/doc/usage/fit/howto.rst index 675c9aa5bb0..9c8d86e50be 100644 --- a/doc/usage/fit/howto.rst +++ b/doc/usage/fit/howto.rst @@ -157,7 +157,7 @@ development host is to be booted old-style (non-FDT) by U-Boot on an embedded target. Assume that the outcome of the build is vmlinux.bin.gz, a file which contains a gzip-compressed PPC Linux kernel (the only data file in this case). The uImage can be produced using the image source file -doc/uImage.FIT/kernel.its (note that kernel.its assumes that vmlinux.bin.gz is +doc/usage/fit/kernel.rst (note that kernel.its assumes that vmlinux.bin.gz is in the current working directory; if desired, an alternative path can be specified in the kernel.its file). Here's how to create the image and inspect its contents: @@ -269,7 +269,7 @@ Example 2 -- new-style (FDT) kernel booting Consider another simple scenario, where a PPC Linux kernel is to be booted new-style, i.e., with a FDT blob. In this case there are two prerequisite data files: vmlinux.bin.gz (Linux kernel) and target.dtb (FDT blob). The uImage can -be produced using image source file doc/uImage.FIT/kernel_fdt.its like this +be produced using image source file doc/usage/fit/kernel_fdt.rst like this (note again, that both prerequisite data files are assumed to be present in the current working directory -- image source file kernel_fdt.its can be modified to take the files from some other location if needed): diff --git a/doc/usage/fit/overlay-fdt-boot.rst b/doc/usage/fit/overlay-fdt-boot.rst index 0f012d6988a..5df304047c6 100644 --- a/doc/usage/fit/overlay-fdt-boot.rst +++ b/doc/usage/fit/overlay-fdt-boot.rst @@ -141,25 +141,21 @@ explosion problem:: data = /incbin/("./reva.dtbo"); type = "flat_dt"; arch = "arm"; - load = <0x87fc0000>; }; fdt-3 { data = /incbin/("./revb.dtbo"); type = "flat_dt"; arch = "arm"; - load = <0x87fc0000>; }; fdt-4 { data = /incbin/("./bar.dtbo"); type = "flat_dt"; arch = "arm"; - load = <0x87fc0000>; }; fdt-5 { data = /incbin/("./baz.dtbo"); type = "flat_dt"; arch = "arm"; - load = <0x87fc0000>; }; }; @@ -202,9 +198,7 @@ Booting this image is exactly the same as the non-overlay example. u-boot will retrieve the base blob and apply the overlays in sequence as they are declared in the configuration. -Note the minimum amount of different DT blobs, as well as the requirement for -the DT blobs to have a load address; the overlay application requires the blobs -to be writeable. +Note the minimum amount of different DT blobs. Configuration using overlays and feature selection -------------------------------------------------- |