From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4hWnV22jZDz36Wb for ; Fri, 28 Aug 2026 18:48:58 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "YR2" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4hWnTy4cthz2xWF for ; Fri, 28 Aug 2026 18:48:54 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4hWnTm5n2lzFw; Fri, 28 Aug 2026 18:48:44 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1787942924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c/0TYGWeTdhGetm01YML0K0ie/Qlm/XNmPyfUzX/UFk=; b=mJpHqIQHZNvCfN1KfKgpJ5ut+RGAxJt6Usq1Qp7dvt1BLT+h27dySaLfFJ6Pbl1CkvxnFj hApQIU7UHkJwEkAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1787942924; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=c/0TYGWeTdhGetm01YML0K0ie/Qlm/XNmPyfUzX/UFk=; b=ssQHwtyzWTjbAL33OOZrpl3aElDawxb2NalXOC4LwE7UuP+kBgE/qBCZbmo2JQ9p6i3Udn MUx2fOPV+QLYVFBmETd7ZrAu3WrRG4n3Alc9/LeGWbb2/kZBeAls4R0XlU2fADKPZi24FB RqS/8THUh748Jl94E+03k8KPua4sf5mX+rpm010jzCndbwjLnCU+7ACh6izVE8/EifGD/i ly/iL7bVfVX1sfYunJmoNN1sDhbbtjfj4aVvqvp5pxpaFHrmDSb/e47K/J6uwtXvc5iizO Lrpmq/ZJftpFKbZ19Ve9k82MSPQDZ5t79ufJC/YZu8Sdufj6CTI7utT9ug2yNw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: [PATCH v1 0/8] Add loongarch64 architecture support to IPFire From: Michael Tremer In-Reply-To: Date: Fri, 28 Aug 2026 20:48:44 +0200 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: <94C9BF24-B216-4E63-93E6-337AF44EB514@ipfire.org> References: <20260805023956.3379890-1-vincent.mc.li@gmail.com> <4C3DE6A7-29E8-4E83-81D4-7CBB1F30B581@ipfire.org> To: Vincent Li Hello Vincent, Thank you very much. I just emailed back. All the best, -Michael > On 28 Aug 2026, at 03:52, Vincent Li wrote: >=20 > On Fri, Aug 28, 2026 at 8:54=E2=80=AFAM Vincent Li = wrote: >>=20 >> On Thu, Aug 27, 2026 at 6:40=E2=80=AFPM Michael Tremer >> wrote: >>>=20 >>> Hello Vincent, >>>=20 >>> Thanks for following up on this. >>>=20 >>> I have a branch here with a collection of changes needed to port = IPFire to loongarch64: >>>=20 >>> = https://git.ipfire.org/?p=3Dpeople/ms/ipfire-2.x.git;a=3Dshortlog;h=3Drefs= /heads/toolchain-loong64 >>>=20 >>> This is unfortunately taking a long time to compile in the emulator, = so progress has been very slow. I also needed a lot more changes to make = the build go through. I am still missing a couple of root files, and I = have not tested if the image would actually boot. >>>=20 >>> Generally, the changes that were needed were somewhat trivial and = there is not a lot of bad stuff that we would have to carry around. The = question however remains to our team if we want to make this port = generally available to users considering that hardware is neither = available to us or our users. >>>=20 >>> Do you have access, and do you know how to get access to hardware? >>=20 >> I bought a Loongson 3a6000 mini PC from aliexpress myself for = testing, >> the mini PC was kind of expensive when I bought it. I can ask the >> Loonson open source community organizer if it is possible for the >> IPFire team to have access to loongson hardware. >=20 > Hi Michael, >=20 > I sent you an email with Loongson's open source community organizer > contact Mingcong Bai on discussion if and how you could get access to > Loongson's hardware. >=20 > Thanks >=20 > Vincent >=20 >>=20 >> Best, >>=20 >> Vincent. >>=20 >>>=20 >>> All the best, >>> -Michael >>>=20 >>>> On 27 Aug 2026, at 04:18, Vincent Li = wrote: >>>>=20 >>>> Hi Michael, >>>>=20 >>>>=20 >>>> On Wed, Aug 5, 2026 at 10:40=E2=80=AFAM Vincent Li = wrote: >>>>>=20 >>>>> This patch series adds initial support for the LoongArch64 = architecture >>>>> to the IPFire build system and installer. LoongArch64 is the = 64-bit >>>>> RISC architecture developed by Loongson Technology, using UEFI as = its >>>>> standard firmware interface. >>>>>=20 >>>>> The series includes: >>>>>=20 >>>>> 1. **Build system detection** (make.sh): Add architecture = detection >>>>> for loongarch64 in the main build script. >>>>>=20 >>>>> 2. **Toolchain fixes** (gcc): Fix dynamic linker path for native >>>>> bootstrap to ensure glibc builds correctly. >>>>>=20 >>>>> 3. **Package build system** (lfs/Config): Update config.guess/sub >>>>> scripts to recognize loongarch64 as a valid architecture. >>>>>=20 >>>>> 4. **EFI and GRUB support** (lfs/Config): Define architecture >>>>> variables for building EFI firmware and GRUB for loongarch64. >>>>>=20 >>>>> 5. **Go language support** (lfs/Config): Set GOARCH=3Dloong64 for >>>>> building Go packages. >>>>>=20 >>>>> 6. **Installer EFI detection** (installer): Enable EFI boot mode >>>>> detection for loongarch64 systems. >>>>>=20 >>>>> 7. **Installer bootloader** (installer): Add GRUB installation >>>>> support for loongarch64-efi. >>>>>=20 >>>>> 8. **Kernel build** (kernel): Add architecture definitions and >>>>> special handling for building the Linux kernel on loongarch64. >>>>>=20 >>>>> These changes are the foundation for a complete loongarch64 port >>>>> of IPFire and have been tested on a LoongArch64 development = system. >>>>>=20 >>>>> Signed-off-by: Vincent Li >>>>> --- >>>>> make.sh: Add support for building on loongarch64 >>>>> gcc: Add dynamic linker path for loongarch64 native toolchain = build >>>>> lfs/Config: Update config.guess and config.sub for loongarch64 = support >>>>> lfs/Config: Add EFI and GRUB architecture definitions for = loongarch64 >>>>> lfs/Config: Set GOARCH for loongarch64 builds >>>>> installer: Enable EFI support for loongarch64 >>>>> installer: Add bootloader installation support for loongarch64 >>>>> kernel: Add build support for loongarch64 >>>>>=20 >>>>> .../kernel/kernel.config.loongarch64-ipfire | 7814 +++++ >>>>> config/rootfiles/common/loongarch64/linux | 23754 = ++++++++++++++++ >>>>> lfs/Config | 14 +- >>>>> lfs/gcc | 4 + >>>>> lfs/linux | 10 + >>>>> make.sh | 7 +- >>>>> src/installer/hw.c | 3 +- >>>>> src/installer/install-bootloader | 3 + >>>>> 8 files changed, 31605 insertions(+), 4 deletions(-) >>>>> create mode 100644 config/kernel/kernel.config.loongarch64-ipfire >>>>> create mode 100644 config/rootfiles/common/loongarch64/linux >>>>>=20 >>>>> -- >>>>> 2.38.1 >>>>=20 >>>> Just a follow-up on this IPFire LoongArch support patch series, do = you >>>> have any input? >>>>=20 >>>> Vincent