On 2026-06-16T06:36:03, None <[email protected]> wrote: > bootdev: scan boot devices at each priority level > > Currently, default 'bootflow scan -lb' will stop booting the board if > any of higher-priority bootdevs fail to be hunted even if there are > bootdevs of lower priority. > > For example, if the board has both NVMe (priority 4) and USB MSD devices > (priority 5), and if NVMe bootdev hunt fails (in the event of a bad NVMe > firmware update), USB (which may be a recovery bootdev) is never hunted > automatically, leaving the board at the U-Boot prompt (user intervention > is needed, e.g. something like 'bootflow scan usb' to hunt USB). > > Fix bootdev_next_prio() to scan bootdevs at the lower priority level by > not exiting the scan loop early. > > Keep the existing logging verbosity unchanged and rely on the failing > subsystem to provide a suitable diagnostic message. > > Signed-off-by: Denis Mukhin <[email protected]> > > boot/bootdev-uclass.c | 2 -- > 1 file changed, 2 deletions(-)
Reviewed-by: Simon Glass <[email protected]>
