<feed xmlns='http://www.w3.org/2005/Atom'>
<title>starfive-tech/u-boot.git/tools/fit_image.c, branch rtthread_AMP</title>
<subtitle>StarFive Tech U-Boot for VisionFive (JH7110) boards (mirror)</subtitle>
<id>https://git.radix-linux.su/starfive-tech/u-boot.git/atom?h=rtthread_AMP</id>
<link rel='self' href='https://git.radix-linux.su/starfive-tech/u-boot.git/atom?h=rtthread_AMP'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/'/>
<updated>2021-07-14T20:57:35+00:00</updated>
<entry>
<title>tools/fitimage: add missing linebreak for some messages</title>
<updated>2021-07-14T20:57:35+00:00</updated>
<author>
<name>Sven Roederer</name>
<email>devel-sven@geroedel.de</email>
</author>
<published>2021-05-25T21:15:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=9c70237f19ab2c9084128b84c491c5e8d102008d'/>
<id>urn:sha1:9c70237f19ab2c9084128b84c491c5e8d102008d</id>
<content type='text'>
Add a linebreak to two messages and fix punctuation.

Signed-off-by: Sven Roederer &lt;devel-sven@geroedel.de&gt;
</content>
</entry>
<entry>
<title>mkimage: Add a 'keyfile' argument for image signing</title>
<updated>2021-04-14T19:23:01+00:00</updated>
<author>
<name>Alexandru Gagniuc</name>
<email>mr.nuke.me@gmail.com</email>
</author>
<published>2021-02-19T18:45:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=36bfcb62b3e7b846d0b693828df54a0d58e07511'/>
<id>urn:sha1:36bfcb62b3e7b846d0b693828df54a0d58e07511</id>
<content type='text'>
It's not always desirable to use 'keydir' and some ad-hoc heuristics
to get the filename of the signing key. More often, just passing the
filename is the simpler, easier, and logical thing to do.

Since mkimage doesn't use long options, we're slowly running out of
letters. I've chosen '-G' because it was available.

Signed-off-by: Alexandru Gagniuc &lt;mr.nuke.me@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>image: Adjust the workings of fit_check_format()</title>
<updated>2021-02-16T03:31:52+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-02-16T00:08:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=c5819701a3de61e2ba2ef7ad0b616565b32305e5'/>
<id>urn:sha1:c5819701a3de61e2ba2ef7ad0b616565b32305e5</id>
<content type='text'>
At present this function does not accept a size for the FIT. This means
that it must be read from the FIT itself, introducing potential security
risk. Update the function to include a size parameter, which can be
invalid, in which case fit_check_format() calculates it.

For now no callers pass the size, but this can be updated later.

Also adjust the return value to an error code so that all the different
types of problems can be distinguished by the user.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reported-by: Bruce Monroe &lt;bruce.monroe@intel.com&gt;
Reported-by: Arie Haenel &lt;arie.haenel@intel.com&gt;
Reported-by: Julien Lenoir &lt;julien.lenoir@intel.com&gt;
</content>
</entry>
<entry>
<title>mkimage: fit: fix import of external data</title>
<updated>2020-08-07T15:47:18+00:00</updated>
<author>
<name>Patrick Oppenlander</name>
<email>patrick.oppenlander@gmail.com</email>
</author>
<published>2020-07-30T04:31:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=c995d854efcbf54ebd99a41f9a3c918340f16376'/>
<id>urn:sha1:c995d854efcbf54ebd99a41f9a3c918340f16376</id>
<content type='text'>
The external data is located after the mmapped FDT pointed to by
'old_fdt', not in the newly created FDT we are importing into at 'fdt'.

Signed-off-by: Patrick Oppenlander &lt;patrick.oppenlander@gmail.com&gt;
</content>
</entry>
<entry>
<title>fit_image: Use calloc() to fix reproducibility issue</title>
<updated>2020-08-05T12:18:34+00:00</updated>
<author>
<name>Fabio Estevam</name>
<email>festevam@gmail.com</email>
</author>
<published>2020-07-28T00:03:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=aaa91a4e4b8a5d74f1317e18aa47d2a7a72e0c43'/>
<id>urn:sha1:aaa91a4e4b8a5d74f1317e18aa47d2a7a72e0c43</id>
<content type='text'>
Vagrant Cascadian reported that mx6cuboxi target no longer builds
reproducibility on Debian.

One example of builds mismatches:

00096680: 696e 6700 736f 756e 642d 6461 6900 6465  ing.sound-dai.de
-00096690: 7465 6374 2d67 7069 6f73 0000            tect-gpios..
+00096690: 7465 6374 2d67 7069 6f73 0061            tect-gpios.a

This problem happens because all the buffers in fit_image.c are
allocated via malloc(), which does not zero out the allocated buffer.

Using calloc() fixes this unpredictable behaviour as it guarantees
that the allocated buffer are zero initialized.

Reported-by: Vagrant Cascadian &lt;vagrant@reproducible-builds.org&gt;
Suggested-by: Tom Rini &lt;trini@konsulko.com&gt;
Signed-off-by: Fabio Estevam &lt;festevam@gmail.com&gt;
Tested-by: Vagrant Cascadian &lt;vagrant@reproducible-builds.org&gt;
</content>
</entry>
<entry>
<title>mkimage: Allow updating the FIT timestamp</title>
<updated>2020-07-25T20:46:57+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-07-10T00:39:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=152b246298bd5f107f5e08ddddee40411aa74cb7'/>
<id>urn:sha1:152b246298bd5f107f5e08ddddee40411aa74cb7</id>
<content type='text'>
Normally the FIT timestamp is created the first time mkimage is run on a
FIT, when converting the source .its to the binary .fit file. This
corresponds to using the -f flag. But if the original input to mkimage is
a binary file (already compiled) then the timestamp is assumed to have
been set previously.

Add a -t flag to allow setting the timestamp in this case.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>Revert "Merge tag 'dm-pull-20jul20' of git://git.denx.de/u-boot-dm"</title>
<updated>2020-07-24T12:42:06+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2020-07-24T12:42:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=7208396bbf1df1c7a85d263b7ff054e6b45d8240'/>
<id>urn:sha1:7208396bbf1df1c7a85d263b7ff054e6b45d8240</id>
<content type='text'>
This reverts commit 5d3a21df6694ebd66d5c34c9d62a26edc7456fc7, reversing
changes made to 56d37f1c564107e27d873181d838571b7d7860e7.

Unfortunately this is causing CI failures:
https://travis-ci.org/github/trini/u-boot/jobs/711313649

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>mkimage: Allow updating the FIT timestamp</title>
<updated>2020-07-20T17:37:47+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-07-10T00:39:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=4c63d21754a2583df1d85d3af6f0a5bf5c300d20'/>
<id>urn:sha1:4c63d21754a2583df1d85d3af6f0a5bf5c300d20</id>
<content type='text'>
Normally the FIT timestamp is created the first time mkimage is run on a
FIT, when converting the source .its to the binary .fit file. This
corresponds to using the -f flag. But if the original input to mkimage is
a binary file (already compiled) then the timestamp is assumed to have
been set previously.

Add a -t flag to allow setting the timestamp in this case.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>mkimage: Default to adding a crc32 hash with '-f auto'</title>
<updated>2020-06-02T21:27:04+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2020-05-27T13:24:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=317291167701480da6c235a17b0a7e89dafcff78'/>
<id>urn:sha1:317291167701480da6c235a17b0a7e89dafcff78</id>
<content type='text'>
This option currently does not add any sort of hash to the images in the
FIT.

Add a hash node requesting a crc32 checksum, which at least provides some
protection.

The crc32 value is easily ignored (e.g. in SPL) if not needed. and takes
up only about 48 bytes per image, including overhead.

Suggested-by: Wolfgang Denk &lt;wd@denx.de&gt;
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Wolfgang Denk &lt;wd@denx.de&gt;
</content>
</entry>
<entry>
<title>Revert "mkimage: fit: Do not tail-pad fitImage with external data"</title>
<updated>2020-05-07T13:01:42+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2020-05-06T15:05:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=7946a814a31989998120b4b4aa417222ba21b2fa'/>
<id>urn:sha1:7946a814a31989998120b4b4aa417222ba21b2fa</id>
<content type='text'>
This has been reported to break booting of U-Boot from SPL on a number
of platforms due to a lack of alignment of the external data.  The
issues this commit is addressing will need to be resolved another way.

Re-introduce a data leak in the padding for now.

This reverts commit 20a154f95bfe0a3b5bfba90bea7f001c58217536.

Reported-by: Alex Kiernan &lt;alex.kiernan@gmail.com&gt;
Reported-by: Michael Walle &lt;michael@walle.cc&gt;
Tested-by: Jan Kiszka &lt;jan.kiszka@siemens.com&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
