loong64: archive qualification page (Continuously updating)

Contents

  1. loong64: archive qualification page (Continuously updating)
    1. Questions for new architectures
      1. Are machines available to buy for the general public?
      2. Is full source available?
      3. Is this architecture related to other architectures already in the archive, or that also should be considered, either now or in the future? Can the related architectures be supported in a single architecture (eg, with a biarch arrangement)?
      4. Are there 3 or more developers (or NMs) actively maintaining the port? Who are they?
      5. What sort of architecture is this? Desktop/workstation? Mainframe/supercomputer? Embedded? Something else?
      6. Does it have any users? If a desktop system, are there Debian admins who run Debian systems on the arch? If an embedded system are there real systems shipping that a Debian port will be useful for? If a mainframe system are there real systems with many users that a Debian port will be useful for? Who are they?
      7. Is there kernel and toolchain support? At what level? Are the latest versions supported, or are legacy releases required for compatibility with some hardware?
      8. Has the ABI stabilised, or are there major ABI changes coming up? Is the ABI stable enough to ensure users will be able just "apt-get dist-upgrade" from one version to the next?
      9. How do you install a system? (URL to a HOWTO)
      10. Has a buildd been setup? How much of the archive has been built (count by source package, builds of old versions are fine for this case)?
      11. Is there an example box developers can login to to see if it works?
      12. It's also worth considering whether the port has any special requirements. If the port is mainly for embedded systems, it may be appropriate to have different installation or release arrangements compared to normal desktop/workstation architectures.
      13. Other pages

Questions for new architectures

Are machines available to buy for the general public?

Yes, the LoongArch based machines (3A5000/3A6000) can be purchased on public platforms such as Jingdong and Aliexpress.

Is full source available?

Yes. The full stack is open source. The LoongArch architecture has been merged by Kernel, Gcc, Gdb, Binutils, Glibc, Llvm, Golang upstream projects and so on. All source code supporting the LoongArch architecture can be pulled from the software upstream or Debian sid.

No, the LoongArch is a new architecture. The LoongArch architecture is an Instruction Set Architecture (ISA) that has Reduced Instruction Set Computer (RISC) style. Loongson and LoongArch documentations can be found at https://github.com/loongson/LoongArch-Documentation.

Are there 3 or more developers (or NMs) actively maintaining the port? Who are they?

John Paul Adrian Glaubitz, Loongson team.

We invite someone (DMs/DDs) to spend some extra time to maintain loong64 together.

What sort of architecture is this? Desktop/workstation? Mainframe/supercomputer? Embedded? Something else?

LoongArch processors are used in Personal Computers, Servers and so on. Please see https://www.loongson.cn/.

Does it have any users? If a desktop system, are there Debian admins who run Debian systems on the arch? If an embedded system are there real systems shipping that a Debian port will be useful for? If a mainframe system are there real systems with many users that a Debian port will be useful for? Who are they?

At present, there are thousands of Loongson information partners. Please see https://www.loongson.cn/application/list?id=19.

The Loongson LoongArch architecture's partners and users are represented through three areas: Cooperating OEMs, Cooperating Operating System Vendors, and user-facing end products.

List a small selection of links among the many partner vendors.

We apologize for the lack of English pages on the official websites of some of our partners.

Lenovo https://www.lenovo.com.cn/

ASUS https://w3.asus.com.cn/

Inspur https://www.inspur.com/

TSINGHUA TONGFANG https://www.tongfangpc.com/index.php/article-_dragonheartgroup-l-75.html

UOS https://www.uniontech.com/ https://www.chinauos.com/partner/guide https://www.chinauos.com/resource/download-professional

Kylinsoft https://www.kylinos.cn/cooperation/partner.html https://product.kylinos.cn/productCase/171/36

Deepin https://www.deepin.org/en https://www.deepin.org/en/download/

openEuler https://www.openeuler.org/zh/ https://www.openeuler.org/zh/download/?version=openEuler%2024.03%20LTS

openAnolis https://openanolis.cn/ https://openanolis.cn/download

Gentoo https://wiki.gentoo.org/wiki/Project:LoongArch

Tencent https://www.tencent.com/zh-cn/ https://im.qq.com/linuxqq/index.shtml https://meeting.tencent.com/download?mfrom=OfficialIndex_TopBanner1_Download

Kingsoft Office https://www.wps.cn/ https://www.wps.cn/product/wpslinux

Dameng Data https://intl.dameng.com/

Emto https://www.emto.com.cn/about2/show.php?id=188

Estor http://www.estor.com.cn/product

Winhong https://www.winhong.com/product/xinChuang/

Is there kernel and toolchain support? At what level? Are the latest versions supported, or are legacy releases required for compatibility with some hardware?

Yes, the LoongArch has been merged by Kernel, Gcc, Gdb, Binutils, Glibc, Llvm, Golang upstream projects and so on. The principle is to prioritize the submission of LoongArch architecture support to the upstream.

Has the ABI stabilised, or are there major ABI changes coming up? Is the ABI stable enough to ensure users will be able just "apt-get dist-upgrade" from one version to the next?

Yes. The ABI is stabilised. Core and other software packages are aligned with upstream software.

Now the build status for loong64 in the Debian Package Auto-Building environment can be found at https://buildd.debian.org/status/architecture.php?a=loong64&suite=sid.

The number of installed packages are 16235 (as of this writing).

The ABI document can be found at https://loongson.github.io/LoongArch-Documentation/LoongArch-ELF-ABI-EN.html.

How do you install a system? (URL to a HOWTO)

We can run debootstrap from x86 port/architecture and running debootstrap second-stage from loong64 port.

In addition, we have made one system (via debian-ports pool and pool-loong64 repo) based on Debian-installer and debian-cd, which can be installed directly via CD/DVD images.

Has a buildd been setup? How much of the archive has been built (count by source package, builds of old versions are fine for this case)?

Yes, there are 6 buildds for loong64. Please see https://buildd.debian.org/status/architecture.php?a=loong64&suite=sid.

The sid packages are being built, with 80~90% constantly since the bootstrap in 2023/08, and constantly over 93% since 2024/04.

The archive-coverage of loong64 from June 7, 2024 is more than 95%.

When creating this page (Tue, 14 May 2024 10:04:15 +0800), the status of Buildds are as follows,

Update status of Buildds (Fri, 07 Jun 2024 20:08:01 +0800）, the specific data is as follows,

Is there an example box developers can login to to see if it works?

The porterbox being deployed by cbmuser for loong64.

It's also worth considering whether the port has any special requirements. If the port is mainly for embedded systems, it may be appropriate to have different installation or release arrangements compared to normal desktop/workstation architectures.

Nothing special.

Other pages

LoongArch, Ports/loong64, HardwareQualification/loong64.