u-boot.git/configs, branch v2025.04

x86: emulation: Disable bloblist for now

2025-04-06T16:02:49Z

As reported by Niklas Sombert, enabling bloblist on these platforms means that we currently don't pass SMBIOS tables on to later stages. For the v2025.04 release, disable bloblists as that is sufficient to restore functionality and we will address the underlying problem for the next release. Link: https://lore.kernel.org/u-boot/c1dc7446-d1d0-4ef2-b201-09fc612aa8db@uni-duesseldorf.de Reported-by: Niklas Sombert Signed-off-by: Tom Rini

configs: sama5d27: Fix the 'reset' command

2025-04-01T08:36:35Z

Since commit 61040097a9d1 ("reset: at91: Add reset driver for basic assert/deassert operations") the "atmel,sama5d3-rstc" compatible for the sama5d2 reset controller in sama5d2.dtsi is not handled by CONFIG_SYSRESET_AT91 anymore, but by CONFIG_RESET_AT91 now. This resulted in the following error, when trying to reset from the U-Boot shell on a sama5d27_wlsom1 board: => reset resetting ... System reset not supported on this platform ### ERROR ### Please RESET the board ### Fix it by enabling the CONFIG_RESET_AT91 driver in all sama5d27 defconfigs. Tested on a sama5d27_wlsom1 board. Based on the fix in commit e1ee52ca56fc ("configs: at91: sam9x60: Switch to new reset driver") Fixes: 61040097a9d1 ("reset: at91: Add reset driver for basic assert/deassert operations") Signed-off-by: Fabio Estevam

arm64: renesas: Enable fallback PSCI on Renesas R-Car R8A779G0 V4H White Hawk

2025-03-16T13:47:28Z

Enable fallback PSCI provider on Renesas R-Car R8A779G0 V4H White Hawk board. This fallback PSCI provider provides basic PSCI interface which can be used by the Linux kernel, but does not provide support for bringing up additional CPU cores or any other functionality, except for SoC level reset. This fallback PSCI provider is intended as a fallback in case a proper PSCI provider is not started before the Linux kernel is started. Linux kernel on ARMv8a will fail to boot in case a PSCI provider is not available, and this basic fallback PSCI provider assures such a boot failure cannot occur, even if that means the system will boot in degraded mode with only one CPU core available, that is still sufficient to perform recovery. In the common case, a proper PSCI provider should be started as part of the Linux kernel fitImage, as the BL31 loadable, and replace this basic fallback PSCI provider before the Linux kernel is started. Signed-off-by: Marek Vasut

configs: Resync with savedefconfig

2025-03-10T23:31:22Z

Resync all defconfig files using qconfig.py Signed-off-by: Tom Rini

Merge tag 'xilinx-for-v2025.04-rc4' of https://source.denx.de/u-boot/custodians/u-boot-microblaze

2025-03-05T18:11:18Z

AMD/Xilinx changes for v2025.04-rc4 Zynq: - Guard code around SPL_FS_LOAD_PAYLOAD_NAME Versal*: - Remove tftp block size 4096 Versal: - Use clocks per DT binding - Store driver data in data section Versal Gen 2: - Fix major/minor version decoding

xilinx: Remove tftp block size 4096

2025-03-05T11:42:34Z

The zynqmp gem driver support max MTU size 1536, so remove tftp block size 4096 from defconfig and use default tftp block size. Fixes: a33b4b96b3cf ("xilinx: Enable MBEDTLS/LWIP/WGET and WGET_HTTPS") Signed-off-by: Padmarao Begari Link: https://lore.kernel.org/r/20250304043030.2344536-1-padmarao.begari@amd.com Signed-off-by: Michal Simek

samsung: snow: Use BLOBLIST_FIXED

2025-03-04T14:22:10Z

Snow requires a fixed bloblist to operate, so re-enable this option. Signed-off-by: Simon Glass Fixes: 864106f3c47 ("bloblist: Make BLOBLIST_ALLOC the default")

rockchip: nanopi-r3s-rk3566: disable unneeded CONFIG_NVME_PCI

2025-02-28T11:21:17Z

This board does not have any NVMe slot, so disable unneeded CONFIG_NVME_PCI option. Fixes: bf4a33e725ae ("board: rockchip: add FriendlyElec NanoPi R3S") Signed-off-by: Tianling Shen Reviewed-by: Quentin Schulz Reviewed-by: Kever Yang

rockchip: rk3308-rock-s0: Fix SD-card boot on v1.1 hw revision

2025-02-28T11:13:50Z

BootROM leave GPIO4_D6 configured as SDMMC_PWREN function and DW MMC driver set PWREN high in dwmci_init(). However, HW revision prior to v1.2 must pull GPIO4_D6 low to access sdmmc. For HW revision v1.2 the state of GPIO4_D6 has no impact. Upstream Linux commit 26c100232b09 "arm64: dts: rockchip: Fix sdmmc access on rk3308-rock-s0 v1.1 boards" fixed this issue by adding a vcc_sd regulator. Include the new vcc_sd regulator in SPL and enable required Kconfig options to set GPIO4_D6 low to fix reading sdmmc on v1.1 hw revision. Fixes: 25438c40a007 ("board: rockchip: Add Radxa ROCK S0") Signed-off-by: Jonas Karlman Reviewed-by: Quentin Schulz Reviewed-by: Kever Yang

imx8mm: imx8mm_evk: fix BOOTSTD boot

2025-02-27T11:14:37Z

Select BOOTSTD_FULL and BOOTSTD_BOOTCOMMAND Correct DEFAULT_FDT_FILE Correct env file for imx8mm_evk_fspi_defconfig Fixes: 364ba68ed1a ("imx: imx8mm_evk: Switch to BOOTSTD") Reported-by: Ludwig Nussel Signed-off-by: Peng Fan