u-boot/test/boot
Simon Glass e824d0d0c2 bootstd: Scan all bootdevs in a boot_targets entry
When the boot_targets environment variable is used with the distro-boot
scripts, each device is included individually. For example, if there
are three mmc devices, then we will have something like:

   boot_targets="mmc0 mmc1 mmc2"

In contrast, standard boot supports specifying just the uclass, i.e.:

   boot_targets="mmc"

The intention is that this should scan all MMC devices, but in fact it
currently only scans the first.

Update the logic to handle this case, without required BOOTSTD_FULL to
be enabled.

I believe at least three people reported this, but I found two.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reported-by: Date Huang <tjjh89017@hotmail.com>
Reported-by: Vincent Stehlé <vincent.stehle@arm.com>
2023-10-13 10:15:41 -07:00
..
files expo: Update tests to include textline 2023-10-11 15:43:55 -04:00
bootdev.c bootstd: Scan all bootdevs in a boot_targets entry 2023-10-13 10:15:41 -07:00
bootflow.c Prepare v2023.10-rc4 2023-09-04 10:51:58 -04:00
bootmeth.c bootstd: Rename distro and syslinux to extlinux 2023-05-13 09:52:32 -04:00
bootstd_common.c bootstd: Allow hunting for a bootdev by label 2023-01-23 18:11:41 -05:00
bootstd_common.h arm: qemu: Move GUIDs to the C file 2023-02-06 13:04:53 -05:00
cedit.c expo: Update tests to include textline 2023-10-11 15:43:55 -04:00
expo.c expo: Update tests to include textline 2023-10-11 15:43:55 -04:00
image.c image: Add the concept of a phase to FIT 2022-10-31 11:02:44 -04:00
Makefile expo: Move cedit test into its own file and tidy 2023-08-25 13:54:33 -04:00
vbe_fixup.c vbe: Use a manual test 2022-10-31 11:04:00 -04:00
vbe_simple.c vbe: Add info about the VBE device to the fwupd node 2022-10-31 11:04:00 -04:00