<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/include/configs, branch next</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/include/configs?h=next</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/include/configs?h=next'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2026-08-25T01:31:25Z</updated>
<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>arm64: renesas: r8a779g3: Switch to distro boot command on Retronix R-Car V4H Sparrow Hawk</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:41:42Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=17baf93381a410b37083abceaa50ac0967a3568e'/>
<id>urn:sha1:17baf93381a410b37083abceaa50ac0967a3568e</id>
<content type='text'>
Switch Retronix R-Car V4H Sparrow Hawk to distro boot command to obtain
generic distro boot capability. The boot scripts now search each of the
SD, NVMe, USB boot devices for either a fitImage with embedded script,
regular boot script, or extlinux.conf, and boot the first one found.
This allows for standardized boot of the device, similar to other such
devices.

There are slight customizations to the distro boot commands, specifically
the PCIe controller is started before USB controller, because the USB
controller is attached to the PCIe controller. Furthermore, USB ethernet
boot is not enabled.

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>arm64: renesas: r8a779g3: Add bootloader update environment on Retronix R-Car V4H Sparrow Hawk</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:41:41Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3511e1e3fbfefa678de083297d8f2a70bab485d2'/>
<id>urn:sha1:3511e1e3fbfefa678de083297d8f2a70bab485d2</id>
<content type='text'>
Add bootloader update environment to Retronix R-Car V4H Sparrow Hawk.
The "update_loader_from_{mmc,nvme,usb}" script updates U-Boot "flash.bin"
in SPI NOR at offset 0x0 from SD card, NVMe SSD and USB mass storage
device respectively. Each script sets up parameters for the generic
update script "update_loader_from_blk", which can be used to update
the "flash.bin" from any block device. The parameters are these:
- renesas_update_loader_iface ....... Update block device (mmc, nvme, usb, ...)
- renesas_update_loader_dev ......... Update block device number (0, 1, ...)
- renesas_update_loader_part ........ Update block device partition (1, 2, ...)
- renesas_update_loader_filename .... Update file name (flash.bin)
- renesas_update_loader_sf_offset ... SPI NOR target offset (0x0)

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>arm64: renesas: r8a779g3: Add PCIe firmware environment on Retronix R-Car V4H Sparrow Hawk</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:41:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9e4253d2dc8eb6c66fe5a429f0f6b003a7fda803'/>
<id>urn:sha1:9e4253d2dc8eb6c66fe5a429f0f6b003a7fda803</id>
<content type='text'>
Add PCIe controller firmware handling environment to Retronix R-Car
V4H Sparrow Hawk. The "renesas_rcar_gen4_load_firmware" script is used
to load PCIe controller firmware from SPI NOR offset 0x300000. The
"flash_pcie_fw_to_qspi_from_mmc" script is used to write the firmware
from SD card to SPI NOR offset 0x300000 .

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>arm: socfpga: n5x: use common soc64 env settings</title>
<updated>2026-08-19T16:36:04Z</updated>
<author>
<name>Tien Fong Chee</name>
<email>tien.fong.chee@altera.com</email>
</author>
<published>2026-08-07T02:48:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=761d3a834f0a3a54fd0d16c21d7f3c6ca8cb5ee1'/>
<id>urn:sha1:761d3a834f0a3a54fd0d16c21d7f3c6ca8cb5ee1</id>
<content type='text'>
Drop the N5X board-local CFG_EXTRA_ENV_SETTINGS override and use the
common SoC64 environment from socfpga_soc64_common.h, matching other
SoC64 boards.

Do not enable CONFIG_DISTRO_DEFAULTS. N5X continues to use the legacy
common env helpers referenced by BOOTCOMMAND (fatscript and mmc* /
mmcfit*) with a board u-boot.scr that only enables the FPGA bridges,
which matches the current N5X SD image layout.

Also set CONFIG_SYS_LOAD_ADDR=0x02000000, matching Agilex/S10, so kernel
and FIT loads sit above the 32 MiB /reserved-memory svcbuffer at 0x0 in
socfpga_agilex.dtsi (included by the N5X board DT). Drop
CONFIG_SYS_BOOTM_LEN=0x2000000 so the ARM64 default (128 MiB) applies;
the previous 32 MiB override is too small for current images.

Tested-on: Intel SoCFPGA N5X SoCDK hardware (ddr retention, linux boot).
Signed-off-by: Tien Fong Chee &lt;tien.fong.chee@altera.com&gt;
Signed-off-by: Chen Huei Lok &lt;chen.huei.lok@altera.com&gt;
</content>
</entry>
<entry>
<title>arm64: versal2: Select GIC redistributor base at runtime</title>
<updated>2026-08-12T04:54:37Z</updated>
<author>
<name>Michal Simek</name>
<email>michal.simek@amd.com</email>
</author>
<published>2026-07-08T06:53:54Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5bca08783b54ce325fb649749de16edede0581d0'/>
<id>urn:sha1:5bca08783b54ce325fb649749de16edede0581d0</id>
<content type='text'>
The GIC redistributor base address depends on the part: the 2VM3654
device has 4 APU cores and 3 GIC ITS blocks, which shifts the
redistributor region up compared to the base 8 core / single ITS part.
A single U-Boot binary must therefore pick the right base at runtime
instead of relying on the compile-time GICR_BASE used by the generic
lowlevel_init().

