u-boot.git/boot/Kconfig, branch v2025.10

bootstd: rauc: Do not select BOOTMETH_GLOBAL

2025-08-25T16:15:12Z

Since the bootmeth "rauc" is not a global boot method, do not select the corresponding BOOTMETH_GLOBAL option. Signed-off-by: Martin Schwan

riscv: Set SYS_BOOTM_LEN default to 0x4000000

2025-08-14T06:32:00Z

This changes the default value to the most commonly used one among existing defconfigs. Signed-off-by: Martin Herren Acked-by: Michal Simek # xilinx_mbv Reviewed-by: Leo Yu-Chi Liang Reviewed-by: Mattijs Korpershoek

Merge patch series "Improve Verdin AM62P thermal setup by generalizing ft_board_setup_ex()"

2025-07-09T14:40:36Z

João Paulo Gonçalves says: In some use cases, board-specific device tree changes must not be overwritten by system fixups. Although U-Boot provides ft_board_setup_ex() for this purpose, it is currently only used on TI Keystone. This series makes ft_board_setup_ex() a generic option, allowing its use by other architectures and boards. Additionally, considering that Toradex Verdin-AM62P hardware lifetime guarantees are based on a 105°C junction temperature (while TI AM62Px supports up to 125°C), this series implements necessary changes within TI K3 AM62P and Toradex board code. These changes include exporting common fixup device Tree functions used in TI K3 for board-code access and also fixup for AM62P thermal zones to correctly reflect the number of CPU nodes according to the SoC part number. Link: https://lore.kernel.org/r/20250623-am62p-fdt-fixup-trip-points-v1-0-12355eb6a72f@toradex.com

boot: Make ft_board_setup_ex() generic

2025-07-09T14:40:03Z

In some use cases, board-specific device tree changes must not be overwritten by system fixups. Although U-Boot provides ft_board_setup_ex() for this purpose, it is currently only used on TI Keystone. Make ft_board_setup_ex() to be a generic option, allowing its use by other architectures/boards. To maintain backward compatibility, enable it by default on TI Keystone. Signed-off-by: João Paulo Gonçalves

boot/image-android: Workaround kernel/ramdisk invalid addr

2025-06-24T13:54:51Z

Some androidboot image have invalid kernel/ramdisk load addr, force to ignore those value and use loadaddr instead. There is a concern on exposing the whole memory to image loading is dangerous. Also, since it's not always possible to change the load addr by repacking the boot.img (mainly due to AVB signature mismatch), we need a way to use kernel_addr_r and ramdisk_addr_r. Suggested-by: Casey Connolly Reviewed-by: Neil Armstrong Tested-by: Mattijs Korpershoek Signed-off-by: George Chan Link: https://lore.kernel.org/r/20250518-android-boot-v3-1-02c8768e131f@gmail.com Signed-off-by: Casey Connolly

Merge patch series "Consistent Kconfig environment options CONFIG_ENV_ prefix"

2025-06-20T18:57:47Z

Marek Vasut says: Rename the environment related variables and add ENV_ prefix, so that all configuration options which are related to environment would have an CONFIG_ENV_ prefix. No functional change. Link: https://lore.kernel.org/r/20250609192701.20260-1-marek.vasut+renesas@mailbox.org

env: Rename DEFAULT_ENV_FILE to ENV_DEFAULT_ENV_TEXT_FILE

2025-06-20T18:15:08Z

Rename the variable and add ENV_ prefix, so that all configuration options which are related to environment would have an CONFIG_ENV_ prefix. No functional change. Also rename USE_DEFAULT_ENV_FILE to USE_ENV_DEFAULT_ENV_TEXT_FILE . Signed-off-by: Marek Vasut

Merge patch series "bootstd: New bootmeth for RAUC A/B systems"

2025-06-18T21:54:33Z

Martin Schwan says: This series implements a new bootmeth for RAUC A/B systems. RAUC (Robust Auto Update Controller) is a lightweight update client, providing "Safe and Secure OTA Updates for Embedded Linux". See the following links for more information about RAUC: https://rauc.io/ https://rauc.readthedocs.io/en/latest/ PHYTEC uses RAUC in its Yocto based distribution "Ampliphy" as the default way of updating embedded devices based on PHYTEC hardware. So far, the logic selecting the correct partitions and files to boot was being implemented in the U-Boot environment. While this is a straightforward way to do it, adding and supporting new platforms became somewhat tedious and is platform-specific. The introduction of U-Boot's "Standard Boot" provided a convincing alternative, promising a simpler and more portable way of booting, even for RAUC systems. This led me to implement a new bootmeth supporting RAUC A/B systems. Note, that this new bootmeth is not proprietary to PHYTEC products and is designed to work on other hardware with a RAUC A/B system, too. The bootmeth currently only supports symmetric A/B partitioning layouts. E.g. A/rescue is not (yet) supported. The partition indexes and default slot tries can be specified via configuration options. For now, the bootmeth_rauc uses a similar approach for loading the Kernel and device tree as the bootmeth_script, in that it requires a FIT containing a U-Boot script loading the desired distro. It could be possible to support booting without a script and load the Kernel and DT directly with this bootmeth, but I found the script method to be very flexible for now, in letting the distro decide what to load. The bootmeth_rauc was tested on a phyBOARD-Pollux i.MX8M Plus [1] with BSP-Yocto-Ampliphy-i.MX8MP-PD24.1.2 [2]. Supported boot devices are currently only MMC devices, but it should be possible to add SPI flashes in the future. To test this patch stack with PHYTEC's phyBOARD-Pollux i.MX8M Plus board, you need to adjust the boot files to include the boot.scr.uimg containing the distro's boot script and set "optargs" to "${raucargs}" in it. Also disable any legacyboot in the U-Boot environment and simply boot with Standard Boot: bootmeth order rauc bootflow scan -lb [1]: https://www.phytec.eu/en/produkte/single-board-computer/phyboard-pollux/ [2]: https://download.phytec.de/Software/Linux/BSP-Yocto-i.MX8MP/BSP-Yocto-Ampliphy-i.MX8MP-PD24.1.2/ Link: https://lore.kernel.org/r/20250604-wip-bootmeth-rauc-v3-0-f9fad913c57e@phytec.de [trini: Don't enable by default]

bootstd: Add implementation for bootmeth rauc

2025-06-18T18:15:35Z

Add a bootmeth driver which supports booting A/B system with RAUC as their update client. Signed-off-by: Martin Schwan Tested-by: Wadim Egorov

bootstd: Rework BLK dependency

2025-05-06T21:47:36Z

The bootstd code itself does not have any dependency on BLK in order to build. However, in order to minimize size growth of non-migrated platforms, change this from being "default y" to "default y if BLK". This will make it easier to begin migration of platforms which do not have any BLK-class device but do want to use bootstd. Signed-off-by: Tom Rini