diff options
| author | Simon Glass <sjg@chromium.org> | 2019-07-08 14:25:28 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2019-07-24 12:53:46 -0700 |
| commit | cf2289435c7e1134c75d9217ef32238aec0ecdbf (patch) | |
| tree | 9c58722f695d50ffae4968f0b89a30b1af201908 /tools/binman/README | |
| parent | 086cec9f980efd6f25e184b84f626d4a667e6645 (diff) | |
binman: Add an image header
It is useful to be able to quickly locate the FDT map in the image. An
easy way to do this is with a pointer at the start or end of the image.
Add an 'image header' entry, which places a magic number followed by a
pointer to the FDT map. This can be located at the start or end of the
image, or at a chosen location.
As part of this, update GetSiblingImagePos() to detect missing siblings.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/binman/README')
| -rw-r--r-- | tools/binman/README | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/tools/binman/README b/tools/binman/README index 8a5f3320dc..ef62d1f1ec 100644 --- a/tools/binman/README +++ b/tools/binman/README @@ -640,7 +640,9 @@ of each entry. Alternatively, an FDT map entry can be used to add a special FDT containing just the information about the image. This is preceded by a magic string so can -be located anywhere in the image. +be located anywhere in the image. An image header (typically at the start or end +of the image) can be used to point to the FDT map. See fdtmap and image-header +entries for more information. Compression @@ -817,7 +819,6 @@ Some ideas: - Add an option to decode an image into the constituent binaries - Support building an image for a board (-b) more completely, with a configurable build directory -- Support putting the FDT in an image with a suitable magic number - Support listing files in images - Support logging of binman's operations, with different levels of verbosity - Support updating binaries in an image (with no size change / repacking) |