GRUB release schedule?

Is there a release schedule for the next stable version of GRUB? It would help for planning purposes. -- Bruce LFS ___ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel

[PATCH v2 7/8] efi: implement LoadFile2 initrd loading protocol for Linux

Recent Linux kernels will invoke the LoadFile2 protocol installed on a well-known vendor media devicepath to load the initrd if it is exposed by the firmware. Using this method is preferred for two reasons: - the Linux kernel is in charge of allocating the memory, and so it can implement any plac

[PATCH v2 6/8] efi: add definition of LoadFile2 protocol

Incorporate the EFI_LOAD_FILE2_PROTOCOL GUID and C types from the UEFI spec. Signed-off-by: Ard Biesheuvel Reviewed-by: Leif Lindholm --- grub-core/commands/efi/lsefi.c | 1 + include/grub/efi/api.h | 15 +++ 2 files changed, 16 insertions(+) diff --git a/grub-core/command

[PATCH v2 5/8] linux/arm: account for COFF headers appearing at unexpected offsets

The way we load the Linux and PE/COFF image headers depends on a fixed placement of the COFF header at offset 0x40 into the file. This is a reasonable default, given that this is where Linux emits it today. However, in order to comply with the PE/COFF spec, which permits this header to appear anywh

[PATCH v2 1/8] linux/arm: fix ARM Linux header layout

The hdr_offset member of the ARM Linux image header appears at offset 0x3c, matching the PE/COFF spec's placement of the COFF header offset in the MS-DOS header. We're currently off by four, so fix that. Signed-off-by: Ard Biesheuvel --- include/grub/arm/linux.h | 2 +- 1 file changed, 1 inserti

[PATCH v2 2/8] loader/linux: permit NULL argument for argv[] in grub_initrd_load()

grub_initrd_load() takes a char *argv[] argument which is only used when an error occurs, to print the name of the file that caused the error. In order to be able to split initrd loading from handling the initrd command, let's permit argv to be NULL, and fall back to the file names recorded in the

[PATCH v2 4/8] linux/arm: unify ARM/arm64 vs Xen PE/COFF header handling

Xen has its own version of the image header, to account for the additional PE/COFF header fields. Since we are adding references to those in the shared EFI loader code, update the common definitions and drop the Xen specific one which no longer has a purpose. Signed-off-by: Ard Biesheuvel --- gr

[PATCH v2 3/8] efi: move MS-DOS stub out of generic PE header definition

The PE/COFF spec permits the COFF signature and file header to appear anywhere in the file, and the actual offset is recorded in 4 byte little endian field at offset 0x3c of the image. When GRUB is emitted as a PE/COFF binary, we reuse the 128 byte MS-DOS stub (even for non-x86 architectures), put

[PATCH v2 0/8] linux: implement LoadFile2 initrd loading

This implements the LoadFile2 initrd loading protocol, which is essentially a callback face into the bootloader to load the initrd data into a caller provided buffer. This means the bootloader no longer has to contain any policy regarding where to load the initrd (which differs between architecture

[PATCH v2 8/8] linux: ignore FDT unless we need to modify it

Now that we implemented support for the LoadFile2 protocol for initrd loading, there is no longer a need to pass the initrd parameters via the device tree. This means there is no longer a reason to update the device tree in the first place, and so we can ignore it entirely. The only remaining reas