<feed xmlns='http://www.w3.org/2005/Atom'>
<title>starfive-tech/u-boot.git/common/Kconfig.boot, 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>2023-09-07T01:34:13+00:00</updated>
<entry>
<title>common: autoboot: Add auto-fastboot on StarFive SoC</title>
<updated>2023-09-07T01:34:13+00:00</updated>
<author>
<name>Xingyu Wu</name>
<email>xingyu.wu@starfivetech.com</email>
</author>
<published>2023-09-06T07:14:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=fe15334eb1ad300a0b094c1ce9968c4ba4a200c6'/>
<id>urn:sha1:fe15334eb1ad300a0b094c1ce9968c4ba4a200c6</id>
<content type='text'>
Add auto-fastboot function before autoboot on StarFive SoC
and add a config to enable or disable this.

In the auto-fastboot, it check a environment flag of 'fb_sf_completed'
first. The flag is NULL and then the fastboot will work.
The flag will be set from USB tool to indicate done after flashing the
image.

Signed-off-by: Xingyu Wu &lt;xingyu.wu@starfivetech.com&gt;
</content>
</entry>
<entry>
<title>image: Drop if/elseif hash selection in calculate_hash()</title>
<updated>2021-09-08T20:12:09+00:00</updated>
<author>
<name>Alexandru Gagniuc</name>
<email>mr.nuke.me@gmail.com</email>
</author>
<published>2021-09-03T00:54:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=92055e138f2873034e2dfd7e1308e30c9bbef3b1'/>
<id>urn:sha1:92055e138f2873034e2dfd7e1308e30c9bbef3b1</id>
<content type='text'>
calculate_hash() would try to select the appropriate hashing function
by a if/elseif contruct. But that is exactly why hash_lookup_algo()
exists, so use it instead.

This does mean that we now have to 'select HASH' to make sure we get
the hash_lookup_algo() symbol. However, the change makes sense because
even basic FITs will have to deal with "hash" nodes.

My only concern is that the 'select SPL_HASH' might cause some
platform to grow above its SPL size allowance

Signed-off-by: Alexandru Gagniuc &lt;mr.nuke.me@gmail.com&gt;
[trini: Make FSL_CAAM be implied only on ARM &amp;&amp; SPL]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>common/spl: Drop [ST]PL_HASH_SUPPORT in favor of [ST]PL_HASH</title>
<updated>2021-09-08T20:11:46+00:00</updated>
<author>
<name>Alexandru Gagniuc</name>
<email>mr.nuke.me@gmail.com</email>
</author>
<published>2021-09-03T00:54:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=0721209699c5092b4d364c3b57256840d3a7dcbc'/>
<id>urn:sha1:0721209699c5092b4d364c3b57256840d3a7dcbc</id>
<content type='text'>
All of these configs exist. Stick to using CONFIG_[ST]PL_HASH, and drop all
references to CONFIG_[ST]PL_HASH_SUPPORT.  This means we need for
CHAIN_OF_TRUST to select SPL_HASH now.

Signed-off-by: Alexandru Gagniuc &lt;mr.nuke.me@gmail.com&gt;
[trini: Add TPL case, fix CHAIN_OF_TRUST, other tweaks]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>common: Remove unused CONFIG_FIT_SHAxxx selectors</title>
<updated>2021-09-08T20:10:34+00:00</updated>
<author>
<name>Alexandru Gagniuc</name>
<email>mr.nuke.me@gmail.com</email>
</author>
<published>2021-09-03T00:54:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=eb5171ddec9d3b04c2517b60e69dc707e92cf716'/>
<id>urn:sha1:eb5171ddec9d3b04c2517b60e69dc707e92cf716</id>
<content type='text'>
Originally CONFIG_FIT_SHAxxx enabled specific SHA algos for and only
for hash_calculate() in common/image-fit.c. However, since commit
14f061dcb1 ("image: Drop IMAGE_ENABLE_SHAxxx"),
the correct selector was changed to CONFIG_SHAxxx.

The extra "_FIT_" variants are neither used, nor needed. Remove them.
One defconfig disables FIT_SHA256, which is now changed to 'SHA256'.

CMD_MVEBU_BUBT needs to select select SHA256 to avoid undefined
references to "sha256_*()". bubt.c needs sha256, so this selection is
correct. It is not clear why this problem did not manifest before.

Note that SHA selection in SPL is broken for this exact reason. There
is no corresponding SPL_SHAxxx. Fixing this is is beyond the scope of
this change.

Also note that we make CONFIG_FIT now imply SHA256, to make up for
FIT_SHA256 previously being a default y option.

