Re: [PATCH] bootstd: Scan all bootdevs in a boot_targets entry

Simon Glass
2023-10-13T23:38:15Z

Hi,

On Sat, 23 Sept 2023 at 13:50, Simon Glass <sjg@chromium.org> wrote:
>
> 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>
> ---
>
> boot/bootdev-uclass.c | 3 ++-
> boot/bootflow.c | 21 +++++++++++++++++++--
> test/boot/bootdev.c | 10 ++++++++++
> 3 files changed, 31 insertions(+), 3 deletions(-)

I'm going to pick this one up. There are no formal tested-by tags but
there are two reports on the mailing list that it fixes the problem.
[1] [2]

Regards,
Simon

[1] https://lore.kernel.org/all/ZSMlNWJ9f7HkoaNg@Dell-Inspiron-15/
[2] https://lore.kernel.org/all/VI1PR08MB2847B5EFD8F36E5A4D41FEBD83D2A@VI1PR08MB2847.eurprd08.prod.outlook.com/

Applied to u-boot-dm, thanks!