Differences between revisions 3 and 4
Revision 3 as of 2022-12-09 06:59:16
Size: 3545
Editor: ?vimer
Comment:
Revision 4 as of 2022-12-09 07:27:42
Size: 3701
Editor: PaulWise
Comment: cleanups, mention the hardware-specific install docs too
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * Kernel support is already upstream  * Linux kernel support is already upstream
Line 22: Line 22:
 No, RISC-V is a new architecture, similar to ARM, but uses a different, open-source instruction set. No, RISC-V is a new architecture, similar to ARM, but uses a different, open-source instruction set.
Line 26: Line 26:
Aurelien Jarno(DD),Manuel A. Fernandez Montecelo(DD), Adrian Bunk(DD), Adam Borowski(DD) from [[https://salsa.debian.org/release-team/release.debian.org/-/blob/master/www/bookworm/arch_spec.yaml#L250|here]]
BO YU(Debian contributor)
Aurelien Jarno (DD),
Manuel A. Fernandez Montecelo (DD),
Adrian Bunk (DD),
Adam Borowski (DD)
(
from [[https://salsa.debian.org/release-team/release.debian.org/-/blob/master/www/bookworm/arch_spec.yaml#L250|the release qualification data]]),
BO YU (Debian contributor)
Line 32: Line 35:
 RISC-V architecture is a scalable architecture. Current use will be embedded single board computing, edge computing, etc. RISC-V architecture is a scalable architecture. Current use will be embedded single board computing, edge computing, etc.
Line 36: Line 39:
 Yes, there are users (SBC vision five boards, SiFive unmatched, etc.)
Yes, there are users (SBC vision five boards, SiFive unmatched, etc.)
Line 41: Line 43:
 Yes.  The architecture support started with these versions, which are recent: Yes. The architecture support started with these versions, which are recent:
Line 46: Line 48:
Line 50: Line 51:
 Yes. The ABI is stable, and supported with the GNU toolchain (binutils, glibc, GCC). Yes. The ABI is stable, and supported with the GNU toolchain (binutils, glibc, GCC).
Line 52: Line 53:
 The ABI document is available at https://riscv.org/wp-content/uploads/2015/01/riscv-calling.pdf The ABI document is available at https://riscv.org/wp-content/uploads/2015/01/riscv-calling.pdf
Line 58: Line 59:
https://wiki.debian.org/RISC-V https://wiki.debian.org/RISC-V#Creating_a_riscv64_chroot
Line 60: Line 61:
Hardware-specific install documentation available too:

https://wiki.debian.org/RISC-V#Hardware
Line 63: Line 67:

sid/experimental package is being built. Check in http://buildd.debian.org/
sid/experimental package are being built. Check in https://buildd.debian.org/
Line 76: Line 79:
 No No

riscv64: archive qualification page

Contents

  1. riscv64: archive qualification page
    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. What hardware is potentially available as a fast buildd?
      12. Is there an example box developers can login to to see if it works?
      13. 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.

Questions for new architectures

Are machines available to buy for the general public?

Yes there are multiple RISC-V board available for purchase:

https://ameridroid.com/products/visionfive-starfive https://www.aliexpress.com/item/1005002856721588.html

Is full source available?

  • Yes. The full stack is open source.
  • Linux kernel support is already upstream
  • Toolchain (GCC, glibc, gdb, binutils) support is already upstream

No, RISC-V is a new architecture, similar to ARM, but uses a different, open-source instruction set.

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

Aurelien Jarno (DD), Manuel A. Fernandez Montecelo (DD), Adrian Bunk (DD), Adam Borowski (DD) (from the release qualification data), BO YU (Debian contributor)

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

RISC-V architecture is a scalable architecture. Current use will be embedded single board computing, edge computing, etc.

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?

Yes, there are users (SBC vision five boards, ?SiFive unmatched, etc.)

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 architecture support started with these versions, which are recent:

  • Linux kernel: >= 5.17

  • GCC: >= 9.4 (currently 11.2)

  • glibc: 2.33
  • binutils: 2.37

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 stable, and supported with the GNU toolchain (binutils, glibc, GCC).

The ABI document is available at https://riscv.org/wp-content/uploads/2015/01/riscv-calling.pdf

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

Currently, running debootstrap from another port/architecture and running debootstrap second-stage from the port.

https://wiki.debian.org/RISC-V#Creating_a_riscv64_chroot

Hardware-specific install documentation available too:

https://wiki.debian.org/RISC-V#Hardware

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)?

sid/experimental package are being built. Check in https://buildd.debian.org/

What hardware is potentially available as a fast buildd?

TBD. Possible amd64 machine that cross compiles to riscv64?

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

debian-riscv64-porterbox-01

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.

No