Project:RISC-V
| Has Name::RISC-V development project | |
|---|---|
| Description | Has Description::Gentoo RISC-V architecture support project |
| Project email | Has Contact::riscv@gentoo.org |
| IRC channel | #gentoo-riscv |
| Lead(s) | none No lead election date set |
| Member(s) | SMW::off
|
| Subproject(s) (and inherited member(s)) |
(none) |
| Parent Project | Base System |
| Project listing | |
[[Article description::The RISC-V project is an effort to bring first-class RISC-V CPU architecture support in Gentoo.]]
Status
Experimental riscv64 stages are available, and a minimum set of packages in the Gentoo repository is keyworded. At the moment we have the following stages:
- riscv64gc / lp64d, openrc
- riscv64gc / lp64d, systemd
- riscv64imac / lp64, openrc
- riscv64imac / lp64, systemd
qemu-riscv can run riscv64 binaries just fine. This way one can also test in an emulated chroot.
What needs to be done
Things to happen yet:
- Integrate the stage3 generation into the weekly autobuilds.
- Provide a bootable image.
- Get riscv32 running somehow.
Keywording policy
- ARCH=riscv is the assigned keyword.
- No stable riscv keywords are planned for the moment.
- For packages without obvious hardware aspect, qemu-user or qemu-system testing is sufficient for keywording ~riscv
- Packages with hardware aspect (bootloader, drivers, ...) have to be tested on real hardware.
- Multilib packages should get tested for both lp64d and lp64 ABI, for others lp64d is sufficient
- When we get to stabilizations in the future, that will require testing on real hardware.
Documentation
- TODO: Describe arch-specific gotchas (alignment requirements, immediate encodings, PIC story).
- RISC-V ABIs
- RISC-V Multilib
This article is issued from Gentoo. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.