On 4 April 2018 at 15:25, Gerd Hoffmann <kra...@redhat.com> wrote: > On Wed, Apr 04, 2018 at 11:18:23AM +0100, Peter Maydell wrote: >> Ping for code review, please? It would be nice if our 'raspi3' >> model for 2.12 was one we could say actually booted a known >> Linux image... > > The Fedora 27 image kernel (aarch64, 4.13) boots and mounts the root > filesystem. This is an improvement, so: > > Tested-by: Gerd Hoffmann <kra...@redhat.com> > > It doesn't finish boot though, at some point the kernel starts to > complain about timeouts and xfs throws io errors, so things are not > perfect yet. > > raspi2 doesn't boot the fedora 27 armhfp kernel. Looks unrelated > though, it fails with "Division by zero in kernel" before even loading > the sdhost driver. I suspect the kernel tries to access some hardware > not emulated by qemu ... > > Trying to run u-boot as boot-loader (so I don't have to copy the kernel > from the image) doesn't work too.
Thanks for the testing. I've applied this series to target-arm.next for 2.12 (with minor tweaks as per code review). I have a blog post pending which describes how to boot a Debian image on the raspi3 model, which I'll publish once this hits master. thanks -- PMM
