Skip to contentSkip to conversation

docs: Document extra arguments to chainloader on EFI

PATCH Superseded Glenn Washburn 1 participant 2 messages Dec 15, 2022 – Dec 16, 2022

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 docs: Document extra arguments to chainloader on EFI

Extra arguments given to chainloader on EFI platforms will be sent to the chainloaded application. Also, minor edit in the chainloading section to note that chainloading can be a jump via the firmware and not necessarily in real mode (which does not exist on some achitectures).

---
 docs/grub.texi | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)
docs/grub.texi +5 -2
index 1752fcb7db..536a0e7e37 100644
@@ -979,7 +979,7 @@ invoke shutdown machinery.
 Operating systems that do not support Multiboot and do not have specific
 support in GRUB (specific support is available for Linux, FreeBSD, NetBSD
 and OpenBSD) must be chain-loaded, which involves loading another boot
-loader and jumping to it in real mode.
+loader and jumping to it in real mode or via the firmware.
 
 The @command{chainloader} command (@pxref{chainloader}) is used to set this
 up.  It is normally also necessary to load some GRUB modules and set the
@@ -4050,10 +4050,13 @@ a list of commands that could use more documentation:
 @node chainloader
 @subsection chainloader
 
-@deffn Command chainloader [@option{--force}] file
+@deffn Command chainloader [@option{--force}] file [args...]
 Load @var{file} as a chain-loader. Like any other file loaded by the
 filesystem code, it can use the blocklist notation (@pxref{Block list
 syntax}) to grab the first sector of the current partition with @samp{+1}.
+On EFI platforms, any arguments after @var{file} will be sent to the loaded
+image.
+
 If you specify the option @option{--force}, then load @var{file} forcibly,
 whether it has a correct signature or not. This is required when you want to
 load a defective boot loader, such as SCO UnixWare 7.1.
Signature · 1 line
2.34.1
#1 lore raw

I sent this before realizing that this was already in the EFI chainload patch series and that that series is good (I previously thought that it was the wrong way to fix the issue). So please ignore, unless the EFI chainloader patch is not acceptable.

Glenn

Quoted 40 lines · On Thu, 15 Dec 2022 15:06:53 -0600 Glenn Washburn…

Extra arguments given to chainloader on EFI platforms will be sent to the chainloaded application. Also, minor edit in the chainloading section to note that chainloading can be a jump via the firmware and not necessarily in real mode (which does not exist on some achitectures).

---
 docs/grub.texi | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)
docs/grub.texi +0 -0
index 1752fcb7db..536a0e7e37 100644
@@ -979,7 +979,7 @@ invoke shutdown machinery.
 Operating systems that do not support Multiboot and do not have
 specific support in GRUB (specific support is available for Linux,

FreeBSD, NetBSD and OpenBSD) must be chain-loaded, which involves loading another boot -loader and jumping to it in real mode. +loader and jumping to it in real mode or via the firmware.

The @command{chainloader} command (@pxref{chainloader}) is used to
set this up. It is normally also necessary to load some GRUB modules and set the @@ -4050,10 +4050,13 @@ a list of commands that could use more documentation: @node chainloader
@subsection chainloader

-@deffn Command chainloader [@option{--force}] file
+@deffn Command chainloader [@option{--force}] file [args...]
Load @var{file} as a chain-loader. Like any other file loaded by the filesystem code, it can use the blocklist notation (@pxref{Block list syntax}) to grab the first sector of the current partition with
@samp{+1}. +On EFI platforms, any arguments after @var{file} will be sent to the loaded +image.
+
If you specify the option @option{--force}, then load @var{file}
forcibly, whether it has a correct signature or not. This is required when you want to load a defective boot loader, such as SCO UnixWare 7.1.