u-boot.git/include/config_distro_bootcmd.h, branch v2026.07

config_distro_bootcmd: do not scan boot partitions if distro_bootpart is defined

2026-04-13T23:34:48Z

For some projects, designing the active bootable partition is done by setting distro_bootpart in the environment instead of changing the bootable flag on the active partition. This patch makes it possible to support both models by scanning boot partitions only if distro_bootpart is not defined in the environment. Signed-off-by: Hugo Villeneuve

config_distro_bootcmd: make possible to substitute 'part list' in distro_bootcmd

2025-05-05T13:51:46Z

Make it possible to substitute the 'part list' command inside 'scan_dev_for_boot_part' with a custom board specific implementation. For this the new define 'SCAN_DEV_FOR_BOOT_PARTS' is introduced. Signed-off-by: Pascal Zimmermann Reviewed-by: Patrice Chotard

Fix EFI boot file name definition for 64-bit x86

2025-04-04T18:26:36Z

This change aligns the preprocessor directive with the standard configuration flag used for detecting 64-bit x86 architecture. Signed-off-by: Jeremy Compostella Reviewed-by: Simon Glass

include: Use CONFIG_XPL_BUILD instead of CONFIG_SPL_BUILD

2024-10-11T17:44:48Z

Use the new symbol to refer to any 'SPL' build, including TPL and VPL Signed-off-by: Simon Glass

config_distro_bootcmd: remove booting environment variables from SPL environment

2023-05-10T20:45:42Z

SPL environments don't need commands that they can never use. Avoid errors with CONFIG_IS_ENABLED conversions by skipping them now. Signed-off-by: Troy Kisky Reviewed-by: Simon Glass

distro_bootcmd: Set distro_bootpart_uuid for block devices

2023-01-12T19:06:16Z

The assignment of block device nodes in Linux is not deterministic by default, i.e. a newly added eMMC controller or other block device can change the assignment of /dev/mmcblkN (or other block device node like e.g. /dev/sdXy) and prevent the system from picking the correct block device for root filesystem in case the root filesystem is specified on kernel command line using 'root=/dev/mmcblkNpM' (or 'root=/dev/sdXy' etc.). One way out is to derive PARTUUID in U-Boot, which is unique identifier of a partition, and pass that as root=PARTUUID= to Linux via kernel command line. Linux would then find the partition using PARTUUID, no matter on which block device the partition resides and which node was assigned to that block device. Derive the PARTUUID before scanning for extlinux presence and assign it into distro_bootpart_uuid environment variable, which can then be used in extlinux.conf kernel command line specifier. Note that it is not possible to do this in scan_dev_for_extlinux script because this script is called from scan_dev_for_boot script, which is called for both block devices as well as UBI volumes, and we can not derive PARTUUID for UBI volumes. Signed-off-by: Marek Vasut

distro_bootcmd: Fix copy-paste error

2023-01-08T13:45:17Z

The "SCRIPT FAILED" string is copied from scan_dev_for_scripts script, update it so it prints "EXTLINUX FAILED" instead in scan_dev_for_extlinux script. Signed-off-by: Marek Vasut

Merge branch 'master' into next

2022-09-19T20:07:12Z

Signed-off-by: Tom Rini

distro_bootcmd: Introduce support for extension command

2022-09-02T16:22:56Z

Try to load required DTB overlays if the board supports extensions and CONFIG_CMD_EXTENSION is enabled. Signed-off-by: Matwey V. Kornilov

distroboot: ubifs: Add support for specifying UBI header offset

2022-08-27T00:45:15Z

Some UBI partitions may use non-standard UBI header offset. For attaching these UBI partitions it is required to pass second argument with offset to "ubi part" command. Therefore extend distroboot to allow specifying additional optional 6th argument with UBI header offset. This offset is set in new distroboot variable ${bootubioff} which may be used by distroboot script to e.g. properly pass this value to linux kernel command line for proper mounting of rootfs by kernel. This variable is set to empty string (cleared) when UBI header offset is not specified into distroboot BOOT_TARGET_DEVICES macro. Usage of helper macro BOOTENV_DEV_UBIFS_BOOTUBIOFF in this change is there as a type check. It ensures that in BOOT_TARGET_DEVICES macro was specified UBIFS func with either 5 or 6 arguments. If not then cpp throws compile error. Signed-off-by: Pali Rohár Reviewed-by: Tom Rini