On Mon, 09 Jul 2018 16:04:48 PDT (-0700), Michael Clark wrote:
On Tue, Jul 10, 2018 at 9:52 AM, 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?
FWIW, I see similar looking messages on QEMU master but get a booting kernel.
Thanks to some of the WD guys our Linux port is rapidly approaching "bootable
on master", so we should start pushing on the QEMU patch queue a bit as well.
Is there anything in particular I can do to help get patches reviewed? Michael
has taken most of the burden here, but I'm trying to schedule much more time
for code review on my end (which I say while replying to a thread that's been
dead for a month... :)).
