On Tue, Jul 10, 2018 at 12:25 AM, Andreas Schwab <sch...@suse.de> wrote: > On Jul 09 2018, Alistair Francis <alistai...@gmail.com> wrote: > >> On Mon, Jul 9, 2018 at 3:00 AM, Andreas Schwab <sch...@suse.de> wrote: >>> What is the state of the sifive_u emulation? When I tried to boot a bbl >>> with an included kernel I get these errors: >>> >>> qemu-system-riscv64: plic: invalid register write: 00002090 >>> qemu-system-riscv64: plic: invalid register write: 00002094 >>> qemu-system-riscv64: plic: invalid register write: 00002098 >>> qemu-system-riscv64: plic: invalid register write: 0000209c >>> qemu-system-riscv64: plic: invalid register write: 000020a0 >>> qemu-system-riscv64: plic: invalid register write: 000020a4 >>> qemu-system-riscv64: plic: invalid register write: 000020a8 >>> qemu-system-riscv64: plic: invalid register write: 000020ac >>> qemu-system-riscv64: plic: invalid register write: 000020b0 >>> qemu-system-riscv64: plic: invalid register write: 000020b4 >> >> I see those as well. I haven't investigated but I assume we are just >> not completely modelling the PLIC. In saying that it should still >> boot. Do you not see the kernel booting? > > I don't see those errors when using the qemu from github:riscv/riscv-qemu.
There are extra patches in that fork. One of them must fix the messages for the PLIC. I think a fair few of them have been reviewed on list, they just need a PR to be merged. Alistair > > Andreas. > > -- > Andreas Schwab, SUSE Labs, sch...@suse.de > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 > "And now for something completely different."
