<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools/binman/cbfs_util.py, branch v2021.01</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools/binman/cbfs_util.py?h=v2021.01</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools/binman/cbfs_util.py?h=v2021.01'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2020-04-26T20:25:21Z</updated>
<entry>
<title>patman: Move to absolute imports</title>
<updated>2020-04-26T20:25:21Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-18T00:09:04Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bf776679a73f3b9eae37aabd2be5754483039cb2'/>
<id>urn:sha1:bf776679a73f3b9eae37aabd2be5754483039cb2</id>
<content type='text'>
At present patman sets the python path on startup so that it can access
the libraries it needs. If we convert to use absolute imports this is not
necessary.

Move patman to use absolute imports. This requires changes in tools which
use the patman libraries (which is most of them).

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Move to absolute imports</title>
<updated>2020-04-26T20:25:21Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-18T00:09:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=16287933a852bab2ac4985a770e08c9aa69d21b1'/>
<id>urn:sha1:16287933a852bab2ac4985a770e08c9aa69d21b1</id>
<content type='text'>
At present binman sets the python path on startup so that it can access
the libraries it needs. If we convert to use absolute imports this is not
necessary.

Move binman to use absolute imports. This enables removable of the path
adjusting in Entry also.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>patman: Drop references to __future__</title>
<updated>2020-04-26T20:25:21Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-04-18T00:08:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=83a45187715e719bfe520b9ca0373bd8b5bee8aa'/>
<id>urn:sha1:83a45187715e719bfe520b9ca0373bd8b5bee8aa</id>
<content type='text'>
We don't need these now that the tools using Python 3. Drop them.

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: Add a prefix before CBFS hex offsets</title>
<updated>2019-07-29T15:38:06Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-20T18:24:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=17a7421ff417f21d0e3e151c992d7188ded3c0d3'/>
<id>urn:sha1:17a7421ff417f21d0e3e151c992d7188ded3c0d3</id>
<content type='text'>
Add a 0x prefix to these errors to avoid confusion.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Support reading from CBFS entries</title>
<updated>2019-07-24T19:54:08Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-08T20:25:51Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3a9c252583785c3aabce834e8f9a54fa94685ee8'/>
<id>urn:sha1:3a9c252583785c3aabce834e8f9a54fa94685ee8</id>
<content type='text'>
CBFS is a bit like a section but with a custom format. Provide the list of
entries and the compression type to binman so that it can extract the data
from the CBFS, just like any other part of the image.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Use the cbfs memlen field only for uncompressed length</title>
<updated>2019-07-24T19:54:08Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-08T20:25:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=52107ee4df878d26923a498b62beedbbaa5c1f7e'/>
<id>urn:sha1:52107ee4df878d26923a498b62beedbbaa5c1f7e</id>
<content type='text'>
The purpose of this badly named field is a bit ambiguous. Adjust the code
to use it only to store the uncompressed length of a file, leaving it set
to None if there is no compression used. This makes it easy to see if the
value in this field is relevant / useful.

Also set data_len for compressed fields, since it should be the length of
the compressed data, not the uncompressed data.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Provide the actual data address for cbfs files</title>
<updated>2019-07-24T19:54:08Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-08T20:25:39Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1223db038a5282b400eab3e4bd2a44fa8658ff4e'/>
<id>urn:sha1:1223db038a5282b400eab3e4bd2a44fa8658ff4e</id>
<content type='text'>
At present a file with no explicit CBFS offset is placed in the next
available location but there is no way to find out where it ended up.
Update and rename the get_data() function to provide this information.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Add support for fixed-offset files in CBFS</title>
<updated>2019-07-24T19:53:46Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-08T19:18:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e073d4e14ff76f545a71dc40fa324618ce80adcb'/>
<id>urn:sha1:e073d4e14ff76f545a71dc40fa324618ce80adcb</id>
<content type='text'>
A feature of CBFS is that it allows files to be positioned at particular
offset (as with binman in general). This is useful to support
execute-in-place (XIP) code, since this may not be relocatable.

Add a new cbfs-offset property to control this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Pad empty areas of the CBFS with files</title>
<updated>2019-07-24T19:53:46Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2019-07-08T19:18:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7c173ced645b9fff4d5b41849375275a8b63f04d'/>
<id>urn:sha1:7c173ced645b9fff4d5b41849375275a8b63f04d</id>
<content type='text'>
When there is lots of open space in a CBFS it is normally padded with
'empty' files so that sequentially scanning the CBFS can skip from one to
the next without a break.

Add support for this.

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