Hi Quentin,
On Mon, 6 Feb 2023 at 03:26, Quentin Schulz quentin.schulz@theobroma-systems.com wrote:
Hi Simon,
On 2/4/23 23:24, Simon Glass wrote:
Implement this feature since it is useful for updating FITs within an image.
Signed-off-by: Simon Glass sjg@chromium.org
tools/binman/binman.rst | 16 ++++++++++ tools/binman/etype/section.py | 28 ++++++++++++----- tools/binman/ftest.py | 58 ++++++++++++++++++++++++++++++++--- 3 files changed, 90 insertions(+), 12 deletions(-)
diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst index 03a99a19bc6..ece2c05128a 100644 --- a/tools/binman/binman.rst +++ b/tools/binman/binman.rst @@ -1327,6 +1327,22 @@ You can also replace just a selection of entries::
$ binman replace -i image.bin "*u-boot*" -I indir+It is possible to replace whole sections as well, but in that case any +information about entries within the section may become outdated. This is +because Binman cannot know whether things have moved around or resized within +the section, once you have updated its data.
+Technical note: With 'allow-repack', Binman writes information about the +original offset and size properties of each entry, if any were specified, in +the 'orig-offset' and 'orig-size' properties. This allows Binman to distinguish +between an entry which ended up being packed at an offset (or assigned a size) +and an entry which had a particular offset / size requested in the Binman +configuration. Where are particular offset / size was requested, this is treated
s/Where are/Where a/
Sadly I forgot about this. Will fix in the next version/
Regards, Simon