From: Nir Lichtman <nir@lichtman.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com
Subject: Re: [PATCH v2] Documentation: Fix x86_64 UEFI outdated references to elilo
Date: Tue, 14 Jan 2025 06:00:29 +0000 [thread overview]
Message-ID: <20250114060029.GA966321@lichtman.org> (raw)
In-Reply-To: <Z4Tj5NyguaU8xoKV@archie.me>
On Mon, Jan 13, 2025 at 04:59:00PM +0700, Bagas Sanjaya wrote:
> On Wed, Jan 08, 2025 at 11:35:22AM +0000, Nir Lichtman wrote:
> > diff --git a/Documentation/arch/x86/x86_64/uefi.rst b/Documentation/arch/x86/x86_64/uefi.rst
> > index fbc30c9a071d..3949d83a9915 100644
> > --- a/Documentation/arch/x86/x86_64/uefi.rst
> > +++ b/Documentation/arch/x86/x86_64/uefi.rst
> > @@ -12,14 +12,19 @@ with EFI firmware and specifications are listed below.
> >
> > 1. UEFI specification: http://www.uefi.org
> >
> > -2. Booting Linux kernel on UEFI x86_64 platform requires bootloader
> > - support. Elilo with x86_64 support can be used.
> > +2. Booting Linux kernel on UEFI x86_64 platform can either be
> > + done using the <Documentation/admin-guide/efi-stub.rst> or using a separate bootloader.
> >
> > 3. x86_64 platform with EFI/UEFI firmware.
> >
[..]
> > - If some or all EFI runtime services don't work, you can try following
> > kernel command line parameters to turn off some or all EFI runtime
> > services.
>
> Looks good, thanks!
>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
Thanks for the review! Small question:
I noticed that there is also a script in the kernel (genimage) which enables
automation of building the image, including an image utilizing the EFI stub.
The EFI stub image can be built by enabling the relavent EFI stub config options
and then running "make hdimage", thing is that I couldn't get the script the to
work yet (stuck on an error about missing EDK2/OMVF), but I could look deeper into
this method as well and add it also to this doc, do you think it is also relavent?
Thanks,
Nir
next prev parent reply other threads:[~2025-01-14 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 11:35 Nir Lichtman
2025-01-13 9:59 ` Bagas Sanjaya
2025-01-14 6:00 ` Nir Lichtman [this message]
2025-01-16 18:22 ` Jonathan Corbet
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=20250114060029.GA966321@lichtman.org \
--to=nir@lichtman.org \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®