From: Jesse Barnes <jbarnes@sgi.com>
To: Matthew Wilcox <willy@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/3] PCI sysfs improvements
Date: Tue, 8 Apr 2003 13:34:10 -0700 [thread overview]
Message-ID: <20030408203410.GA18765@sgi.com> (raw)
In-Reply-To: <20030407234334.GS23430@parcelfarce.linux.theplanet.co.uk>
On Tue, Apr 08, 2003 at 12:43:34AM +0100, Matthew Wilcox wrote:
>
> [Note: This patch depends on the sysfs-bin patch]
>
> Improve pci-sysfs:
> - Add PCI config space access to sysfs.
> - Prefix values in the PCI space with `0x' cos they're hex values.
> - Reformat the resource file with 64-bit values.
> - Present all resources in the file, don't stop at the first empty one.
>
> Todo:
> - Implement write access.
> - Convert resource file into directories
This looks good. Could you post what the relevant sysfs tree looks
like? I like your idea of adding mmio and portio space as well. And
of course, I'd like legacy I/O space too, but I guess I'll have to do
that myself if I find the time...
Thanks,
Jesse
prev parent reply other threads:[~2003-04-08 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 23:43 [PATCH] [2/3] PCI sysfs improvements Matthew Wilcox
2003-04-08 20:34 ` Jesse Barnes [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=20030408203410.GA18765@sgi.com \
--to=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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