<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/doc, branch next</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/doc?h=next</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/doc?h=next'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2026-08-29T15:56:00Z</updated>
<entry>
<title>Merge tag 'u-boot-rockchip-2027.01-20260828' of https://git.u-boot-project.org/u-boot/custodians/u-boot-rockchip into next</title>
<updated>2026-08-29T15:56:00Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-08-29T15:56:00Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=856a00aeb61c1d4e7825257e54219599f8e34a6c'/>
<id>urn:sha1:856a00aeb61c1d4e7825257e54219599f8e34a6c</id>
<content type='text'>
- Fixed possible SPI hangs when only PICO is routed (TX-only),
- Added support for ROC-RK3399-PC-PLUS (via roc-pc-rk3399_defconfig)
</content>
</entry>
<entry>
<title>test/py: nand: Add tests for NAND flash device</title>
<updated>2026-08-28T20:57:37Z</updated>
<author>
<name>Love Kumar</name>
<email>love.kumar@amd.com</email>
</author>
<published>2026-08-18T10:16:27Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=043b4280138d45c50340c0f899935b83be4375b7'/>
<id>urn:sha1:043b4280138d45c50340c0f899935b83be4375b7</id>
<content type='text'>
Add tests for nand commands to test various NAND flash operations such
as erase, write and read. Use the current test/py APIs (ubman fixture
and utils helpers) and refactor the pre-command helper to return a
dictionary.

Also add the test_nand.py test to the generated documentation. See
commit 8f8f0f0ed9d0 ("doc: pytest: Document the test_net_boot test")
for the kinds of changes required for the docstring to be rendered
correctly.

Signed-off-by: Love Kumar &lt;love.kumar@amd.com&gt;
</content>
</entry>
<entry>
<title>tools: fit: sign all config image references</title>
<updated>2026-08-25T23:12:40Z</updated>
<author>
<name>James Hilliard</name>
<email>james.hilliard1@gmail.com</email>
</author>
<published>2026-08-10T23:43:07Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f252d228be2b2d180737ad0a851f91749273cbd9'/>
<id>urn:sha1:f252d228be2b2d180737ad0a851f91749273cbd9</id>
<content type='text'>
Target-side configuration verification builds the signed-region list from
every image-reference property in the selected configuration. Host-side
signing still uses either the signature node sign-images property or the
legacy kernel/fdt/script default list.

This lets mkimage generate configuration signatures which U-Boot cannot
verify when the configuration references other image types, such as
firmware, loadables or ramdisk entries. It also lets the host and target
disagree when sign-images names only a subset of the configuration images.

Build the host-side signing list from the configuration properties in the
same way as target-side verification. Use one shared property classifier so
the host and target cannot drift apart again. This makes signed
configurations cover the root node, the configuration node, every
referenced image node, and its hash, cipher and dm-verity subnodes,
regardless of image type.

Warn when a legacy sign-images property is present, since it no longer
limits the signed image list. Require every referenced image to have at
least one hash subnode. Add sandbox coverage proving that a firmware
reference omitted from sign-images is still recorded in hashed-nodes and
verified.

Update the signed-configuration documentation to describe the same rule and
the hash-subnode requirement.

Fixes: 2092322b31cc ("boot: Add fit_config_get_hash_list() to build signed node list")
Signed-off-by: James Hilliard &lt;james.hilliard1@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'v2026.10-rc3' into next</title>
<updated>2026-08-25T01:31:25Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-08-25T01:31:25Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=286b8d68f521c601f103ab70ee79e339b838d531'/>
<id>urn:sha1:286b8d68f521c601f103ab70ee79e339b838d531</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Prepare v2026.10-rc3</title>
<updated>2026-08-25T00:46:24Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-08-25T00:46:24Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=964ad5b5c91b7be56e443e899d7f873e6aa8c9fc'/>
<id>urn:sha1:964ad5b5c91b7be56e443e899d7f873e6aa8c9fc</id>
<content type='text'>
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>doc: ti: k3: Fix pseudo DTS syntax</title>
<updated>2026-08-22T21:58:05Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut+renesas@mailbox.org</email>
</author>
<published>2026-08-08T21:45:36Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a24415ab6761f3c24566f0ef0e96c0577b00310a'/>
<id>urn:sha1:a24415ab6761f3c24566f0ef0e96c0577b00310a</id>
<content type='text'>
The code block does not use valid DTS syntax, but rather a pseudo
DTS syntax. Sphinx complains about this, so fix the syntax.

