On Wed, Apr 16, 2008 at 10:30:54PM +0200, Jiri Slaby wrote: > On 04/16/2008 03:31 PM, Jiri Kosina wrote: >> Otherwise default kernel configuration might make the hardware that worked >> properly in previous versions not to work with new kernel. > > Actually I have one problem here. Autoloading. I don't have any idea how to > solve it. To solve it backward compatible with older userspace (if I would > change module-init-tools). I'm thinking only about a default-y option which > inhibits these drivers as a module for some time until the change gfets > propagated (and user decides he no longer needs it). > > Modules are supposed to have MODULE_DEVICE_TABLE(hid, table) (which has > another minor issue with different buses). This won't load any module, > since depmod et al. don't know this device table so far. > > Any ideas, please? > When I added serio bus I had to send patches to Rusty for module-init-tools... No way around it as far as I understand. -- Dmitry -- 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
