On 19 Apr 2017, at 2:15 PM, Luke Kenneth Casson Leighton < lkcl@lkcl.net> wrote:
On Tue, Apr 18, 2017 at 1:46 PM, Manuel A. Fernandez Montecelo < manuel.montezelo@gmail.com> wrote: The support for the serial devices is ad-hoc and quite flaky, and
there are problems like e.g. locking when trying to read and write to
the device at the same time.
There were people working on virtio support for riscv-qemu, not sure
if it's merged yet, but that would be the way to go for a definitive
solution.
ahh great to hear. it is slightly bizarre to be considering developing software for hardware that's entirely in flux, isn't it? :) i'll take a look and see how things stand.
The user-mode ABI is pretty much frozen so any user space packages built for RV32IMAFDC or RV64IMAFDC should be to a stable ABI.
The privileged spec is in flux, however this only affects kernel mode code.
RISCVEMU has Virtio Block, Net and Console. It’s an interpreter so not as fast as QEMU.
In any case it includes a kernel config in the patches directory that can be used to build a RISC-V VirtIO kernel:
There is also a fedora image linked from the page which includes a self-hosted compiler. |