Gerd Hoffmann writes:
> Hi,
>
>> > Hmm, I think the xen core needs better QOM support ...
>> >
>> > struct XenDevice should have a DeviceState element, so it can be used as
>> > device object directly instead of attaching a device object like
>> > this ...
>>
>> Hmm, interesting idea. The dev
Hi,
> > Hmm, I think the xen core needs better QOM support ...
> >
> > struct XenDevice should have a DeviceState element, so it can be used as
> > device object directly instead of attaching a device object like
> > this ...
>
> Hmm, interesting idea. The device object could even be added in
On 27/09/16 11:08, Gerd Hoffmann wrote:
> Hi,
>
>> struct usbback_info {
>> struct XenDevice xendev; /* must be first */
>> +char id[24];
>> +struct USBBACKDevice *dev;
>> USBBus bus;
>> void *urb_srin
On 27/09/16 11:00, Daniel P. Berrange wrote:
> On Mon, Sep 26, 2016 at 02:43:57PM +0200, Juergen Gross wrote:
>> In order to be able to specify to which pvusb controller a new pvusb
>> device should be added we need a qemu device for each pvusb controller
>> with an associated id.
>>
>> Add such a
Hi,
> struct usbback_info {
> struct XenDevice xendev; /* must be first */
> +char id[24];
> +struct USBBACKDevice *dev;
> USBBus bus;
> void *urb_sring;
> void *conn_sring;
>
On Mon, Sep 26, 2016 at 02:43:57PM +0200, Juergen Gross wrote:
> In order to be able to specify to which pvusb controller a new pvusb
> device should be added we need a qemu device for each pvusb controller
> with an associated id.
>
> Add such a device when a new controller is requested and attac
In order to be able to specify to which pvusb controller a new pvusb
device should be added we need a qemu device for each pvusb controller
with an associated id.
Add such a device when a new controller is requested and attach the
usb bus of that controller to the new device. Any device connected
