All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: PCI in /proc, /sys, and so on
Date: Sat, 31 May 2003 22:05:30 -0400	[thread overview]
Message-ID: <1054433129.22088.764.camel@cube> (raw)

In /proc/bus/pci, there is a tree containing
files to access PCI config space (only, no BARs)
and a seemingly out-of-place "devices" file.
There is no support for multiple domains.
Like this:
.
|-- 00
|   |-- 0b.0
|   `-- 10.0
|-- 01
|   |-- 0b.0
|   |-- 17.0
|   |-- 18.0
|   |-- 19.0
|   `-- 1a.0
|-- 02
|   |-- 0b.0
|   `-- 0f.0
`-- devices

Over in /sys/devices, there is a tree with more
info. At first glance I thought "pci0" would be
the first domain, but really it is just the bus
number. So that duplicates part of the name
lower down the tree: /sys/devices/pci2/02:0b.0
has a pair of "2" that are redundant.

So, there's no PCI domain support anywhere except
in some nasty ioctl, and no interface to allow
simple file-based access to PCI MMIO regions.

Future directions? Where would file-based access
be most acceptable? (in /proc, in /sys, or ???)

It sure would be nice to have all the stuff for
any given device end up in the same directory.



                 reply	other threads:[~2003-06-01  1:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1054433129.22088.764.camel@cube \
    --to=albert@users.sf.net \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.