Add a SoC specific lowlevel_init() that reads the PMC TAP IDCODE and
selects GICR_BASE_2VM3654 for the 2VM3654 device, otherwise keeps the
default GICR_BASE. CONFIG_ARMV8_MULTIENTRY is not supported on Versal
Gen 2 so the generic slave handling is intentionally dropped.

Signed-off-by: Michal Simek &lt;michal.simek@amd.com&gt;
Link: https://patch.msgid.link/4c0dc2b6e29d300db15be0844879ab4d028d98a9.1783493630.git.michal.simek@amd.com
</content>
</entry>
<entry>
<title>Merge patch series "k3-am62-pocketbeagle2: add board and variant support"</title>
<updated>2026-08-11T18:52:16Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-08-11T18:52:16Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2f838307d6bc07416b510524016709798c04712e'/>
<id>urn:sha1:2f838307d6bc07416b510524016709798c04712e</id>
<content type='text'>
Randolph Sapp &lt;rs@ti.com&gt; says:

Resubmitting with a synced rm-cfg.yaml and tuned diff parameters. We desperately
need to add documentation about how the rm-cfg.yaml is generated here. And the
beagleplay needs to get it's rm-cfg resynced with am62x at some point.

Since it's been decided internally to follow along with what Zephyr is doing and
make a completely separate device tree for the 1GB + eMMC Industrial board, I'm
resubmitting v3 with the variant support patch dropped. We will circle back to
enable the Industrial part once the dt has been accepted kernel side.

See the following link for more information regarding that decision:
https://lore.kernel.org/u-boot/DJLTHZL0ERIG.JV1UL67GFIVJ@ti.com/

Add initial board support for the PocketBeagle 2 from BeagleBoard.org. This is
based on the current official series from Robert Nelson [1] and work from Bryan
Brattlof [2].

Now that the various memory issues have been resolved we can clearly see at
runtime that there's an issue with the current device. One of our reservations
overlaps with the u-boot stack. To get around this we'll need to change the
relocation address to something we know will not collide.

[1] https://github.com/beagleboard/u-boot/tree/v2026.01-am62-pocketbeagle2
[2] https://github.com/bryanbrattlof/beagleboot/tree/b4/pb2i

Link: https://lore.kernel.org/r/20260730215319.965327-2-rs@ti.com
</content>
</entry>
<entry>
<title>k3-am62-pocketbeagle2: add support for efi capsules</title>
<updated>2026-08-11T18:51:39Z</updated>
<author>
<name>Randolph Sapp</name>
<email>rs@ti.com</email>
</author>
<published>2026-07-30T21:53:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=6a9d070f8bcece0f8a2c323415684dfcac8c2ad4'/>
<id>urn:sha1:6a9d070f8bcece0f8a2c323415684dfcac8c2ad4</id>
<content type='text'>
Add support for EFI capsules for this device. One large caveat is that
the partition holding boot binaries cannot be the ESP partition due to
the following ROM limitations.

- The boot disk must be MBR
- The boot partition must be labeled 0x0c with a boot flag

A separate ESP partition should be provided for EFI capabilities.

Signed-off-by: Randolph Sapp &lt;rs@ti.com&gt;
</content>
</entry>
<entry>
<title>k3-am62-pocketbeagle2: add initial board support</title>
<updated>2026-08-11T18:51:39Z</updated>
<author>
<name>Randolph Sapp</name>
<email>rs@ti.com</email>
</author>
<published>2026-07-30T21:53:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c9858573fc9344aef90d03fb271d38964b053a0b'/>
<id>urn:sha1:c9858573fc9344aef90d03fb271d38964b053a0b</id>
<content type='text'>
Add initial board support for the PocketBeagle 2, based on Robert Nelson
and Bryan Brattlof's work. Unify all debug consoles to main_uart6. Use
DDR config v10.32 from our sysconfig tool [1] for Kingston's memory [2],
(4Gb Desnity with a CL of 11 and CWL of 9). Add support for the
SPL_TEXT_BASE config parameter. Ensure all files have a summary and SPDX
identifier.

Also, use board_get_usable_ram_top() to fixup our relocaddr since
otherwise the u-boot stack reservation will collide with the
wkup_r5fss0_core0_memory_region.

[1] https://dev.ti.com/sysconfig
[2] https://mm.digikey.com/Volume0/opasdata/d220001/medias/docus/6465/D2516AN9EXGXN-TU.pdf

Signed-off-by: Randolph Sapp &lt;rs@ti.com&gt;
Reviewed-by: Andrew Davis &lt;afd@ti.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'main' of https://git.u-boot-project.org/u-boot/custodians/u-boot-sh</title>
<updated>2026-08-08T18:18:40Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-08-08T18:18:40Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=9167d2079afecfa5881bad8665a2a4636061e3f4'/>
<id>urn:sha1:9167d2079afecfa5881bad8665a2a4636061e3f4</id>
<content type='text'>
This includes temporary U-Boot DT ECC carveouts for R-Car Gen5, they
will be dropped from U-Boot DTs once OF_UPSTREAM DTs get re-synced.
This also includes RPC-IF support for R-Car Gen5 and env storage in RPC
HF.
This also includes an update for R-Car Gen5 UFS controller driver.
</content>
</entry>
</feed>
