Input layer demand loading
Quoted 9 lines
Quoted 5 lines
True, but then if you try to open the port, you will only get the base joydev.o module loaded, not the gameport driver, which is what you _really_ want to have loaded, right?
So there really isn't much benifit to doing this, sorry.
Why? It could work the way PCMCIA SCSI works. Cardmgr loads the LLDD, but sd, sg, etc. are loaded on demand.
how? SCSI (or USB, PCI, EISA etc) have driver-independent means to identify device or at least device class.
But how are you going you going to know you need to load specific mouse driver (logitech not microsoft) or specific joystick flavour? All that you possibly know that you have _some_ mouse or _some_ joystick ...
-andrey
Am Mittwoch, 16. Juli 2003 20:19 schrieb Andrey Borzenkov:
Quoted 10 lines
Quoted 9 lines
Quoted 5 lines
True, but then if you try to open the port, you will only get the base joydev.o module loaded, not the gameport driver, which is what you _really_ want to have loaded, right?
So there really isn't much benifit to doing this, sorry.
Why? It could work the way PCMCIA SCSI works. Cardmgr loads the LLDD, but sd, sg, etc. are loaded on demand.
Quoted 6 lines
how? SCSI (or USB, PCI, EISA etc) have driver-independent means to identify device or at least device class.
But how are you going you going to know you need to load specific mouse driver (logitech not microsoft) or specific joystick flavour? All that you possibly know that you have _some_ mouse or _some_ joystick ...
Exactly, you'd only load the hardware independent part on demand. Or, alternatively, you'd record the driver to load in the hotplug script and load it on demand.
Regards
Oliver
Quoted 10 lines · Andrey Borzenkov
Quoted 9 lines
Quoted 5 lines
True, but then if you try to open the port, you will only get the base joydev.o module loaded, not the gameport driver, which is what you _really_ want to have loaded, right?
So there really isn't much benifit to doing this, sorry.
Why? It could work the way PCMCIA SCSI works. Cardmgr loads the LLDD, but sd, sg, etc. are loaded on demand.
Quoted 6 lines
how? SCSI (or USB, PCI, EISA etc) have driver-independent means to identify device or at least device class.
But how are you going you going to know you need to load specific mouse driver (logitech not microsoft) or specific joystick flavour? All that you possibly know that you have _some_ mouse or _some_ joystick ...
Isn't that why we have hotplug in userspace?
That way, we know we have a mouse, but it's up to userspace to find out what kind.
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 29 lines · Andrey Borzenkov
-----Original Message-----
Quoted 15 lines · Andrey Borzenkov
Quoted 13 lines
Quoted 9 lines
Quoted 5 lines
True, but then if you try to open the port, you will only get the base joydev.o module loaded, not the gameport driver, which is what you _really_ want to have loaded, right?
So there really isn't much benifit to doing this, sorry.
Why? It could work the way PCMCIA SCSI works. Cardmgr loads the LLDD, but sd, sg, etc. are loaded on demand.
how? SCSI (or USB, PCI, EISA etc) have driver-independent means to identify device or at least device class.
Quoted 9 lines
Quoted 3 lines
But how are you going you going to know you need to load specific mouse driver (logitech not microsoft) or specific joystick flavour? All that you possibly know that you have _some_ mouse or _some_ joystick ...
Isn't that why we have hotplug in userspace?
That way, we know we have a mouse, but it's up to userspace to find out what kind.
Quoted 6 lines
that is not what hotplug is for. What you describe is called "probing".
Hotplug is there to load hardware driver once hardware is known, not to probe what hardware is there.
It can be used this way but it is rather abuse (or misuse) I'd say.
In many cases, you only know you have a class of devices, and you need more probing after the initial hardware notification (hotplug).
There are many people that want all probing to be in user space. Let's face it, it's easier (no need to reboot) to upgrade a userspace probing app than to install a new kernel.
Unfortunatly, it doesn't look like that will happen for 2.6, but I'd bet it will in 2.7, and hotplug will probably be a considerable player in that area (unless something better is used instead).