Skip to contentSkip to conversation

psmouse et al and mousedev dependancy

DISCUSSION Michael Tokarev 2 participants 2 messages Mar 16, 2005

lore
Share & tools
lore
#0 lore raw

A quick (hopefully) question.

When mousedev is compiled as a module, loading psmouse or usbhid modules does not enable the mouse, one have to load mousedev too. The same is true for keybdev and actual keyboard drivers.

Why not add this dependancy explicitly in psmouse et al modules, something like (pseudocode):

#if CONFIG_MOUSEDEV==m
request_module(mousedev);
#endif

, or, to "use" some symbol in psmouse.ko which is defined in mousedev?

Thanks.

/mjt

#1 lore raw

Hi,

Quoted 6 lines · Michael Tokarev

A quick (hopefully) question.

When mousedev is compiled as a module, loading psmouse or usbhid modules does not enable the mouse, one have to load mousedev too. The same is true for keybdev and actual keyboard drivers.

Quoted 9 lines

Why not add this dependancy explicitly in psmouse et al modules, something like (pseudocode):

#if CONFIG_MOUSEDEV==m
request_module(mousedev);
#endif

, or, to "use" some symbol in psmouse.ko which is defined in mousedev?

Not everyone uses mousedev (evdev, tsdev, joydev) so they are not loaded by default. It is actually hotplug scripts' task to load proper interface module after a new input device has been discovered.

Signature · 1 line
Dmitry