Make a few RISC-V test machines available for package maintainers

kashyapc commented

2026-02-03 13:06:21 +00:00

Owner

Make a few RISC-V machines available for Fedora package maintainers to test/debug/build their packages.

Quoting the rationale expressed here[1].

"In some cases Fedora Package maintainers may not have access to all supported architectures or releases of Fedora that they maintain packages for. In order to assist with this, some community members are providing access to test machines/instances that they maintain to allow Fedora package maintainers to test, build, compile or debug their packages.

(Cc: @kevin)

[1] https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers

Make a few RISC-V machines available for Fedora package maintainers to test/debug/build their packages. Quoting the rationale expressed here[1]. ``` "In some cases Fedora Package maintainers may not have access to all supported architectures or releases of Fedora that they maintain packages for. In order to assist with this, some community members are providing access to test machines/instances that they maintain to allow Fedora package maintainers to test, build, compile or debug their packages. ``` (Cc: @kevin) [1] https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers

kashyapc changed title from ~~Add a couple of RISC-V test machines for package maintainers~~ to Make a few RISC-V test machines available for package maintainers

2026-02-03 13:07:30 +00:00

smilner commented

2026-02-03 14:05:49 +00:00

cc @Zlopez

davidlt commented

2026-02-03 14:52:56 +00:00

Owner

At this point I would highly advice to wait for potential RVA23 boards as those are more likely to be useful for long-term. That would mean Spacemit K3 (Banana Pi, MIlk-V, Sipeed, DeepComputing, and others) will be selling module + carrier (all seems to be identical from Spacemit itself). There should be later this year Tenstorrent Atlantis (RVA23, designed for Datacenter/Server/HPC/Distro work). I expect Atlantis to have UEFI + ACPI.

Alternative would be Milk-V Titan (DP1000). From ISA point of view it's boring, and it got a bit delayed. Potentially short-term support as distributions are switching to RVA23 as baseline.

If K3 doesn't get delayed it will be 1-2 months away from DP1000. The current expectation for K3 board availability is March/April.

At this point I would highly advice to wait for potential RVA23 boards as those are more likely to be useful for long-term. That would mean Spacemit K3 (Banana Pi, MIlk-V, Sipeed, DeepComputing, and others) will be selling module + carrier (all seems to be identical from Spacemit itself). There should be later this year Tenstorrent Atlantis (RVA23, designed for Datacenter/Server/HPC/Distro work). I expect Atlantis to have UEFI + ACPI. Alternative would be Milk-V Titan (DP1000). From ISA point of view it's boring, and it got a bit delayed. Potentially short-term support as distributions are switching to RVA23 as baseline. If K3 doesn't get delayed it will be 1-2 months away from DP1000. The current expectation for K3 board availability is March/April.

kashyapc referenced this issue

2026-02-03 21:12:45 +00:00

Add server-grade RISC-V builders in Fedora datacenter #6

kashyapc commented

2026-02-03 21:21:38 +00:00

Author

Owner

@davidlt wrote in #7 (comment):

At this point I would highly advice to wait for potential RVA23 boards as those are more likely to be useful for long-term. That would mean Spacemit K3 (Banana Pi, MIlk-V, Sipeed, DeepComputing, and others) will be selling module + carrier (all seems to be identical from Spacemit itself). There should be later this year Tenstorrent Atlantis (RVA23, designed for Datacenter/Server/HPC/Distro work). I expect Atlantis to have UEFI + ACPI.

All that sounds good, but from the second-hand information I heard at FOSDEM, Atlantis is likely to be delayed by another quarter.

Alternative would be Milk-V Titan (DP1000). From ISA point of view it's boring, and it got a bit delayed. Potentially short-term support as distributions are switching to RVA23 as baseline.

If K3 doesn't get delayed it will be 1-2 months away from DP1000. The current expectation for K3 board availability is March/April.

Yeah, I've also seen some folks at FOSDEM mention me that they've ordered SpacemiT K3.

Overall, let's reevaluate in a couple of months.

@davidlt wrote in https://forge.fedoraproject.org/riscv/planning/issues/7#issuecomment-361515: > At this point I would highly advice to wait for potential RVA23 boards as those are more likely to be useful for long-term. That would mean Spacemit K3 (Banana Pi, MIlk-V, Sipeed, DeepComputing, and others) will be selling module + carrier (all seems to be identical from Spacemit itself). There should be later this year Tenstorrent Atlantis (RVA23, designed for Datacenter/Server/HPC/Distro work). I expect Atlantis to have UEFI + ACPI. All that sounds good, but from the second-hand information I heard at FOSDEM, Atlantis is likely to be delayed by another quarter. > Alternative would be Milk-V Titan (DP1000). From ISA point of view it's boring, and it got a bit delayed. Potentially short-term support as distributions are switching to RVA23 as baseline. > > If K3 doesn't get delayed it will be 1-2 months away from DP1000. The current expectation for K3 board availability is March/April. Yeah, I've also seen some folks at FOSDEM mention me that they've ordered SpacemiT K3. Overall, let's reevaluate in a couple of months.

kashyapc referenced this issue

2026-02-04 16:06:19 +00:00

Write a "community initiative" for RISC-V as a primary arch #8

ngompa commented

2026-05-26 16:44:17 +00:00

FYI: @owensz @redbeard

kashyapc self-assigned this

2026-06-10 13:11:39 +00:00

kashyapc referenced this issue

2026-06-11 23:27:23 +00:00

Path for 'riscv64' inclusion in primary Koji #23

siddhesh commented

2026-07-14 17:44:50 +00:00

@kashyapc I know we've discussed gcc package build times in the recent past; do these new machines meet the 36 hours turnaround requirement? I know I had said 30 hours for the build time; 36 should be acceptable for the full turnaround, i.e. from job submission to completion which includes time spent waiting for a builder.

jmontleon commented

2026-07-14 17:50:57 +00:00

Owner

K3 Pico ITX takes about 70 hours right now: https://riscv-koji.fedoraproject.org/koji/taskinfo?taskID=227609

Which takes 100+ hours off older hardware: https://riscv-koji.fedoraproject.org/koji/taskinfo?taskID=215111

But still well over 30.

K3 Pico ITX takes about 70 hours right now: https://riscv-koji.fedoraproject.org/koji/taskinfo?taskID=227609 Which takes 100+ hours off older hardware: https://riscv-koji.fedoraproject.org/koji/taskinfo?taskID=215111 But still well over 30.

kashyapc commented

2026-07-14 18:16:05 +00:00

Author

Owner

@siddhesh Yeah, what Jason says.

And you can see some approx timings for other packages here: Fedora build benchmarks on SpacemiT K3 (RVA23 hardware)

@siddhesh Yeah, what Jason says. And you can see some approx timings for other packages here: [Fedora build benchmarks on SpacemiT K3 (RVA23 hardware)](https://forge.fedoraproject.org/riscv/planning/issues/17)

Rows
Columns

Make a few RISC-V test machines available for package maintainers #7