On Wed, 14 Jan 2009, Michael Tokarev wrote: > Let's take a look at my example, hid_bright. Without this module, my > keyboard does not work, even if usbhid&Co is loaded. But this module > does exactly two things: > > hid_hw_start(hdev, HID_CONNECT_DEFAULT); > usbhid_set_leds(hdev); > Maybe, just maybe, it's possible to init stuff by default, and get > additional features or quirks later, when actually loading the > sub-driver? But any way, this "doing nothing" driver thing seems to be > wrong... Yes. And actually hid-bright and hid-dell drivers have been already removed in current Linus' tree, and the leds are handled in the generic code again. So in this particular case, things are exactly the same as they used to be before for your hardware. Still, there are drivers that are more complicated and having the code in the generic code is not bearable, so we have to think about this and solve it anyway, even though this is not going to be a problem particularly for your system in 2.6.29. -- Jiri Kosina -- 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
