diff options
| author | Jason Wessel <jason.wessel@windriver.com> | 2013-10-30 12:35:17 -0500 |
|---|---|---|
| committer | Saul Wold <sgw@linux.intel.com> | 2013-10-31 23:57:04 -0700 |
| commit | 754b52ea7a3cdf8e7e939a314525d16c4dfb52cb (patch) | |
| tree | 875ffc0ddba2c80d4050de490ced5b878eb2b2b6 /meta/site/x86_64-linux | |
| parent | 2d9114aaf130179cb13c20c8b045c2694eca6fd9 (diff) | |
| download | openembedded-core-754b52ea7a3cdf8e7e939a314525d16c4dfb52cb.tar.gz openembedded-core-754b52ea7a3cdf8e7e939a314525d16c4dfb52cb.tar.bz2 openembedded-core-754b52ea7a3cdf8e7e939a314525d16c4dfb52cb.zip | |
grub-efi.bbclass: Fix startup.nsh to work on more EFI revs
Some revs of the EFI firmware + shell do not automatically setup the
path in a such a way as to execute a binary without an absolute
reference like "FS0:\EFI\BOOT\bootx64.efi". All the versions that I
have tested work properly by simply calling the binary which is in the
EFI\BOOT directory by name like "bootx64.efi".
The error you see on the console looks like the following:
startup.nsh> EFI\BOOT\bootx64.efi
'EFI\BOOT\bootx64.efi' is not recognized as an internal or external command, operable program, or batch file
Shell>
This patch simply drops the EFI\BOOT for greater compatibility.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/site/x86_64-linux')
0 files changed, 0 insertions, 0 deletions