> > Or were you talking about extracting the device information from the
> > module?
> 
> Exactly.

That can be done, but it seems like a lot more coding than just
providing shell scripts for each driver.  Eventually, it'd make
more sense not to compile specific device IDs into drivers.


> Modules can then be loaded by that userlevel daemon or the kernel
> itself. (I think the userspace solution has greater flexibility though.)

And lower overall cost too.  The userspace code (and tables) need only
be loaded when they're really needed.  If I enable KUSBD, I've paid a
miniscule cost in code space, but I can plug in any of my USB devices
and know their drivers will be loaded automatically.


> This limits adding a driver to copying a file in a modules/*/ directory
> and running depmod.

Then there's the question of what plugging it in will do to the rest
of the system ... a new printer should maybe tell CUPS about itself,
for example.  It'll probably want to have an /etc/usb/config/* script
run after it's loaded, and maybe some application code (demos, etc).

- Dave



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to