On 6 January 2014 22:37, Christopher Covington <cov@codeaurora.org> wrote:

Hi Ryan,

On 01/06/2014 05:27 PM, Ryan Harkin wrote:
> On 6 January 2014 20:26, Peter Maydell <peter.maydell@linaro.org

> <mailto:peter.maydell@linaro.org>> wrote:
>
> On 6 January 2014 19:46, Ryan Harkin <ryan.harkin@linaro.org

> <mailto:ryan.harkin@linaro.org>> wrote:
> > Hello,
> >
> > I'm trying to fire up an ARM fastmodel using a virtio block device rather
> > than the emulated MMC block device.
> >
> > UEFI is reading the kernel & DTB off the virtio device, so I know the device
> > is present.
>
> > So far, I don't see any vda devices being enumerated (or any other virtio
> > messages) and it rootwaits for /dev/vda2.
>
> Stupid question: does the DTB you're passing to the kernel
> definitely have the virtio-mmio devices in it? (hopefully in the
> right locations).
>
>
> OMG, I think my brain has been in deep sleep. No, the DTB doesn't have
> virtio-mmio.
>
> I'll try it again tomorrow, but I'm pretty sure that's it. Thanks!

While debugging it may be easier to specify the device with a kernel parameter
than make device tree modifications.

virtio_mmio.device=1K@0x0130000:42

Thanks for your help, that's a nice tip.  It didn't quite work however.  The DT entry I added was slightly different:


+            virtio_block@0130000 {
+                compatible = "virtio,mmio";
+                reg = <0x130000 0x1000>;
+                interrupts = <0x2a>;
+            };

But, it's working now, so thanks again to Peter

 for pointing out the obvious mistake.

Regards,
Christopher

--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.