u-boot.git/tools/binman/control.py, branch v2020.04 Unnamed repository; edit this file 'description' to name the repository. binman: Add logging for the number of pack passes 2019-10-15T14:40:02+00:00 Simon Glass sjg@chromium.org 2019-08-24T13:23:13+00:00 aed6c0b04350aaecdf3d93db5ee9b374f425222b Sometimes binman takes multiple passes to complete packing an image. Add logging to indicate this. Signed-off-by: Simon Glass <sjg@chromium.org> 
Sometimes binman takes multiple passes to complete packing an image. Add
logging to indicate this.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Write symbol info before image inclusion 2019-10-15T14:40:02+00:00 Simon Glass sjg@chromium.org 2019-08-24T13:23:12+00:00 261cbe0b3716737e328481b6f3f51cfcb7f13e31 At present the symbol information is written to binaries just before binman exits. This is fine for entries within sections since the section contents is calculated when it is needed, so the updated symbol values are included in the image that is written. However some binaries are inside entries which have already generated their contents and do not notice that the entries have changed (e.g. Intel IFWI). Move the symbol writing earlier to cope with this. Signed-off-by: Simon Glass <sjg@chromium.org> 
At present the symbol information is written to binaries just before
binman exits. This is fine for entries within sections since the section
contents is calculated when it is needed, so the updated symbol values are
included in the image that is written.

However some binaries are inside entries which have already generated
their contents and do not notice that the entries have changed (e.g. Intel
IFWI).

Move the symbol writing earlier to cope with this.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Allow use of help and entry-docs without libfdt 2019-10-15T14:40:02+00:00 Simon Glass sjg@chromium.org 2019-08-24T13:22:44+00:00 8dbb7444ebaa499b753269c88cdd76f12f0fa875 At present if libfdt is not available binman can't do anything much. Improve the situation a little. Ideally there should be a test to cover this, but I'm not quite sure how to fake this. Signed-off-by: Simon Glass <sjg@chromium.org> (fixed up missing ReadChildData() enty test) 
At present if libfdt is not available binman can't do anything much.
Improve the situation a little.

Ideally there should be a test to cover this, but I'm not quite sure how
to fake this.

Signed-off-by: Simon Glass <sjg@chromium.org>
(fixed up missing ReadChildData() enty test)
binman: Allow verbose output with all commands 2019-10-08T05:57:43+00:00 Simon Glass sjg@chromium.org 2019-09-16T00:10:36+00:00 7bc4f0f88327bcd3c2daafe969f049dcfab41b00 At present the verbose flag only works for the 'build' command. This is not intended, nor is it useful. Update the code to support the verbose flag and make use of a command exception handler. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com> [bmeng: rebase the patch against u-boot-x86/next to get it applied cleanly] Signed-off-by: Bin Meng <bmeng.cn@gmail.com> 
At present the verbose flag only works for the 'build' command. This is
not intended, nor is it useful. Update the code to support the verbose
flag and make use of a command exception handler.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
[bmeng: rebase the patch against u-boot-x86/next to get it applied cleanly]
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
binman: Add command-line support for replacing entries 2019-07-29T15:38:06+00:00 Simon Glass sjg@chromium.org 2019-07-20T18:24:15+00:00 a6cb995096c40ecd6597e20d792851ac7f80004e Add a 'replace' command to binman to permit entries to be replaced, either individually or all at once (using a filter). Signed-off-by: Simon Glass <sjg@chromium.org> 
Add a 'replace' command to binman to permit entries to be replaced, either
individually or all at once (using a filter).

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Correct the error message for invalid path 2019-07-29T15:38:06+00:00 Simon Glass sjg@chromium.org 2019-07-20T18:24:14+00:00 bb5edc1d3c0ebc989dfaa7d1e57cdde15d61f2e0 At present this message references -o for output file. But binman uses -f now. Fix it. Signed-off-by: Simon Glass <sjg@chromium.org> 
At present this message references -o for output file. But binman uses -f
now. Fix it.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Split control.WriteEntryToImage() into separate functions 2019-07-29T15:38:06+00:00 Simon Glass sjg@chromium.org 2019-07-20T18:24:13+00:00 d7fa4e4b22d8f493e6f643843f0a7aaf448d098a This code has three distinct phases: 1. The image is loaded and the state module is set up 2. The entry is written to the image 3. The image is repacked and written back to the file Split the code out with three separate functions, one for each phase. Signed-off-by: Simon Glass <sjg@chromium.org> 
This code has three distinct phases:

1. The image is loaded and the state module is set up
2. The entry is written to the image
3. The image is repacked and written back to the file

Split the code out with three separate functions, one for each phase.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Update control.WriteEntry() to support writing the map 2019-07-29T15:38:06+00:00 Simon Glass sjg@chromium.org 2019-07-20T18:24:12+00:00 3ad804e6bd1d1b9d3a669a053796ae4341e235dc Add the ability to write a new map file. Also tidy up a few comments and rename a misleading variable. Signed-off-by: Simon Glass <sjg@chromium.org> 
Add the ability to write a new map file. Also tidy up a few comments and
rename a misleading variable.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Move control.WriteEntry further down the file 2019-07-29T15:38:06+00:00 Simon Glass sjg@chromium.org 2019-07-20T18:24:11+00:00 22a76b7428e74c4193f4356f6caeeda69628cf64 Move this function after the extraction logic so we can keep the writing logic in one place. Signed-off-by: Simon Glass <sjg@chromium.org> 
Move this function after the extraction logic so we can keep the writing
logic in one place.

Signed-off-by: Simon Glass <sjg@chromium.org>
binman: Support replacing data in a cbfs 2019-07-29T15:38:06+00:00 Simon Glass sjg@chromium.org 2019-07-20T18:24:06+00:00 eb0f4a4cb40264a90a91e10e3ec00d1e0da7fb66 At present binman cannot replace data within a CBFS since it does not allow rewriting of the files in that CBFS. Implement this by using the new WriteData() method to handle the case. Add a header to compressed data so that the amount of compressed data can be determined without reference to the size of the containing entry. This allows the entry to be larger that the contents, without causing errors in decompression. This is necessary to cope with a compressed device tree being updated in such a way that it shrinks after the entry size is already set (an obscure case). It is not used with CBFS since it has its own metadata for this. Increase the number of passes allowed to resolve the position of entries, to handle this case. Add a test for this new logic. Signed-off-by: Simon Glass <sjg@chromium.org> 
At present binman cannot replace data within a CBFS since it does not
allow rewriting of the files in that CBFS. Implement this by using the
new WriteData() method to handle the case.

Add a header to compressed data so that the amount of compressed data can
be determined without reference to the size of the containing entry. This
allows the entry to be larger that the contents, without causing errors in
decompression. This is necessary to cope with a compressed device tree
being updated in such a way that it shrinks after the entry size is
already set (an obscure case). It is not used with CBFS since it has its
own metadata for this. Increase the number of passes allowed to resolve
the position of entries, to handle this case.

Add a test for this new logic.

Signed-off-by: Simon Glass <sjg@chromium.org>