Can someone confirm that that only way to avoid having the hid USB driver bind to a device in preference to a custom driver based on vendor/product is to add the vendor/product to the hid blacklist in hid-core?
It looks like usb_match_id will at least for 2.4 will just fine the first match, which makes things a bit random, and probably depends which order in which the probe functions were registered, which depends on a whole host of factors. In a modular kernel, if modules are not yet loaded, usbmodules are likely to nominate that hid is loaded before the custom driver. Does this differ over 2.4/2.5/2.6 kernels? Tom Mander ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
