On Dec 18, 2007 8:50 AM, Graeme Gill <[EMAIL PROTECTED]> wrote: > > - the quirk could be added into the usbhid quirk list, so that it ignores > > the device (this is what has been currently done for the device in > > question) > > I'm gathering that this is in fact unnecessary (usb_detach_kernel_driver_np() > does seem to work - the report about it not working was in error), and is > undesirable if the possibility of switching to 'hidraw' is to be held open. > I agree. usb_detach_kernel_driver_np() will work unless the user has an very old kernel or very old libusb installation. I think libusb 0.1.8 onwards have this function.
Sometimes the user does not set up the hotplug/udev/hal rules correctly and thus can not run the libusb based application as a normal user. > > > There's also an excellent chance you don't need to call > > > usb_set_configuration() at all. Your devices have got only one > > > configuration, right? > > > > Well, I don't know. All the current devices may only have one > > interface, but this is in common code that is intended to > > cope with any number of currently unknown future devices, so > > I am just following l ibusb recommendations, and doing a > > usb_set_configuration(), to make sure they work. And if you want to support libusb-win32 under Windows, usb_set_configuration() is definitely necessary. I will think many blacklists in HID are not necessary if the application is based on libusb. We were tempted to submit patches for PICkit 1/2 but later decided not to do so since usb_detach_kernel_driver_np() works well. Xiaofan http://mcuee.blogspot.com - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
