Multiple drivers for one device

Multiple drivers for one device

[Kenneth Porter]

I have a PCILYNX Firewire card. I have two drivers available: pcilynx and 
nosy (http://bitplanet.net/nosy/). Nosy is a Firewire sniffer driver that 
puts the chip into "snoop" mode. I bought the card specifically for this 
function. What's the correct procedure to get the /dev/nosy device node 
created in udev? I notice that after my 2.6 kernel (Fedora Core 4) boots, 
the pcilynx driver is loaded. I rmmod it and modprobe nosy into place, then 
create the /dev entry manually. (Actually, I put it in /etc/udev/device so 
that it gets created at boot time.) Is there a preferred way to get the 
nosy driver loaded instead of pcilynx? Is there a way to get the device 
node created automagically when the driver is modprobed into place?


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: Multiple drivers for one device

[Kay Sievers]

On Fri, Jul 08, 2005 at 01:19:03PM -0700, Kenneth Porter wrote:
> I have a PCILYNX Firewire card. I have two drivers available: pcilynx and 
> nosy (http://bitplanet.net/nosy/). Nosy is a Firewire sniffer driver that 
> puts the chip into "snoop" mode. I bought the card specifically for this 
> function. What's the correct procedure to get the /dev/nosy device node 
> created in udev? I notice that after my 2.6 kernel (Fedora Core 4) boots, 
> the pcilynx driver is loaded. I rmmod it and modprobe nosy into place, then 
> create the /dev entry manually.

Does this driver integrate with the driver core and is visible in /sys?
If not, udev can't do anything.

> (Actually, I put it in /etc/udev/device so 
> that it gets created at boot time.) Is there a preferred way to get the 
> nosy driver loaded instead of pcilynx? Is there a way to get the device 
> node created automagically when the driver is modprobed into place?

There is no udev proposed way to do it. Distributions have their own way
to do this. /etc/udev/devices is Fedora specific and should work fine
on Fedora.

Kay


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel