public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: Michael Tremer <michael.tremer@ipfire.org>, development@lists.ipfire.org
Cc: Vincent Li <vincent.mc.li@gmail.com>
Subject: [PATCH v1 4/8] lfs/Config: Add EFI and GRUB architecture definitions for loongarch64
Date: Tue,  4 Aug 2026 19:39:52 -0700	[thread overview]
Message-ID: <20260805023956.3379890-5-vincent.mc.li@gmail.com> (raw)
In-Reply-To: <20260805023956.3379890-1-vincent.mc.li@gmail.com>

Add support for building EFI bootable images on loongarch64 by defining
the appropriate architecture variables. This enables the build system
to correctly locate and build the EFI firmware, GRUB bootloader, and
associated boot components for the LoongArch64 architecture.

- Set EFI=1 to enable EFI support
- Set EFI_ARCH=LOONGARCH64 for EFI firmware selection
- Set GRUB_ARCH=loongarch64 to build the correct GRUB target

Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
---
 lfs/Config | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/lfs/Config b/lfs/Config
index 2334d5f0a..06ba065ea 100644
--- a/lfs/Config
+++ b/lfs/Config
@@ -111,7 +111,7 @@ DIR_TMP_PAK = $(DIR_TMP)/package-$(PROG)
 # Add the compiler location and version and specs to the ccache hash
 CCACHE_COMPILERCHECK += $(shell gcc -dumpspecs 2>/dev/null | md5sum | cut -d ' ' -f1)
 
-# We support EFI on x86_64 riscv64 and aarch64
+# We support EFI on x86_64 riscv64 aarch64 and loongarch64
 ifeq "$(BUILD_ARCH)" "x86_64"
 	EFI = 1
 	EFI_ARCH = x64
@@ -130,6 +130,12 @@ ifeq "$(BUILD_ARCH)" "aarch64"
 	GRUB_ARCH = arm64
 endif
 
+ifeq "$(BUILD_ARCH)" "loongarch64"
+	EFI = 1
+	EFI_ARCH = LOONGARCH64
+	GRUB_ARCH = $(BUILD_ARCH)
+endif
+
 CMAKE = cmake
 
 # In the toolchain, we might be cross-compiling and need cmake to know
-- 
2.38.1



  parent reply	other threads:[~2026-08-05  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  2:39 [PATCH v1 0/8] Add loongarch64 architecture support to IPFire Vincent Li
2026-08-05  2:39 ` [PATCH v1 1/8] make.sh: Add support for building on loongarch64 Vincent Li
2026-08-05  2:39 ` [PATCH v1 2/8] gcc: Add dynamic linker path for loongarch64 native toolchain build Vincent Li
2026-08-05  2:39 ` [PATCH v1 3/8] lfs/Config: Update config.guess and config.sub for loongarch64 support Vincent Li
2026-08-05  2:39 ` Vincent Li [this message]
2026-08-05  2:39 ` [PATCH v1 5/8] lfs/Config: Set GOARCH for loongarch64 builds Vincent Li
2026-08-05  2:39 ` [PATCH v1 6/8] installer: Enable EFI support for loongarch64 Vincent Li
2026-08-05  2:39 ` [PATCH v1 7/8] installer: Add bootloader installation " Vincent Li

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=20260805023956.3379890-5-vincent.mc.li@gmail.com \
    --to=vincent.mc.li@gmail.com \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@ipfire.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