On Thu, Nov 02, 2023 at 11:51:15AM -0700, Tony Dinh wrote: > During bootstd scanning for bootdevs, if bootdev_hunt_drv() encounters > a device not found error (e.g. ENOENT), let it return a successful status > so that bootstd will continue scanning the next devices, not stopping > prematurely. > > Background: > > During scanning for bootflows, it's possible for bootstd to encounter a > faulty device controller. Also when the same u-boot is used for another > variant of the same board, some device controller such as SATA might > not exist. > > I've found this issue while converting the Marvell Sheevaplug board to > use bootstd. This board has 2 variants, the original Sheevaplug has MMC and > USB only, but the later variant comes with USB, MMC, and eSATA ports. We > have been using the same u-boot (starting with CONFIG_IDE and later with DM > CONFIG_SATA) for both variants. This worked well with the old > envs-scripting booting scheme. > > Signed-off-by: Tony Dinh <mibo...@gmail.com> > Reviewed-by: Simon Glass <s...@chromium.org>
Applied to u-boot/master, thanks! -- Tom
signature.asc
Description: PGP signature
