On 05/04/2012 07:07 AM, Peter Stuge wrote:
> Hans de Goede wrote:
>> what is expected by spice is that after it detects a hotplug itself
>> (through platform dependent code) that it can then do a new
>> libusb_get_device_list() call and the new device will be there.
> What hotplug events are received? Ie. when a device driver changes,
> does the same device (as exposed by the Windows backend) go away and
> come back, or will the previous libusb_device actually have
> disappeared during the driver change?
>
We are listening, in the application level, for USB device added/removed
events. When a device-added event is received (*),
a libusb driver is installed for that specific device (assuming it was
not already installed).
When libusb driver installation operation successfully completes, libusb
can still not open nor use the device, as the backend api is
"Unsupported API".
With this patch, the application asks libusb to rescan the devices,
libusb updates the device backend api, and the application can access
the device via libusb, and continue with its usbredir operation.
(*) Some conditions are to be met before that operation takes place,
such as the user requests this device to be shared with the guest.
I hope that answers your question.
Uri.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
