mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: chalianis1@gmail.com
To: s.hauer@pengutronix.de
Cc: barebox@lists.infradead.org, Chali Anis <chalianis1@gmail.com>
Subject: [PATCH 3/3] doc: efi: add efi armv8 payload documentation.
Date: Wed, 22 Oct 2025 01:25:08 -0400	[thread overview]
Message-ID: <20251022052508.1368520-3-chalianis1@gmail.com> (raw)
In-Reply-To: <20251022052508.1368520-1-chalianis1@gmail.com>

From: Chali Anis <chalianis1@gmail.com>

Add how to compile armv8 efi payload and how to run it with qemu

Signed-off-by: Chali Anis <chalianis1@gmail.com>
---
 Documentation/boards/efi.rst | 21 +++++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)

diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst
index 869e5e88172f..a3a06b987f97 100644
--- a/Documentation/boards/efi.rst
+++ b/Documentation/boards/efi.rst
@@ -23,7 +23,7 @@ x86_64 binary currently is tested.
 Building barebox for EFI
 ------------------------
 
-Use the following to build barebox for EFI:
+Use the following to build barebox for EFI to target x86 machine:
 
 .. code-block:: sh
 
@@ -31,6 +31,14 @@ Use the following to build barebox for EFI:
   make efi_defconfig
   make
 
+Use the following to build barebox for EFI to target armv8 machine:
+
+.. code-block:: sh
+
+  export ARCH=arm
+  make efi_v8_defconfig
+  make
+
 The resulting EFI image is ``barebox.efi`` (or the barebox-flash-image link).
 
 Running barebox on EFI systems
@@ -39,8 +47,9 @@ Running barebox on EFI systems
 The simplest way to run barebox on a USB memory stick. (U)EFI only supports
 FAT filesystems, so make sure you either have a FAT16 or FAT32 filesystem on
 the memory stick. Put ``barebox.efi`` into the ``EFI/BOOT/`` directory and
-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``.
+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.
 
-- 
2.34.1




      parent reply	other threads:[~2025-10-22  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  5:25 [PATCH 1/3] test: Containerfile: add qemu-efi-aarch64 chalianis1
2025-10-22  5:25 ` [PATCH 2/3] test: arm: add efi v8 test for efi arm64 payload chalianis1
2025-10-22  5:25 ` chalianis1 [this message]

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=20251022052508.1368520-3-chalianis1@gmail.com \
    --to=chalianis1@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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