On Mon, Jun 19, 2000 at 06:44:49PM -0700, Johannes Erdfelt wrote:
> I intend to post something this (after some feedback and changes) to
> linux-kernel as well.
>
> Please give me feedback.
First off, nice summary of all of the current implementations and problems
that abound. It's nice to see it all in one place.
I only have a few "small" questions:
> 6.4.2 Processing on REGISTER events
>
> When a REGISTER event occurs, the module obtains the descriptors for the
> device and parses them, determining which configurations, interfaces and
> alternate settings are available on the device. It then executes an
> arbitrary algorithm (not explained here for brevity) to select a
> configuration, then select alternate settings and drivers for each
> interface. The software then programs the active configuration and the
> active alternate setting for each interface.
>
> If the driver must be loaded at insertion time, instead of at use time,
> the driver will be loaded, binds the driver to the interfaces necessary
> and activates the interface.
>
> The module then obtains unique or semi-unique characteristics from the
> device and retrieves any previously saved permissions for the device.
> If no information is retrieved from the local database, default values
> from the configuration can be applied to the device.
>
> Lastly, a script is executed to perform any local device configuration
> necessary. For instance, a script can be used to configure an ethernet
> device.
Where does this 'module' live? In kernel space or userspace?
And how does the interface between kernel and userspace work out?
Does this module kick off the script(s) mentioned above?
Does there need to be a way for a driver to register itself with this
module to let the module know what devices and interfaces it can handle?
I do agree with the fact that it looks like devfs can be used for all of
this, and something does need to be done that spans more than just one
subsystem (i.e. USB, FireWire, PCMCIA, etc.) I'm glad that this summary
says just that.
Thanks,
greg k-h
--
greg@(kroah|wirex).com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
