From: Michael Tremer <michael.tremer@ipfire.org>
To: Vincent Li <vincent.mc.li@gmail.com>
Cc: development@lists.ipfire.org
Subject: Re: [PATCH v1 0/8] Add loongarch64 architecture support to IPFire
Date: Fri, 28 Aug 2026 20:48:44 +0200 [thread overview]
Message-ID: <94C9BF24-B216-4E63-93E6-337AF44EB514@ipfire.org> (raw)
In-Reply-To: <CAK3+h2w1fNHHJ7Tojy8OQeYF6BY3enf-eNpXuTm+CrkuzA5idQ@mail.gmail.com>
Hello Vincent,
Thank you very much. I just emailed back.
All the best,
-Michael
> On 28 Aug 2026, at 03:52, Vincent Li <vincent.mc.li@gmail.com> wrote:
>
> On Fri, Aug 28, 2026 at 8:54 AM Vincent Li <vincent.mc.li@gmail.com> wrote:
>>
>> On Thu, Aug 27, 2026 at 6:40 PM Michael Tremer
>> <michael.tremer@ipfire.org> wrote:
>>>
>>> Hello Vincent,
>>>
>>> Thanks for following up on this.
>>>
>>> I have a branch here with a collection of changes needed to port IPFire to loongarch64:
>>>
>>> https://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=shortlog;h=refs/heads/toolchain-loong64
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> Do you have access, and do you know how to get access to hardware?
>>
>> 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.
>
> Hi Michael,
>
> 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.
>
> Thanks
>
> Vincent
>
>>
>> Best,
>>
>> Vincent.
>>
>>>
>>> All the best,
>>> -Michael
>>>
>>>> On 27 Aug 2026, at 04:18, Vincent Li <vincent.mc.li@gmail.com> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>>
>>>> On Wed, Aug 5, 2026 at 10:40 AM Vincent Li <vincent.mc.li@gmail.com> wrote:
>>>>>
>>>>> 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.
>>>>>
>>>>> The series includes:
>>>>>
>>>>> 1. **Build system detection** (make.sh): Add architecture detection
>>>>> for loongarch64 in the main build script.
>>>>>
>>>>> 2. **Toolchain fixes** (gcc): Fix dynamic linker path for native
>>>>> bootstrap to ensure glibc builds correctly.
>>>>>
>>>>> 3. **Package build system** (lfs/Config): Update config.guess/sub
>>>>> scripts to recognize loongarch64 as a valid architecture.
>>>>>
>>>>> 4. **EFI and GRUB support** (lfs/Config): Define architecture
>>>>> variables for building EFI firmware and GRUB for loongarch64.
>>>>>
>>>>> 5. **Go language support** (lfs/Config): Set GOARCH=loong64 for
>>>>> building Go packages.
>>>>>
>>>>> 6. **Installer EFI detection** (installer): Enable EFI boot mode
>>>>> detection for loongarch64 systems.
>>>>>
>>>>> 7. **Installer bootloader** (installer): Add GRUB installation
>>>>> support for loongarch64-efi.
>>>>>
>>>>> 8. **Kernel build** (kernel): Add architecture definitions and
>>>>> special handling for building the Linux kernel on loongarch64.
>>>>>
>>>>> These changes are the foundation for a complete loongarch64 port
>>>>> of IPFire and have been tested on a LoongArch64 development system.
>>>>>
>>>>> Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
>>>>> ---
>>>>> 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
>>>>>
>>>>> .../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
>>>>>
>>>>> --
>>>>> 2.38.1
>>>>
>>>> Just a follow-up on this IPFire LoongArch support patch series, do you
>>>> have any input?
>>>>
>>>> Vincent
next prev parent reply other threads:[~2026-08-28 18:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 2:39 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 ` [PATCH v1 4/8] lfs/Config: Add EFI and GRUB architecture definitions for loongarch64 Vincent Li
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
2026-08-27 2:18 ` [PATCH v1 0/8] Add loongarch64 architecture support to IPFire Vincent Li
2026-08-27 10:40 ` Michael Tremer
2026-08-28 0:54 ` Vincent Li
2026-08-28 1:52 ` Vincent Li
2026-08-28 18:48 ` Michael Tremer [this message]
2026-09-01 4:59 ` 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=94C9BF24-B216-4E63-93E6-337AF44EB514@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=vincent.mc.li@gmail.com \
/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