On 13.2.2013 15.23, "Hans de Goede" <hdego...@redhat.com> wrote: > >> In my thinking weather there is a driver or not is >> logically a property of libusb_device and should >> be queried from that handle and result in corresponding >> error (LIBUSB_ERROR_NO_DRIVER) if passed to libusb_open(). > >Apps which are actually interested in this will want an >event on the transitions from driverless to non-driverless >too, so that they will know that the windows-device-manager >is done with the driver installation.
Ok, I see, I guess this could also be a 'property' of libsub_device (in my way of thinking), but I also see that it is handy to communicate this info via different events, even better so as far as my limited understanding of the this issue goes, that sound fine. Thanks for explaining. br Kusti ------------------------------------------------------------------------------ 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
