Re: [PATCH v3 3/7] efi: implemented LoadFile2 initrd loading protocol for Linux

On Thu, Oct 28, 2021 at 11:31:16PM +0300, Nikita Ermakov wrote: > From: Ard Biesheuvel > > Recent Linux kernels will invoke the LoadFile2 protocol installed on > a well-known vendor media path to load the initrd if it is exposed by > the firmware. Using this method is preferred for two reasons: >

Re: [PATCH] grub-install: check for arm-efi as a default target

On Thu, Feb 21, 2019 at 3:54 PM Steve McIntyre <93...@debian.org> wrote: > > On Thu, Feb 21, 2019 at 03:23:55PM +0100, dann frazier wrote: > >On Thu, Feb 21, 2019 at 12:42 PM Leif Lindholm > >wrote: > >> > >> Hi Steve, > >> > >> On

Re: [PATCH] grub-install: check for arm-efi as a default target

On Thu, Feb 21, 2019 at 12:42 PM Leif Lindholm wrote: > > Hi Steve, > > On Mon, Feb 11, 2019 at 02:42:34AM +, Steve McIntyre wrote: > > Much like on x86, we can work out if the system is running on top of > > EFI firmware. If so, return "arm-efi". If not, fall back to > > "arm-uboot" as previo

[RFC][PATCH 1/2] Factor out EFI detection into its own function

From: dann frazier No functional change. This will let us re-use the code for ARM. Signed-off-by: dann frazier --- grub-core/osdep/linux/platform.c | 20 grub-core/osdep/windows/platform.c | 10 -- 2 files changed, 24 insertions(+), 6 deletions(-) diff --git a

[RFC][PATCH 2/2] arm: grub-install: Default to arm-efi target in EFI-based QEMU virt models

From: dann frazier We currently default to the arm-uboot target in grub-install, but arm-efi should be used for some systems with UEFI firmware, such as Tianocore/EDK2-based QEMU models. We could change the default to arm-efi anytime we successfully probe for an EFI runtime. However, that would

[RFC][PATCH 0/2] grub-install: Use arm-efi target EFI-mode QEMU virt machines

boot/modinfo.sh doesn't exist. Please specify --target or --directory This series avoids that by whitelisting EFI-based linux/virt platforms. dann frazier (2): Factor out EFI detection into its own function arm: grub-install: Default to arm-efi target in EFI-based QEMU virt mode

[PATCH] grub-reboot: Warn when "for the next boot only" promise cannot be kept

2/msg00276.html Ref: https://bugs.launchpad.net/bugs/788298 Signed-off-by: dann frazier --- util/grub-reboot.in | 16 1 file changed, 16 insertions(+) diff --git a/util/grub-reboot.in b/util/grub-reboot.in index 4d4f75704..ef3b5c049 100644 --- a/util/grub-reboot.in +++ b/util/grub

[PATCH] Revert "Keep the native terminal active when enabling gfxterm"

reverts commit 52ef7b23f528ce844716661d586497a177e80d5b. Signed-off-by: dann frazier --- util/grub.d/00_header.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/util/grub.d/00_header.in b/util/grub.d/00_header.in index 8d46fc973..93a90233e 100644 --- a/util/grub.d/00_header.in

[PATCH] Keep the native terminal active when enabling gfxterm

grub-mkconfig will set GRUB_TERMINAL_OUTPUT to "gfxterm" unless the user has overridden it. On EFI systems, this will stop output from going to the default "console" terminal. When the EFI fw console is configured to output to both serial and video, this will cause GRUB to only display on video - w

Re: [PATCH] Avoid NULL pointer dereference in progress module.

On Fri, Aug 21, 2015 at 8:24 AM, Dann Frazier wrote: > On Thu, Aug 20, 2015 at 11:55 AM, Andrei Borzenkov > wrote: >> 18.08.2015 00:57, dann frazier пишет: >>> >>> grub_net_fs_open() saves off a copy of the file structure it gets passed >>> and >>&

Re: [PATCH] Avoid NULL pointer dereference in progress module.

On Thu, Aug 20, 2015 at 11:55 AM, Andrei Borzenkov wrote: > 18.08.2015 00:57, dann frazier пишет: >> >> grub_net_fs_open() saves off a copy of the file structure it gets passed >> and >> uses it to create a bufio structure. It then overwrites the passed in file >&

Re: [PATCH] [RFC] Add exitcode support

On Tue, Aug 18, 2015 at 1:17 PM, Ben Hildred <426...@gmail.com> wrote: > > > On Tue, Aug 18, 2015 at 12:56 PM, Dann Frazier > wrote: >> >> On Tue, Aug 18, 2015 at 12:03 PM, Ben Hildred <426...@gmail.com> wrote: >> > I only briefly scanned

Re: [PATCH] [RFC] Add exitcode support

do think I prefer passing down an abstract request to the low level grub_exit() function vs. a series of platform-specific variables because it gives the platform code the ability to execute additional code if necessary - e.g. setting fw environment variable. -dann > On Tue, Aug 18, 2015 at 11

[PATCH] [RFC] Add exitcode support

entry (presumably an on-disk OS), providing something akin to pxelinux's "localboot". The implementation here is to add a new optional argument to the exit command. The platform-specific grub_exit() implementations can then translate it into a platform-appropriate exit code. Signed-

[PATCH] Avoid NULL pointer dereference in progress module.

is could occur if grub_strdup() fails in grub_file_open(). Signed-off-by: dann frazier --- grub-core/lib/progress.c | 3 +-- grub-core/net/net.c | 14 +- 2 files changed, 14 insertions(+), 3 deletions(-) diff --git a/grub-core/lib/progress.c b/grub-core/lib/progress.c index 63a

Re: [PATCH] progress: Check for NULL filename

On Thu, Aug 13, 2015 at 10:52:19AM +0300, Andrei Borzenkov wrote: > On Wed, Aug 12, 2015 at 6:53 PM, dann frazier > wrote: > > Avoid a NULL pointer dereference if the upper fs layer hasn't set the > > file->name field. Files opened through the grub_net_fs interface curr

[PATCH] progress: Check for NULL filename

Avoid a NULL pointer dereference if the upper fs layer hasn't set the file->name field. Files opened through the grub_net_fs interface currently do not have this field set (though perhaps they should?). Signed-off-by: dann frazier --- grub-core/lib/progress.c | 3 +-- 1 file ch

[PATCH] arm64/setjmp: Add missing license macro

Including the setjmp module in an arm64-efi image will cause it to immediately exit with an "incompatible license" error. The source file includes a GPLv3+ boilerplate, so fix this by declaring a GPLv3+ license using the GRUB_MOD_LICENSE macro. Signed-off-by: dann frazier --- gru