On Thu, May 04, 2000, Alan Cox <[EMAIL PROTECTED]> wrote:
> > Ah, it does to me. What does PCMCIA do?
>
> The PCMCIA kernel code reads the tuples that identify the card. They are
> passed to the daemon. That looks in the table of devices to find which
> driver to load (remember that PCMCIA lacks the USB generic classes of
> driver sanity). The driver is loaded then bound to the PCMCIA stuff. Then
> the scripts for it are kicked off.
>
> So its something like
>
> Insertion event
> Umm.. this is a CyQ've Ethernet blah blah
> Post to user space
>
> pcmcia daemon
> Scan in /etc/pcmcia
> Thats an ne2000 driver job
> Load ne2000 driver if not loaded
> Tell pcmcia to plug that card and driver together
>
> Plugged together
> pcmcia daemon builds a descriptor set
> Run the script for this type of object
> Matches eth0 and mac
> Run that script item
> ifconfig blah
> route add foo
> done
BTW - My userspace driver binding patch did everything up to Plugged
together. Adding that functionality looks to be easy.
The only thing that is different is that it uses devfsd instead of
another daemon.
AFAICT from talking to David Hinds, the same functionality could also be
accomplished via merging it into devfsd the same way my patch did for
USB.
JE
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