"
doc/board/ti/k3.rst:467: WARNING: Lexing literal_block '/dts-v1/;...};'
as "dts" resulted in an error at token: 'i'. Retrying in relaxed mode.
[misc.highlighting_failure]
"

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'u-boot-dfu-next-20260819' of https://git.u-boot-project.org/u-boot/custodians/u-boot-dfu into next</title>
<updated>2026-08-20T19:37:09Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-08-20T19:26:51Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=93d858da82ea0fa551af9aa6d50ef57fa94c5c49'/>
<id>urn:sha1:93d858da82ea0fa551af9aa6d50ef57fa94c5c49</id>
<content type='text'>
CI: https://git.u-boot-project.org/u-boot/custodians/u-boot-dfu/-/pipelines/1016

u-boot-dfu-next-20260819

Android:
* avb: Make the AVB root key source pluggable
* avb: Add OP-TEE root key digest provider
* avb: Add board-specific root key provider
* avb: Update docs for root key source
</content>
</entry>
<entry>
<title>doc: board: renesas: Document Retronix R-Car Gen4 V4H Sparrow Hawk SPI NOR layout</title>
<updated>2026-08-20T18:15:23Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut+renesas@mailbox.org</email>
</author>
<published>2026-08-09T01:35:31Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f5b3b60e42553d49a7a7d19eaec66770e11534f7'/>
<id>urn:sha1:f5b3b60e42553d49a7a7d19eaec66770e11534f7</id>
<content type='text'>
Document the SPI NOR layout, placement of U-Boot bootloader,
U-Boot environment and optional PCIe controller firmware.

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>rockchip: rk3399: Add ROC-PC-PLUS board detection</title>
<updated>2026-08-19T12:07:47Z</updated>
<author>
<name>Fabio Estevam</name>
<email>festevam@nabladev.com</email>
</author>
<published>2026-08-13T17:02:45Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=66ecacc5e4a3afa547244ce9c68937023188340a'/>
<id>urn:sha1:66ecacc5e4a3afa547244ce9c68937023188340a</id>
<content type='text'>
The ROC-RK3399-PC has an MP8859 regulator on I2C7 at address 0x66,
while the ROC-RK3399-PC-PLUS does not. Probe for the regulator in SPL
and use the result to select the matching devicetree from the U-Boot
FIT. Fall back to the original board if the I2C bus cannot be probed.

Build both devicetrees from the existing roc-pc-rk3399_defconfig and
enable the XMC SPI NOR driver used by the Plus variant. Set fdtfile
from the selected U-Boot devicetree so the matching Linux devicetree
is used as well.

Signed-off-by: Fabio Estevam &lt;festevam@nabladev.com&gt;
Reviewed-by: Quentin Schulz &lt;quentin.schulz@cherry.de&gt;
Link: https://patch.msgid.link/20260813170246.110899-3-festevam@gmail.com
Signed-off-by: Quentin Schulz &lt;u-boot@0leil.net&gt;
</content>
</entry>
<entry>
<title>doc: board: toradex: add the Colibri VF50/VF61 page</title>
<updated>2026-08-14T19:20:55Z</updated>
<author>
<name>Mehmet Fide</name>
<email>mehmet.fide@screeningeagle.com</email>
</author>
<published>2026-08-14T08:17:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=26e89c6268273a9ca4c2784788cdb502d73f25da'/>
<id>urn:sha1:26e89c6268273a9ca4c2784788cdb502d73f25da</id>
<content type='text'>
The other Toradex modules are documented here, the Vybrid ones were
not. Describe the build, the two ways of getting the image into NAND,
and the flashloader command of the WinCE-era bootloader that modules
from that era still carry.

Acked-by: Francesco Dolcini &lt;francesco.dolcini@toradex.com&gt;
Signed-off-by: Mehmet Fide &lt;mehmet.fide@screeningeagle.com&gt;
</content>
</entry>
</feed>
