aboutsummaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorWarner Losh <imp@FreeBSD.org>2020-10-09 00:16:26 +0000
committerWarner Losh <imp@FreeBSD.org>2020-10-09 00:16:26 +0000
commitc6d56081c9dca474130c0b34c39451b21c55102f (patch)
tree21fa9d1b9a5feae127c01c796a5314fff9a19058 /Makefile
parent42f96162c3d648ea4302dbb4c28b1edf1da3651b (diff)
downloadsrc-c6d56081c9dca474130c0b34c39451b21c55102f.tar.gz
src-c6d56081c9dca474130c0b34c39451b21c55102f.zip
Initial support for implementing the bootXXX.efi workaround
Too many version of UEFI firmware (so far only confirmed on amd64) don't really support efibootmgr selection of boot. That's the most reliable, when it works, since there's no guesswork. However, many do not save, unmolested, the variables that efibootmgr sets, so as a fallback we also install loader.efi as bootXXX.efi (where XXX is either aa64 or x64) if it doesn't already exist in /efi/boot on the ESP. The standard only defines this for removable devices, but it's almost ubiquitously used as a fallback. Many BIOSes implement a drive selection feature that takes over the efibootmgr protocol, rendinering it useless (either generally, or for those vendors not on the short list). bootxxx.efi works around this. However, we don't install it unconditionally there, as that breaks some popular multi-boot setups. MFC After: 1 week Differential Revision: https://reviews.freebsd.org/D26428
Notes
Notes: svn path=/head/; revision=366554
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions