Hi Jiri, On Fri, Mar 30, 2012 at 4:49 PM, Jiri Kosina <jkosina@xxxxxxx> wrote: > On Mon, 20 Feb 2012, Nikolai Kondrashov wrote: >> Add "have_special_driver" hid module parameter - a list of additional HID >> devices which have specialized driver on HID bus. Needed to support out-of-tree >> HID drivers. > > I find this a little bit hackish :) How about for example the userspace > transport drivers for Bluetooth-LE that are currently in the works? I like the idea and the implementation seems good, but I can't see how it is related to the task of having out-of-tree HID drivers, sorry. > I'd very much prefer just using sysfs (bind/unbind) way of doing things if > possible for this purpose. What do you think? To my shame I must admit I didn't know or forgot of this mechanism. Although I did some research asking kernel developers at work about possibility to rebind a different driver. They either forgot about it at the time too, or I didn't ask properly. I think, I can craft an udev rule which will detach a tablet from the generic HID driver and attach it to my driver through sysfs. Please forget about this patch for now, I will resume bothering you in case it's not possible or not appropriate :) Thanks! Sincerely, Nick -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
