Re: [RFC] HID bus design overview.
Jiri Kosina <[email protected]>
| Newsgroups | gmane.linux.usb.devel,gmane.linux.kernel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 2 Apr 2007, Li Yu wrote: > Hi, I do not think that using blacklist in base driver for this purpose > is good idea. If so, we need modify source when each new HID device > driver come, that's so ugly. Hi Li, well, the drivers are exceptions from the generic handling, so creating an exceptional rule (entry in hid_blacklist) for them is not that bad. OK, it's not the nicest thing on earth probably, but serves the purpose in current vendors-trying-to-break-hardware-in-the-most-original-way world quite well. This is going to cause some headache to out-of-tree drivers. Oh well, do we care that much? In your scenario you'll still need a way how to unbind the device from the hid driver and bind it to the new specific device, won't you?. This could be done by a separate userspace program, but well ... I think just blacklisting the hardware is much cleaner, than needing to ship a separate userspace program along with the driver. Thanks, -- Jiri Kosina ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel