On 2012.05.02 09:28, Hans de Goede wrote:
> The problem is that with usb device redirection we can have 1 device
> already redirected, and then the user asks to redirect another device
> to the virtual machine, so we install a driver for the other device,
> and then need to be able to use the other device without re-init

I see.

Still, installing a driver and expecting libusbx to be in a state to use 
the device is pretty much akin to hotplug on Windows, as you are 
transitioning from a device that didn't have a supported driver and thus 
was inaccessible to libusbx as if it wasn't plugged in, to a device that 
is now accessible with a supported driver, i.e. as if it had been 
plugged in. Moreover, unless I'm very mistaken, this kind of operation 
will effectively generate standard hotplug messages on Windows.

Considering that the current enum was designed with hotplug in mind, and 
thus with the aim of addressing this kind of situation natively once we 
get there (because by then we will have a thread that updates the device 
list as needed, from Windows hotplug notifications, and thus avoids 
having to apply this patch), I think you may be better off waiting for 
the hotplug branch to kick in. Or you can try to reuse the -pbatard/hp 
one, but it hasn't been updated in a long time.

I'm pretty sure the first thing we'll need to do, if we apply this 
patch, is remove it in the hotplug/2.0 branch, so I'm a bit on the fence 
as to whether it should be applied.

Given the choice, I'd rather work on kickstarting the libusbx 2.0 branch 
and apply the hp patches I have in -pbatard, but it may take a while...

Regards,

/Pete

------------------------------------------------------------------------------
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

Reply via email to