3 ms·
The FPGA based RISC-V hardware that I already have is much slower, has much less RAM and is in other ways more limited than QEMU. OTOH what's missing from QEMU
by rwmj 10y ago
The FPGA based RISC-V hardware that I already have is much slower, has much less RAM and is in other ways more limited than QEMU. OTOH what's missing from QEMU is virtio support.
However none of this is relevant for Fedora builders, which must be 19" rackable server hardware. This is a non-negotiable condition from the Fedora project itself, and also quite understandable because they don't want to be managing flaky dev boards. (For those interested, we solved this for armv7 initially using Calxeda hardware, and later using aarch64 hardware running in 32 bit mode).
- mynameislegion 10y agoIs there a reason you cant use cross-builds? or qemu once it has virtio?
- rwmj 10y agoCross builds aren't really a supported way to build RPMs. No other architecture supported by Fedora uses cross-compilation, so it would just be an endless stream of problems and forks. The current autobuilder is using QEMU (without virtio, but it'd be a lot easier and faster with) running on a 16 core Xeon. https://github.com/rwmjones/fedora-riscv-autobuild https://github.com/rwmjones/fedora-riscv-autobuild But for the Fedora official builders, it's 19" rackable RISC-V real server hardware, and that's the non-negotiable condition we've been given, which I support and understand. It'll be a few years, but it doesn't stop people using Fedora on RISC-V right now, they just have to grab the packages from a slightly different URL: https://fedorapeople.org/groups/risc-v/ https://fedorapeople.org/groups/risc-v/