mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-01 17:10:11 +00:00
ee2ce29223
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 <mibodhi@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> |
||
---|---|---|
.. | ||
ahci-pci.c | ||
ahci-uclass.c | ||
ahci.c | ||
ahci_mvebu.c | ||
ahci_sunxi.c | ||
dwc_ahci.c | ||
dwc_ahsata.c | ||
dwc_ahsata_priv.h | ||
fsl_sata.c | ||
fsl_sata.h | ||
Kconfig | ||
libata.c | ||
Makefile | ||
mtk_ahci.c | ||
sata.c | ||
sata_bootdev.c | ||
sata_ceva.c | ||
sata_mv.c | ||
sata_sandbox.c | ||
sata_sil.c | ||
sata_sil.h |