From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Multiple drivers for one device
Date: Mon, 11 Jul 2005 14:02:14 +0000 [thread overview]
Message-ID: <20050711140211.GB6760@vrfy.org> (raw)
In-Reply-To: <AEF6C48E6742439EF64DDA6C@[10.169.6.233]>
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
prev parent reply other threads:[~2005-07-11 14:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 20:19 Multiple drivers for one device Kenneth Porter
2005-07-11 14:02 ` Kay Sievers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050711140211.GB6760@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).