There may be several distinct bugs involved with #824954. For one, I suspect `grub-install`'s behavior needs to change if EFI variables aren't supported. I use this as a flag which could distinguish installation on top of a full EFI implementation (perhaps Tianocore-derived), versus U-Boot's rather primative EFI implementation.
Notably right now `grub-install` tries to install to /boot/efi/EFI/debian by default. This is appropriate for a full EFI implementation where boot entries can be added by adding variables. Yet with U-Boot's limited implementation, the files must go in EFI/BOOT (--bootloader-id=BOOT). Right now I'm simply trying to figure out what others have done to reuse it for my own purposes. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
