Michael Reinelt wrote:
>
> Jeff Garzik wrote:
> >
> > > Another (design) question: How will such a driver/module deal with
> > > autodetection and/or devfs? I don't like to specify 'alias /dev/tts/4
> > > netmos', because thats pure junk to me. What about pci hotplugging?
> >
> > pci hotplugging happens pretty much transparently. When a new device is
> > plugged in, your pci_driver::probe routine is called. When a new device
> > is removed, your pci_driver::remove routine is called.
>
> Thats clear to me. But the probe and remove routine can only be called
> if the module is already loaded. My question was: who will load the
> module? (I'll call it 'netmos.o')
typically a hotplug agent, cardmgr in this case.
> If I do a 'modprobe serial', how should the serial driver know that the
> netmos.o should be loaded, too?
cardmgr ideally should load netmos.o, which will automatically pull in
serial.o.
(cardmgr is from the pcmcia-cs package, at
http://pcmcia-cs.sourceforge.net/)
Regards,
Jeff
--
Jeff Garzik | Sam: "Mind if I drive?"
Building 1024 | Max: "Not if you don't mind me clawing at the dash
MandrakeSoft | and shrieking like a cheerleader."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
