From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI config space
Date: Sat, 03 Jan 2004 02:21:40 +0000 [thread overview]
Message-ID: <20040103022140.GA6896@kroah.com> (raw)
In-Reply-To: <20040102215557.97085.qmail@web14907.mail.yahoo.com>
On Fri, Jan 02, 2004 at 05:57:02PM -0800, Jon Smirl wrote:
> --- Greg KH <greg@kroah.com> wrote:
> > On Fri, Jan 02, 2004 at 05:03:20PM -0800, Jon Smirl wrote:
> > > And I should use something like execl (seems to be in klibc) to call udev to
> > > query for it's directory and my path?
> >
> > "my path"? What does that mean?
>
> My DEVPATH, /class/dri/card0 so that I can do:
> udev -q /class/dri/card0
> and get the path to my device:
> dri/card0
That is your device node that udev created, right?
> and combine it with:
> udev -r
> which returns
> /udev/
>
> So that I can build the path to my device:
> /udev/dri/card0
Yes, then you can do whatever operations on that device node you want
to.
But if you want to touch the PCI config stuff for your device, just go
off of the DEVPATH. There should be a "device" symlink in your
/class/dri/card0/ directory that points to the pci device directory,
right?
Anyway, it sounds like you are on the right path...
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
prev parent reply other threads:[~2004-01-03 2:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 21:55 PCI config space Jon Smirl
2004-01-03 0:50 ` Greg KH
2004-01-03 1:03 ` Jon Smirl
2004-01-03 1:22 ` Greg KH
2004-01-03 1:57 ` Jon Smirl
2004-01-03 2:21 ` Greg KH [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=20040103022140.GA6896@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).