<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/binman/ftest.py, branch v2019.10</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/binman/ftest.py?h=v2019.10</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/binman/ftest.py?h=v2019.10'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2019-07-29T15:38:06Z</updated>
<entry>
<title>binman: Add command-line support for replacing entries</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a6cb995096c40ecd6597e20d792851ac7f80004e'/>
<id>urn:sha1:a6cb995096c40ecd6597e20d792851ac7f80004e</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Correct the error message for invalid path</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bb5edc1d3c0ebc989dfaa7d1e57cdde15d61f2e0'/>
<id>urn:sha1:bb5edc1d3c0ebc989dfaa7d1e57cdde15d61f2e0</id>
<content type='text'>
At present this message references -o for output file. But binman uses -f
now. Fix it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Clean up all output directories in tests</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f86a736349bd520fffb55bb9dbe3d63816780d67'/>
<id>urn:sha1:f86a736349bd520fffb55bb9dbe3d63816780d67</id>
<content type='text'>
At present some tests leave behind output directories. This happens
because some tests call binman, which sets up an output directory, then
call it again, which sets up another output directory and leaves the
original one behind.

Fix this by using a separate temporary directory when binman is called
twice, or by manually removing the output directory.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Add a test function to clean up the output dir</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bf574f129be2e2c7193024e0efac15d6b3496534'/>
<id>urn:sha1:bf574f129be2e2c7193024e0efac15d6b3496534</id>
<content type='text'>
Put tearDown()'s logic into a new _CleanupOutputDir() function so that it
can be called from elsewhere.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Support replacing data in a cbfs</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:06Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=eb0f4a4cb40264a90a91e10e3ec00d1e0da7fb66'/>
<id>urn:sha1:eb0f4a4cb40264a90a91e10e3ec00d1e0da7fb66</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Place Intel descriptor at image start</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:01Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=27145fd3a836173390c2d2adcd267fa3005b7fbe'/>
<id>urn:sha1:27145fd3a836173390c2d2adcd267fa3005b7fbe</id>
<content type='text'>
The Intel descriptor must always appear at the start of an (x86) image,
so it is supposed to position itself there always. However there is no
explicit test for this. Add one and fix a bug introduced by the recent
change to adjust Entry to read the node in a separate call.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Support shrinking a entry after packing</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:23:58Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=61ec04f9eda413664e5c11a6099c89a44b73b5b9'/>
<id>urn:sha1:61ec04f9eda413664e5c11a6099c89a44b73b5b9</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Update the _testing entry to support shrinkage</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:23:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=79d3c58d1268786ce40c6c0920ed2a447247fdc4'/>
<id>urn:sha1:79d3c58d1268786ce40c6c0920ed2a447247fdc4</id>
<content type='text'>
Sometimes entries shrink after packing. As a start towards supporting
this, update the _testing entry to handle the test case.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Allow updating entries that change size</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:23:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=51014aabc28e497eb98e0ba9c1fa0f19e871af1b'/>
<id>urn:sha1:51014aabc28e497eb98e0ba9c1fa0f19e871af1b</id>
<content type='text'>
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 &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Add more tests for image header position</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:23:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=eba1f0cc942947722f70029c033b915113cec1ba'/>
<id>urn:sha1:eba1f0cc942947722f70029c033b915113cec1ba</id>
<content type='text'>
The positioning does not currently work correctly if at the end of an
image with no fixed size. Also if the header is in the middle of an image
it can cause a gap in the image since the header position is normally at
the image end, so entries after it are placed after the end of the image.

Fix these problems and add more tests to cover these cases.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
