diff options
| author | xypron.glpk@gmx.de <xypron.glpk@gmx.de> | 2017-06-20 19:10:27 +0000 |
|---|---|---|
| committer | Alexander Graf <agraf@suse.de> | 2017-07-19 14:14:41 +0200 |
| commit | 70bfcdc6bb6f969babd69efc49e1dc7a1faeca54 (patch) | |
| tree | c799a3c2bc63ba65e76c031e3994414fdba6fca6 /lib/dhry | |
| parent | 1da1bac477581fdb8aa093b6ed842874ffc5916d (diff) | |
| download | u-boot-70bfcdc6bb6f969babd69efc49e1dc7a1faeca54.tar.gz | |
efi_loader: disk: iterate only over valid block devices
The efi_loader currently stops iterating over the available
block devices stopping at the first device that fails.
This may imply that no block device is found.
With the patch efi_loader only iterates over valid devices.
It is based on patch
06d592bf52f6 (dm: core: Add uclass_first/next_device_check())
which is currently in u-boot-dm.git.
For testing I used an odroid-c2 with a dts including
&sd_emmc_a {
status = "okay";
};
This device does not exist on the board and cannot be initialized.
Without the patch:
=> bootefi hello
## Starting EFI application at 01000000 ...
WARNING: Invalid device tree, expect boot to fail
mmc_init: -95, time 1806
Found 0 disks
Hello, world!
## Application terminated, r = 0
With the patch:
=> bootefi hello
## Starting EFI application at 01000000 ...
WARNING: Invalid device tree, expect boot to fail
mmc_init: -95, time 1806
Scanning disk mmc@70000.blk...
Scanning disk mmc@72000.blk...
Card did not respond to voltage select!
mmc_init: -95, time 9
Scanning disk mmc@74000.blk...
Found 3 disks
Hello, world!
## Application terminated, r = 0
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: Andreas Färber <afaerber@suse.de>
Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'lib/dhry')
0 files changed, 0 insertions, 0 deletions