On Mon, Feb 11, 2013 at 11:21 PM, Hans de Goede <hdego...@redhat.com> wrote: >>> There may be some gotcha's when you start using libwdi to replace the >>> native windows driver with winusb / libusb0 / libusbk while an app >>> using the hotplug stuff is open, but that is unrelated to the API, that >>> is just tricky in general. >> >> I do not think that is the way to go. I do not quite like the idea of >> adding libwdi into libusbx. Take note driver switching is time >> consuming and may lead to quite bad user experiences if done in >> an libusbx based application. > > Note, I did not mean doing the switch from libusb, but what would happen > if the driver switching happens while a hotplug-enabled libusb is running.
I see. During driver installation or driver switching, the device is not ready yet. I believe the arrival event will only happen after the driver installation is complete if the device is newly attached. I am not so sure whether arrival/removal event will happen during the driver switching process. Need to test this scenario once we are in the implementation and testing stage. BTW, for driveless device, I do not think we need to deal with them too much, just treat them as not present. -- Xiaofan ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
