Hi Henrik On Mon, Jul 16, 2012 at 8:45 PM, Henrik Rydberg <rydberg@xxxxxxxxxxx> wrote: > Hi David, > > Perhaps one should make hid-core warn instead of bailing out instead? > Something may need to be done to make sure everything works smoothly, > but really, why would hid-core mind keeping a device on the bus with a > non-standard io driver? No, I think bailing out is the correct thing to do. If we emit a warning but leave the device on the bus, the device will have no driver loaded and idling in background. Hence, dropping the device is the best solution for 99% of the devices. However, devices that explicitly do not require the generic drivers (like picolcd and wiimote) should be able to stay on the bus. We could of course put them out of the HID subsystem as they have very little in common with the other HID drivers, but that wouldn't make the situation any better. It would mean writing transport-level drivers for picolcd and wiimote which are exactly the same as USBHID and HIDP. Hence, I think allowing non-standard drivers on the BUS is ok as long as they explicitly request it. Thanks David -- 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
