<feed xmlns='http://www.w3.org/2005/Atom'>
<title>starfive-tech/u-boot.git/arch/sandbox, 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-08-22T09:04:52+00:00</updated>
<entry>
<title>bootcount: add a new driver with syscon as backend</title>
<updated>2021-08-22T09:04:52+00:00</updated>
<author>
<name>Nandor Han</name>
<email>nandor.han@vaisala.com</email>
</author>
<published>2021-06-10T12:40:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=c50b21b70523939c561d0455a2c423f63a9162ca'/>
<id>urn:sha1:c50b21b70523939c561d0455a2c423f63a9162ca</id>
<content type='text'>
The driver will use a syscon regmap as backend and supports both
16 and 32 size value. The value will be stored in the CPU's endianness.

Signed-off-by: Nandor Han &lt;nandor.han@vaisala.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>dtoc: Support widening a bool value</title>
<updated>2021-08-01T15:05:24+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-29T01:23:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=eec44c7218a3c3ce924a282cc46a59e83feb9de1'/>
<id>urn:sha1:eec44c7218a3c3ce924a282cc46a59e83feb9de1</id>
<content type='text'>
At present if we see 'ranges' property (with no value) we assume it is a
boolean, as per the devicetree spec.

But another node may define 'ranges' with a value, forcing us to widen it
to an int array. At present this is not supported and causes an error.

Fix this and add some test cases.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reported-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>sandbox: Reduce keyed autoboot delay</title>
<updated>2021-08-01T15:05:24+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-24T21:14:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=cb8970092f2cd5f1eaadf7d15d28cb905067e07f'/>
<id>urn:sha1:cb8970092f2cd5f1eaadf7d15d28cb905067e07f</id>
<content type='text'>
The autoboot tests are a recent addition to U-Boot, providing much-needed
coverage in this area.

A side effect of the keyed autoboot test is that this feature is enabled
in sandbox always. This changes the autoboot prompt and confuses the
pytests. Some tests become slower, for example the vboot tests take about
27s now instead of 3s.

We don't actually need this feature enabled to be able to run the tests.
Add a switch to allow sandbox to turn it on and off as needed. Use this
in the one test that needs it.

Add a command-line flag in case this is desired in normal use.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Fixes: 25c8b9f298e ("test: add first autoboot unit tests")
Reviewed-by: Steffen Jaeckel &lt;jaeckel-floss@eyet-services.de&gt;
</content>
</entry>
<entry>
<title>reboot-mode: read the boot mode from RTC memory</title>
<updated>2021-07-23T14:16:39+00:00</updated>
<author>
<name>Nandor Han</name>
<email>nandor.han@vaisala.com</email>
</author>
<published>2021-06-10T13:56:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=c74675bd904b6ce9d5820a80f27793c0583fd54c'/>
<id>urn:sha1:c74675bd904b6ce9d5820a80f27793c0583fd54c</id>
<content type='text'>
RTC devices could provide battery-backed memory that can be used for
storing the reboot mode magic value.

Add a new reboot-mode back-end that uses RTC to store the reboot-mode
magic value. The driver also supports both endianness modes.

Signed-off-by: Nandor Han &lt;nandor.han@vaisala.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>reboot-mode: read the boot mode from GPIOs status</title>
<updated>2021-07-23T14:16:39+00:00</updated>
<author>
<name>Nandor Han</name>
<email>nandor.han@vaisala.com</email>
</author>
<published>2021-06-10T13:56:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=f9db2f16cb6fc7b6d05b0e70de65881bc97ba5c2'/>
<id>urn:sha1:f9db2f16cb6fc7b6d05b0e70de65881bc97ba5c2</id>
<content type='text'>
A use case for controlling the boot mode is when the user wants
to control the device boot by pushing a button without needing to
go in user-space.

Add a new backed for reboot mode where GPIOs are used to control the
reboot-mode. The driver is able to scan a predefined list of GPIOs
and return the magic value. Having the modes associated with
the magic value generated based on the GPIO values, allows the
reboot mode uclass to select the proper mode.

Signed-off-by: Nandor Han &lt;nandor.han@vaisala.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: don't set SA_NODEFER in signal handler</title>
<updated>2021-07-21T16:27:35+00:00</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>xypron.glpk@gmx.de</email>
</author>
<published>2021-07-05T17:43:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=fd25ca3275946476d5c3fa32e3e7e3087fa5c572'/>
<id>urn:sha1:fd25ca3275946476d5c3fa32e3e7e3087fa5c572</id>
<content type='text'>
The sandbox can handle signals. Due to a damaged global data pointer
additional exceptions in the signal handler may occur leading to an endless
loop. In this case leave the handling of the secondary exception to the
operating system.

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: mmc: Support fixed MMC devices</title>
<updated>2021-07-21T16:27:35+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-05T22:32:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=6b165ab2b7b1dc89357afbe86c1977addf5aed3b'/>
<id>urn:sha1:6b165ab2b7b1dc89357afbe86c1977addf5aed3b</id>
<content type='text'>
Add support for reading devicetree flags for MMC devices. With this we
can distinguish between fixed and removable drives. Note that this
information is only available when the device is probed, not when it is
bound, since it is read in the of_to_plat() method. This could be changed
if needed later.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Jaehoon Chung &lt;jh80.chung@samsung.com&gt;
</content>
</entry>
<entry>
<title>sandbox: Use hinting with the display</title>
<updated>2021-07-21T16:27:34+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-05T22:32:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=350b1d3b6830bf7383b7df051521526eb2c0d8c4'/>
<id>urn:sha1:350b1d3b6830bf7383b7df051521526eb2c0d8c4</id>
<content type='text'>
SDL provides a hinting feature which provides a higher-quality image
with the double-display option (-K). Enable it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Add work-around for SDL2 display</title>
<updated>2021-07-21T16:27:34+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-05T22:32:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=fcb7e31082c8abf77f5efac5920093f3bcb5d8ca'/>
<id>urn:sha1:fcb7e31082c8abf77f5efac5920093f3bcb5d8ca</id>
<content type='text'>
At present the display does not show on some machines, e.g. Ubunutu
20.04 but the reason is unknown. Add a work-around until this can be
determined.

Also include more error checking just in case.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>sandbox: Support executables for more phases</title>
<updated>2021-07-21T16:27:34+00:00</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-07-05T22:32:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/starfive-tech/u-boot.git/commit/?id=f178bebf551a43445ba8f1e1a4c1638eff8eb612'/>
<id>urn:sha1:f178bebf551a43445ba8f1e1a4c1638eff8eb612</id>
<content type='text'>
The SPL header has a function for obtaining the phase in capital letters,
e.g. 'SPL'. Add one for lower-case also, as used by sandbox.

Use this to generalise the sandbox logic for determining the filename of
the next sandbox executable. This can provide support for VPL.

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