On 02/28/2012 04:30 PM, Jiri Kosina wrote:
well, I am not really sure what value does it provide to have such functionality in the kernel. I can understand that it helps you when developing out-of-tree (yet) drivers ... but as you are patching the kernel anyway with those drivers, you can easily run a kernel that has hid_have_special_driver[] array adjusted accordingly. And once you are submitting the driver for inclusion, you are of course submitting it together with hid_have_special_driver[] addition. So it doesn't seem to be a debugging facility to me, and neither does it provide any added value for users of vanilla kernel.
Maybe I did too extensive an explanation. Here is a shorter one. This is not needed for development, but only for end users to be able to load an out-of-tree driver before it becomes available in their distribution. Without this, they will need to build their own kernel with my patches every time it is updated. With this, they will even be able to use DKMS to have drivers built and installed automatically with each kernel update. My rationalization for this specific solution: http://thread.gmane.org/gmane.linux.usb.general/58661/focus=58869 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
