On 2/20/20 12:06 PM, Ard Biesheuvel wrote:
After having added new ways to load the initrd and the mixed mode kernel,
we will need to tell the loader about this, so it can use the new, generic
method if supported, and fall back to the existing method(s) otherwise.
This is an RFC - if there are better ways to record this in the image
somehow, please shout.
Hello Ard,
for boot loaders like GRUB I understand that the boot loader could use
the initrd file path from its scripts to prepare a
EFI_LOAD_FILE2_PROTOCOL matching the loaded kernel.
I am not sure about the requirements for a firmware.
Up to now the U-Boot UEFI sub-system does not care about initial RAM
disk images at all. With Ilias suggested patch series U-Boot could offer
a file from a fixed file location via a EFI_LOAD_FILE2_PROTOCOL.
Is there anything else you expect a firmware like U-Boot or EDK2 to do?
Best regards
Heinrich
Cc: lersek@xxxxxxxxxx
Cc: leif@xxxxxxxxxxxx
Cc: pjones@xxxxxxxxxx
Cc: mjg59@xxxxxxxxxx
Cc: agraf@xxxxxxxxx
Cc: ilias.apalodimas@xxxxxxxxxx
Cc: xypron.glpk@xxxxxx
Cc: daniel.kiper@xxxxxxxxxx
Cc: nivedita@xxxxxxxxxxxx
Cc: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx
Ard Biesheuvel (3):
efi/x86: Use symbolic constants in PE header instead of bare numbers
efi/libstub: Introduce symbolic constants for the stub major/minor
version
efi: Bump the Linux EFI stub major version number to #1
arch/arm/boot/compressed/efi-header.S | 4 +-
arch/arm64/kernel/efi-header.S | 4 +-
arch/x86/boot/header.S | 64 ++++++++++----------
include/linux/pe.h | 21 +++++++
4 files changed, 58 insertions(+), 35 deletions(-)
