u-boot.git/tools/binman/control.py, branch v2019.10

binman: Add command-line support for replacing entries

2019-07-29T15:38:06Z

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

binman: Correct the error message for invalid path

2019-07-29T15:38:06Z

At present this message references -o for output file. But binman uses -f now. Fix it. Signed-off-by: Simon Glass

binman: Split control.WriteEntryToImage() into separate functions

2019-07-29T15:38:06Z

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

binman: Update control.WriteEntry() to support writing the map

2019-07-29T15:38:06Z

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

binman: Move control.WriteEntry further down the file

2019-07-29T15:38:06Z

Move this function after the extraction logic so we can keep the writing logic in one place. Signed-off-by: Simon Glass

binman: Support replacing data in a cbfs

2019-07-29T15:38:06Z

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

binman: Support shrinking a entry after packing

2019-07-29T15:38:06Z

Sometimes an entry may shrink after it has already been packed. In that case we must repack the items. Of course it is always possible to just leave the entry at its original size and waste space at the end. This is what binman does by default, since there is the possibility of the entry changing size every time binman calculates its contents, thus causing a loop. Signed-off-by: Simon Glass

binman: Allow updating entries that change size

2019-07-29T15:38:06Z

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

binman: Write the original input fdtmap to a file

2019-07-29T15:38:06Z

When reading an image in, write its fdtmap to a file in the output directory. This is useful for debugging. Update the 'ls' command to set up the output directory; otherwise it will fail. Signed-off-by: Simon Glass

binman: Support updating entries in an existing image

2019-07-29T15:38:06Z

While it is useful and efficient to build images in a single pass from a unified description, it is sometimes desirable to update the image later. Add support for replace an existing file with one of the same size. This avoids needing to repack the file. Support for more advanced updates will come in future patches. Signed-off-by: Simon Glass