All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org, Daniel Kiper <dkiper@net-space.pl>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/2] EFI chainloader improvement
Date: Thu, 25 Aug 2022 23:32:01 -0500	[thread overview]
Message-ID: <cover.1661487848.git.development@efficientek.com> (raw)

This series improves the EFI chainloader. I've noticed for a while now that
chainloading would fail when root=memdisk. It didn't really make sense because
I was specifying the image to chainload as device+path, so why would it care
about what my root was. But I noticed that if I changed the root to the device
the image file was located on, then chainloading worked. The second patch
fixes this by removing some previous assumptions that I don't believe are
valid (eg. that LoadImage needs a valid device path).

Glenn

Glenn Washburn (2):
  efi/chainloader: Do not require a valid $root when chainloading
  docs: Document that extra arguments to chainloader on EFI

 docs/grub.texi                     |  7 +++++--
 grub-core/loader/efi/chainloader.c | 31 +++++++++++-------------------
 2 files changed, 16 insertions(+), 22 deletions(-)

-- 
2.34.1



             reply	other threads:[~2022-08-26  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  4:32 Glenn Washburn [this message]
2022-08-26  4:32 ` [PATCH 1/2] efi/chainloader: Do not require a valid $root when chainloading Glenn Washburn
2022-08-26  9:12   ` Dimitri John Ledkov
2022-08-26 18:02     ` Glenn Washburn
2022-08-26  4:32 ` [PATCH 2/2] docs: Document that extra arguments to chainloader on EFI Glenn Washburn
2022-12-15 21:45 ` [PATCH 0/2] EFI chainloader improvement Glenn Washburn
2023-05-30 14:59 ` Daniel Kiper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1661487848.git.development@efficientek.com \
    --to=development@efficientek.com \
    --cc=ardb@kernel.org \
    --cc=dkiper@net-space.pl \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.