From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: forcing device to appear in subdir
Date: Mon, 05 Jan 2004 18:38:31 +0000 [thread overview]
Message-ID: <20040105183831.GB22177@kroah.com> (raw)
In-Reply-To: <20040103184237.92495.qmail@web14901.mail.yahoo.com>
On Sun, Jan 04, 2004 at 08:44:24AM -0800, Jon Smirl wrote:
> --- Greg KH <greg@kroah.com> wrote:
> > On Sat, Jan 03, 2004 at 10:42:37AM -0800, Jon Smirl wrote:
> > > DRI devices are supposed to appear in dri/card0, dri/card1, etc.
> >
> > Says the LSB standard?
>
> What does LSB say on this? It's been dri/cardX ever since dri was created, long
> before I started working on it.
LSB says to follow what LANANA says, and the LANANA documentation says:
226 char Direct Rendering Infrastructure (DRI)
0 = /dev/dri/card0 First graphics card
1 = /dev/dri/card1 Second graphics card
...
So yup, you should be in your own subdirectory. Care to send me a patch
for udev.rules that adds this subdir for all dri devices?
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:[~2004-01-05 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-03 18:42 forcing device to appear in subdir Jon Smirl
2004-01-04 8:52 ` Greg KH
2004-01-04 16:44 ` Jon Smirl
2004-01-05 18:38 ` Greg KH [this message]
2004-01-05 22:02 ` Jon Smirl
2004-01-05 22:09 ` Greg KH
2004-01-10 1:15 ` 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=20040105183831.GB22177@kroah.com \
--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).