From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: dri and udev
Date: Sat, 27 Dec 2003 19:13:31 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107258774625081@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107251004911161@msgid-missing>
On Sat, Dec 27, 2003 at 09:08:57AM -0800, Jon Smirl wrote:
> Adding:
> REPLACE, KERNEL="card*", NAME="dri/card%n"
> to udev rules makes it work.
>
> DRI sure made an unfortunate legacy choice of calling the driver cardX.
>
> How is this going to work when there are multiple devices with the same name?
> For example
> /dev/hda and /dev/i2o/hda?
Those are two different devices, with different major/minor numbers.
i2o can't create a hda block device if there is already a block device
called hda in the system. So it will be called something else. As i2o
isn't working yet in 2.6, I'm not to worried about it :)
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
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
next prev parent reply other threads:[~2003-12-27 19:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 7:24 dri and udev Jon Smirl
2003-12-27 16:36 ` Kay Sievers
2003-12-27 17:08 ` Jon Smirl
2003-12-27 19:13 ` Greg KH
2003-12-27 19:13 ` Greg KH
2003-12-27 19:13 ` Greg KH [this message]
2003-12-27 19:14 ` Greg KH
2003-12-27 20:57 ` Jon Smirl
2003-12-27 20:57 ` Jon Smirl
2003-12-28 1:23 ` Marco d'Itri
2003-12-28 1:23 ` Marco d'Itri
2003-12-30 0:36 ` Greg KH
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=marc-linux-hotplug-107258774625081@msgid-missing \
--to=greg@kroah.com \
--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).