jupiter

The latest RISC-V computer I've tested is the Milk-V Jupiter. It's pokey at Intel Core 2 Duo levels of performance—at least according to Geekbench.

But performance is only one aspect that interests me. This is the first RISC-V Mini ITX motherboard I've tested, which means it can be installed in a PC case or rackmount enclosure, and it is much more featureful than a typical credit-card-sized SBC.

It includes niceties like front panel IO, front-panel Audio, USB 3.0, and USB 2.0, 24-pin ATX power input, an M.2 M-key slot for NVMe, and an open ended PCI Express slot!

This blog post follows along roughly with today's video:

I've been testing a Milk-V Jupiter this week, and have tested a number of other RISC-V development boards over the past two years.

As with any new CPU architecture, software support and ease of adoption are extremely important if you want to reach a wider audience. I wouldn't expect every developer and SBC hobbyist to be able to compile the Linux kernel, and the need to compile much of anything these days is getting rare. So having any instance where one has to know how to tweak a Makefile or pass in different flags to a compiler is a bit of a turn-off for platform adoption.

So one thing I've followed closely is how easy it is for me to get my own software running on RISC-V boards. It's one thing to run some vendor-provided demos. It's another entirely to take my real-world applications and infrastructure apps, and get them to work without hassle.

And to that end, Docker and Ansible, two tools I use extensively for dev/ops work, both run stably—though with plenty of caveats since RISC-V is still so new.