Signed-off-by: Alexandru Gagniuc &lt;mr.nuke.me@gmail.com&gt;
[trini: Add imply SHA256 to FIT]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Kconfig: FIT_SIGNATURE should not select RSA_VERIFY</title>
<updated>2021-08-16T08:49:35+00:00</updated>
<author>
<name>Alexandru Gagniuc</name>
<email>mr.nuke.me@gmail.com</email>
</author>
<published>2021-07-29T16:47:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=61416fe9df966319866f058bb69c49922f33adcb'/>
<id>urn:sha1:61416fe9df966319866f058bb69c49922f33adcb</id>
<content type='text'>
FIT signatures can now be implemented with ECDSA. The assumption that
all FIT images are signed with RSA is no longer valid. Thus, instead
of 'select'ing RSA, only 'imply' it. This doesn't change the defaults,
but allows one to explicitly disable RSA support.

Signed-off-by: Alexandru Gagniuc &lt;mr.nuke.me@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Igor Opaniuk &lt;igor.opaniuk@foundries.io&gt;
Reviewed-by: Patrick Delaunay &lt;patrick.delaunay@foss.st.com&gt;
</content>
</entry>
<entry>
<title>Rename SPL_CRYPTO_SUPPORT to SPL_CRYPTO</title>
<updated>2021-07-28T18:27:54+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-11T03:14:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=0c6bdbb97c5c7d233145de594325b9fbe1beb8bb'/>
<id>urn:sha1:0c6bdbb97c5c7d233145de594325b9fbe1beb8bb</id>
<content type='text'>
Rename this option so that CONFIG_IS_ENABLED can be used with it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>test: add first autoboot unit tests</title>
<updated>2021-07-23T17:36:20+00:00</updated>
<author>
<name>Steffen Jaeckel</name>
<email>jaeckel-floss@eyet-services.de</email>
</author>
<published>2021-07-08T13:57:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=25c8b9f298e46ea6048b5308f7ee207c6461c36a'/>
<id>urn:sha1:25c8b9f298e46ea6048b5308f7ee207c6461c36a</id>
<content type='text'>
This adds tests for the crypt-based and plain SHA256-based password hashing
algorithms in the autoboot flow.

Signed-off-by: Steffen Jaeckel &lt;jaeckel-floss@eyet-services.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>common: add support to fallback to plain SHA256</title>
<updated>2021-07-23T17:36:20+00:00</updated>
<author>
<name>Steffen Jaeckel</name>
<email>jaeckel-floss@eyet-services.de</email>
</author>
<published>2021-07-08T13:57:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=33198740aca2d68e9760cfd6ebb5a55894431966'/>
<id>urn:sha1:33198740aca2d68e9760cfd6ebb5a55894431966</id>
<content type='text'>
In case crypt-based hashing is enabled this will be the default mechanism
that is used. If a user wants to have support for both, the environment
variable `bootstopusesha256` can be set to `true` to allow plain SHA256
based hashing of the password.

Signed-off-by: Steffen Jaeckel &lt;jaeckel-floss@eyet-services.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>common: add AUTOBOOT_FLUSH_STDIN option</title>
<updated>2021-07-23T17:36:20+00:00</updated>
<author>
<name>Steffen Jaeckel</name>
<email>jaeckel-floss@eyet-services.de</email>
</author>
<published>2021-07-08T13:57:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=d199c3ab1c3afa7a17259f4045516f5fbfaaa446'/>
<id>urn:sha1:d199c3ab1c3afa7a17259f4045516f5fbfaaa446</id>
<content type='text'>
The key-sequence based unlock mechanisms are sensitive to junk symbols
that could have been sent to stdin and are still waiting to be retrieved.
Enabling this option will read all symbols off stdin before displaying the
autoboot prompt (and starting to read the password from stdin).

Signed-off-by: Steffen Jaeckel &lt;jaeckel-floss@eyet-services.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>common: allow disabling of timeout for password entry</title>
<updated>2021-07-23T17:36:20+00:00</updated>
<author>
<name>Steffen Jaeckel</name>
<email>jaeckel-floss@eyet-services.de</email>
</author>
<published>2021-07-08T13:57:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=6c0ce6d3ca273f12e1cb4018144bee8e6131d30d'/>
<id>urn:sha1:6c0ce6d3ca273f12e1cb4018144bee8e6131d30d</id>
<content type='text'>
In case a user has to enter a complicated password it is sometimes
desireable to give the user more time than the default timeout.
Enabling this feature will disable the timeout entirely in case the user
presses the &lt;Enter&gt; key before entering any other character.

Signed-off-by: Steffen Jaeckel &lt;jaeckel-floss@eyet-services.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
</feed>
