Hi Jiri, Thanks for your message. Pretty good timing, actually, as I was just about to pick this back up. ;)
On Thu, Nov 01, 2012 at 11:38:19AM +0100, Jiri Kosina wrote: > On Mon, 10 Sep 2012, Dmitry Torokhov wrote: > > > > The other piece to this puzzle is that usbhid should blacklist these > > > devices > > > to avoid binding if it happens to be loaded before usbtouchscreen. To do > > > this, usbhid needs to be able to blacklist devices based on interface > > > protocol (right now it only supports blacklist on VID + PID). > > > > > > Would you accept a patch set that implements this? > > > > Juri, this question is really for you... > > Generally, I am not objecting to this idea in general. > > What is the particular use case here, so that it's needed? We have some eGalax devices with class HID and protocol None that both usbhid and usbtouchscreen will bind to, but we only want them bound to usbtouchscreen. Some do in fact work with usbhid, but not all of them do. OTOH they all work with usbtouchscreen as of commit 037a833ed05a86d01ea27a2c32043b86c549be1b. We want to blacklist these devices in usbhid to avoid binding to it if it is loaded first. But usbhid should continue to handle eGalax devices with class HID and protocol other than None (e.g. Mouse). They all have the same vendor and product IDs, so we need to be able to blacklist on (VID, PID, protocol) instead of just (VID, PID). Does that make sense? Thanks, Forest -- Forest Bond http://www.alittletooquiet.net http://www.rapidrollout.com
signature.asc
Description: Digital signature
