diff options
| author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2023-09-28 10:02:57 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2023-10-11 13:22:32 -0400 |
| commit | 4cb6c8e5f0de3c4c5f9eba51c6a1610934a8cf77 (patch) | |
| tree | 6381e62bf9e136855b7b6700ef9d6a071eb61074 /doc | |
| parent | 4fb7e570d6bc3658e581937940de8cde52bd4103 (diff) | |
| download | u-boot-4cb6c8e5f0de3c4c5f9eba51c6a1610934a8cf77.zip u-boot-4cb6c8e5f0de3c4c5f9eba51c6a1610934a8cf77.tar.gz u-boot-4cb6c8e5f0de3c4c5f9eba51c6a1610934a8cf77.tar.bz2 | |
mkimage: update man page and -h output
The man page correctly said that -B was ignored without -E, while the
`mkimage -h` output suggested otherwise. Now that -B can actually be
used by itself, update the man page.
While at it, also amend the `mkimage -h` line to mention the
connection with -E.
The FDT header is a fixed 40 bytes, so its size cannot (and is not)
modified, while its alignment is a property of the address in RAM one
loads the FIT to, so not something mkimage can affect in any way. (In
the file itself, the header is of course at offset 0, which has all
possible alignments already.)
Reported-by: Sean Anderson <seanga2@gmail.com>
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/mkimage.1 | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/mkimage.1 b/doc/mkimage.1 index d0a038a..c190389 100644 --- a/doc/mkimage.1 +++ b/doc/mkimage.1 @@ -281,8 +281,10 @@ properties. A \(oqdata-offset\(cq of 0 indicates that it starts in the first .BI \-B " alignment" .TQ .BI \-\-alignment " alignment" -The alignment, in hexadecimal, that external data will be aligned to. This -option only has an effect when \-E is specified. +The alignment, in hexadecimal, that the FDT structure will be aligned +to. With +.BR \-E , +also specifies the alignment for the external data. . .TP .BI \-p " external-position" |