diff options
| author | Michael Walle <michael@walle.cc> | 2020-09-29 08:54:48 +0200 |
|---|---|---|
| committer | Heinrich Schuchardt <xypron.glpk@gmx.de> | 2020-10-06 07:43:56 +0200 |
| commit | f3866909e35074ea6f50226d40487a180de1132f (patch) | |
| tree | eaf219f7c7e61aecde22efdb6c9922a7fa1c12e3 /lib | |
| parent | eb0d1d83994a1e54d6720a6fc8eb1fd3ce2e56a9 (diff) | |
| download | u-boot-f3866909e35074ea6f50226d40487a180de1132f.zip u-boot-f3866909e35074ea6f50226d40487a180de1132f.tar.gz u-boot-f3866909e35074ea6f50226d40487a180de1132f.tar.bz2 | |
distro_bootcmd: call EFI bootmgr even without having /EFI/boot
Currently, the EFI bootmgr is only called if there is a EFI binary
inside the path for removable media is found, i.e. /EFI/boot/. This
doesn't make sense. It is the duty of the bootmgr to find out the
path and name of the EFI binary to boot. It should be called even
if there is no /EFI/boot directory.
Thus, call the bootmgr before we try to boot the EFI binary inside
the removable media path.
Also remove the ${fdtcontroladdr} parameter because the fallback is
handled in cmd/bootefi.c and that already takes care of correct settings
if the board has ACPI and thus no device tree at all.
Signed-off-by: Michael Walle <michael@walle.cc>
Reviewed-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions