[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: arm/cadence_gem driver support
From: |
Kent Dorfman |
Subject: |
Re: arm/cadence_gem driver support |
Date: |
Wed, 25 Sep 2019 12:46:40 -0400 |
Thanks for the input!
Could you post your complete startup command sequence for the VM? I'm
trying to get a handle on whether I would need to create DTB files for
the image. Also I've noted that qemu can be picky about command
option ordering.
Thanks
On 9/25/19, Alexei Colin <address@hidden> wrote:
> On Wed, Sep 25, 2019 at 11:24:12AM -0400, Kent Dorfman wrote:
>> yes. fully bridged access via a tap is what I was looking for...but I
>> don't see anything on your command line identifying the guest network
>> as cadence_gem: no model=cadence_gem. Is it implicit?
>
> Instantiation of the device is happening via Xilinx Qemu device tree
> node, which has a 'compatible' string identifying the model. The command
> line args are implicitly referring to the device in the device tree, by
> order, I believe (so, '-net nic' will refer to first ethernet device in
> DT, '-net nic -net nic' will refer to first and second etc).
>
> I have not tried tap mode in upstream Qemu.
>