summaryrefslogtreecommitdiff
path: root/doc/usage
diff options
context:
space:
mode:
authorDaniel Golle <[email protected]>2026-02-27 00:03:29 +0000
committerHeinrich Schuchardt <[email protected]>2026-03-27 10:50:29 +0100
commit72cc446490e74fdf392f5e049cf8fd28d9c6818d (patch)
tree6f88c2d14822a230dff266d51bbc01c0cdd680c0 /doc/usage
parentc24a72c35abe9cbbeb72e2effc6b6c73cd828a32 (diff)
treewide: fix uImage.FIT document paths
Commit 488445cefa1 ("doc: Move FIT into its own directory") moved the documentation in doc/uImage.FIT to doc/usage/fit, subsequently all documents and example sources have been converted to reStructuredText. Fix (almost) all of the remaining occurrences of the old path and filenames across the tree. The exception is doc/uImage.FIT/command_syntax_extensions.txt which apparently has been removed entirely, or at least I was unable to locate where that document is now. Signed-off-by: Daniel Golle <[email protected]>
Diffstat (limited to 'doc/usage')
-rw-r--r--doc/usage/fit/howto.rst4
1 files changed, 2 insertions, 2 deletions
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):