[PATCH v2 5/5] doc: efi: add efi armv8 documentaion.
Ahmad Fatoum
a.fatoum at pengutronix.de
Fri Dec 12 06:06:38 PST 2025
On 12/12/25 6:08 AM, chalianis1 at gmail.com wrote:
> From: Chali Anis <chalianis1 at gmail.com>
>
> Signed-off-by: Chali Anis <chalianis1 at gmail.com>
Reviewed-by: Ahmad Fatoum <a.fatoum at pengutronix.de>
Just a comment below:
> -name it ``BOOTx64.EFI`` on 64bit architectures and ``BOOTIA32.EFI`` on 32bit
> -architectures. Switching to USB boot in the BIOS should then be enough to
> +name it, for x86 ``BOOTx64.EFI`` or ``BOOTIA32.EFI`` on 64bit or 32bit
> +architectures recpectivly, for armv8 ``BOOTAA64.EFI``.
Maybe mention CONFIG_EFI_PAYLOAD_DEFAULT_PATH, which will have the name
depending on architecture?
> +Switching to USB boot in the BIOS should then be enough to
> start barebox via USB. Some BIOSes allow to specify a path to a binary to
> be executed, others have a "start UEFI shell" entry which executes
> EFI/Shellx64.efi on the :term:`ESP`. This can be a barebox binary as well.
> @@ -87,9 +96,13 @@ necessary to make a copy first.
> To start it create a USB memory stick like above and execute:
>
> .. code-block:: sh
> -
> +
> + # On x86
> qemu-system-x86_64 -pflash OVMF.fd -nographic /dev/sdx
>
> + # On armv8
> + qemu-system-aarch64 -L /usr/share/qemu-efi-aarch64 -bios QEMU_EFI.fd -nographic /dev/sdx
> +
> A plain VFAT image will work aswell, but in this case the UEFI BIOS won't
> recognize it as ESP and ``/boot`` won't be mounted.
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list