mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Nir Lichtman <nir@lichtman.org>,
	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: Mon, 13 Jan 2025 16:59:00 +0700	[thread overview]
Message-ID: <Z4Tj5NyguaU8xoKV@archie.me> (raw)
In-Reply-To: <20250108113522.GA897677@lichtman.org>

[-- Attachment #1: Type: text/plain, Size: 2963 bytes --]

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.
>  
>  Mechanics
>  ---------
>  
> +Refer to <Documentation/admin-guide/efi-stub.rst> to learn how to use the EFI stub.
> +
> +Below are general EFI setup guidelines on the x86_64 platform,
> +regardless of whether you use the EFI stub or a separate bootloader.
> +
>  - Build the kernel with the following configuration::
>  
>  	CONFIG_FB_EFI=y
> @@ -31,16 +36,27 @@ Mechanics
>  	CONFIG_EFI=y
>  	CONFIG_EFIVAR_FS=y or m		# optional
>  
> -- Create a VFAT partition on the disk
> -- Copy the following to the VFAT partition:
> +- Create a VFAT partition on the disk with the EFI System flag
> +    You can do this with fdisk with the following commands:
> +
> +        1. g - initialize a GPT partition table
> +        2. n - create a new partition
> +        3. t - change the partition type to "EFI System" (number 1)
> +        4. w - write and save the changes
> +
> +    Afterwards, initialize the VFAT filesystem by running mkfs::
> +
> +        mkfs.fat /dev/<your-partition>
> +
> +- Copy the boot files to the VFAT partition:
> +    If you use the EFI stub method, the kernel acts also as an EFI executable.
> +
> +    You can just copy the bzImage to the EFI/boot/bootx64.efi path on the partition
> +    so that it will automatically get booted, see the <Documentation/admin-guide/efi-stub.rst> page
> +    for additional instructions regarding passage of kernel parameters and initramfs.
>  
> -	elilo bootloader with x86_64 support, elilo configuration file,
> -	kernel image built in first step and corresponding
> -	initrd. Instructions on building elilo and its dependencies
> -	can be found in the elilo sourceforge project.
> +    If you use a custom bootloader, refer to the relevant documentation for help on this part.
>  
> -- Boot to EFI shell and invoke elilo choosing the kernel image built
> -  in first step.
>  - 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>

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-01-13  9:59 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 [this message]
2025-01-14  6:00   ` Nir Lichtman
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=Z4Tj5NyguaU8xoKV@archie.me \
    --to=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=nir@lichtman.org \
    --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®