From: Greg KH <greg@kroah.com>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Exporting PCI ROMs via syfs
Date: Fri, 21 May 2004 16:48:11 -0700 [thread overview]
Message-ID: <20040521234811.GA13404@kroah.com> (raw)
In-Reply-To: <20040521010510.84867.qmail@web14928.mail.yahoo.com>
On Thu, May 20, 2004 at 06:05:10PM -0700, Jon Smirl wrote:
> GregKH has suggested that a good interface for accessing the contents of PCI
> ROMs from user space would be to make them available from sysfs. What would be a
> good way to structure the code for doing this? Should this be part of the pci
> driver, and how would this interface into class_simple to make the attribute
> appear?
No class_simple stuff, what about just the sysfs code for the pci device
itself? Like where we export the config info today?
And yes, it sounds like we need a quirks file to keep some cards from
doing bad things.
thanks,
greg k-h
next prev parent reply other threads:[~2004-05-22 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 1:05 Exporting PCI ROMs via syfs Jon Smirl
2004-05-21 23:38 ` Valdis.Kletnieks
2004-05-22 2:56 ` Greg KH
2004-05-21 23:48 ` Greg KH [this message]
2004-05-22 3:20 ` Jon Smirl
2004-05-22 21:24 ` Martin Mares
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=20040521234811.GA13404@kroah.com \
--to=greg@kroah.com \
--cc=jonsmirl@yahoo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox