<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/tools, branch v2025.01-rc1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/tools?h=v2025.01-rc1</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/tools?h=v2025.01-rc1'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2024-10-22T02:51:23Z</updated>
<entry>
<title>envtools: make them build again</title>
<updated>2024-10-22T02:51:23Z</updated>
<author>
<name>Rasmus Villemoes</name>
<email>ravi@prevas.dk</email>
</author>
<published>2024-10-16T15:10:35Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6606a6adfaf8517cff7e5fe0fb206beed80087d5'/>
<id>urn:sha1:6606a6adfaf8517cff7e5fe0fb206beed80087d5</id>
<content type='text'>
In v2024.10, "make envtools" is broken for at least these defconfigs:

   am335x_evm_defconfig
   rpi_3_defconfig
   rpi_4_defconfig
   mx7dsabresd_defconfig
   wandboard_defconfig
   imx8mp_evk_defconfig

The only defconfig we use for which it is not broken is
stm32mp13_defconfig. They all work just fine in v2024.07.

The symptoms are slightly different, but all related to the fact that
some transitively included header uses IS_ENABLED or CONFIG_IS_ENABLED
without linux/kconfig.h having already been included.

A simple git bisect doesn't produce anything sensible, it ends up at
3a9f642ca94 (crypto: nuvoton: npcm_sha: Support SHA 384/512) which
clearly has nothing to do with this. But digging deeper, one
eventually finds 0f92fa45603 ("env: Remove &lt;common.h&gt; and add needed
includes").

So at first I tried adding "#include &lt;linux/kconfig.h&gt;" in
include/env_default.h and include/env_flags.h. That fixes it for some,
but not all, of the above. For example rpi_3_defconfig still fails,
then in log.h complaining about BIT() and u8 not being defined. At
least BIT() is should have gotten from bitops.h, except that that's
behind ifdef __KERNEL__, so not set for the envtools build.

It turns out that the envtools source code in fw_env_private.h already
has some hackery to deal with all this, in the form of the __ASSEMBLY__
games it plays before including config.h. It seems that if we just
make sure to do that include early enough, so that config.h is indeed
parsed with that __ASSEMBLY__ hackery in place, everything builds
fine.

Fixes: 0f92fa45603 ("env: Remove &lt;common.h&gt; and add needed includes")
Signed-off-by: Rasmus Villemoes &lt;ravi@prevas.dk&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Fabio Estevam &lt;festevam@gmail.com&gt;
</content>
</entry>
<entry>
<title>Merge patch series "aspeed: ast2700: Add Caliptra ECDSA driver"</title>
<updated>2024-10-21T23:53:11Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2024-10-21T23:53:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a3709638ecbc7ffeff36d2233c5cf4e830e428a2'/>
<id>urn:sha1:a3709638ecbc7ffeff36d2233c5cf4e830e428a2</id>
<content type='text'>
Chia-Wei Wang &lt;chiawei_wang@aspeedtech.com&gt; says:

Aspeed AST2700 SoCs integrates the Caliptra secure IP, where an ECDSA384
signature verification HW interface is exported for SoC crypto needs.

This patch series firstly extends the FIT image signing/verify common
code to support the ECDSA384 algorithm. For better convenience, the
device tree for ECDSA public key storage is also revised by referring
to RSA implementations.

After the FIT common code revision, the driver is implemented for
AST2700 to leverage the Caliptra ECDSA384 signature verification.

These are verified by signed FIT images with the algorithm "sha384,ecdsa384".

Link: https://lore.kernel.org/r/20241014095620.216936-1-chiawei_wang@aspeedtech.com
</content>
</entry>
<entry>
<title>lib: ecdsa: Add ECDSA384 support</title>
<updated>2024-10-21T23:52:52Z</updated>
<author>
<name>Chia-Wei Wang</name>
<email>chiawei_wang@aspeedtech.com</email>
</author>
<published>2024-10-14T09:56:18Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=75068b1a2dbcf475c1043e7aa0f6882554d759bc'/>
<id>urn:sha1:75068b1a2dbcf475c1043e7aa0f6882554d759bc</id>
<content type='text'>
Add ECDSA384 algorithm support for image signing and verification.

Signed-off-by: Chia-Wei Wang &lt;chiawei_wang@aspeedtech.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>docker: Update coreboot</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-10-14T22:32:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1903aa72ec443faa28a931da090ef379955d7e3f'/>
<id>urn:sha1:1903aa72ec443faa28a931da090ef379955d7e3f</id>
<content type='text'>
Update to a newer version which supports settings in CMOS RAM and
linear framebuffer.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>expo: Use standard numbering for save and discard</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-10-14T22:31:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=d8ff97ce91529263c9d82a4bc00e133822673ab0'/>
<id>urn:sha1:d8ff97ce91529263c9d82a4bc00e133822673ab0</id>
<content type='text'>
Set aside some expo IDs for 'save' and 'discard' buttons. This avoids
needing to store the IDs for these. Adjust the documentation and expo
tool for the new EXPOID_BASE_ID value.

Ignore these objects when saving and loading the cedit, since they do
not contain real data.

Adjust 'cedit run' to return failure when the user exits the expo
without saving. Update the test for this change as well.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: Add a tutorial on resolving test-coverage bugs</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-09-30T18:51:38Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7f4e1ea00bc417d99fa5a87091932280de34cab4'/>
<id>urn:sha1:7f4e1ea00bc417d99fa5a87091932280de34cab4</id>
<content type='text'>
Provide a short description of how tests work, why they are so critical
and how to resolve gaps in Binman's test coverage.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Acked-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Reviewed-by: Mattijs Korpershoek &lt;mkorpershoek@baylibre.com&gt;
</content>
</entry>
<entry>
<title>binman: Support getting test-coverage on just one test</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-09-30T18:51:37Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3473e1779cccf486df7cae43b79fedd837703756'/>
<id>urn:sha1:3473e1779cccf486df7cae43b79fedd837703756</id>
<content type='text'>
Pass the arguments through to test_util so that a single test can be
used.

Update the docs and add some missing backquotes in the same section.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>u_boot_pylib: Support running coverage on selected functions</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-09-30T18:51:36Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c95a3c889079c83f4a47c2a09794879378047592'/>
<id>urn:sha1:c95a3c889079c83f4a47c2a09794879378047592</id>
<content type='text'>
At present run_test_coverage() assumes you want code coverage for the
entire code base. This is the normal situation, but sometimes it is
useful to see the coverage provided by just a single test. Add support
for this.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>buildman: Correct some warnings about regex strings</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2024-09-21T17:57:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=02eb9f166573009f576133a15d6323ff4ab479b1'/>
<id>urn:sha1:02eb9f166573009f576133a15d6323ff4ab479b1</id>
<content type='text'>
With Python 3.12 some warnings have cropped up. Fix them.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>binman: implement signing FIT images during image build</title>
<updated>2024-10-18T20:10:22Z</updated>
<author>
<name>Alexander Kochetkov</name>
<email>al.kochet@gmail.com</email>
</author>
<published>2024-09-16T08:24:46Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=133c000ca334743fda3a4d77f7638da1a807e40e'/>
<id>urn:sha1:133c000ca334743fda3a4d77f7638da1a807e40e</id>
<content type='text'>
The patch implement new property 'fit,sign' that can be declared
at the top-level 'fit' node. If that option is declared, fit tryies
to detect private keys directory among binman include directories.
That directory than passed to mkimage using '-k' flag and that enable
signing of FIT.

Signed-off-by: Alexander Kochetkov &lt;al.kochet@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Renumbered files, moved new tests to end:
Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
