diff options
| author | Simon Glass <sjg@chromium.org> | 2019-07-20 12:23:56 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2019-07-29 09:38:06 -0600 |
| commit | 51014aabc28e497eb98e0ba9c1fa0f19e871af1b (patch) | |
| tree | bc48a7e5c0fdedc1a8e32b033cd9dc915b1fcb8d /tools/binman/README | |
| parent | eba1f0cc942947722f70029c033b915113cec1ba (diff) | |
binman: Allow updating entries that change size
So far we don't allow entries to change size when repacking. But this is
not very useful since it is common for entries to change size after an
updated binary is built, etc.
Add support for this, respecting the original offset/size/alignment
constraints of the image layout. For this to work the original image
must have been created with the 'allow-repack' property.
This does not support entry types with sub-entries such as files and
CBFS, but it does support sections.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/binman/README')
| -rw-r--r-- | tools/binman/README | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/tools/binman/README b/tools/binman/README index 1f9e13784f..af2a231471 100644 --- a/tools/binman/README +++ b/tools/binman/README @@ -589,7 +589,9 @@ that there is an 'fdtmap' entry in the image. For example: $ binman replace -i image.bin section/cbfs/u-boot which will write the contents of the file 'u-boot' from the current directory -to the that entry. The file must be the same size as the entry being replaced. +to the that entry. If the entry size changes, you must add the 'allow-repack' +property to the original image before generating it (see above), otherwise you +will get an error. Logging |