From: Greg KH <greg@kroah.com>
To: "Lee, Jung-Ik" <jung-ik.lee@intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: RFC: bare pci configuration access functions ?
Date: Thu, 31 Oct 2002 17:02:41 -0800 [thread overview]
Message-ID: <20021101010241.GE12405@kroah.com> (raw)
In-Reply-To: <72B3FD82E303D611BD0100508BB29735046DFF69@orsmsx102.jf.intel.com>
Wait, first off, are we talking about 2.4, or 2.5 here? For 2.5 I think
everything is covered, right?
On Thu, Oct 31, 2002 at 11:29:19AM -0800, Lee, Jung-Ik wrote:
> Question:
> ========
> Will it be desirable to have bare global pci config access functions as seen
> in i386/ia64 pci codes ? It's clean and needs just what it takes - seg, bus,
> dev, func, where, value, and size.
No, I do not think so. I think the way 2.5 does this is the correct
way. But as I did that patch, I might be a bit biased :)
We could just force every arch to export the same functions that i386
and ia64 does, that shouldn't be a big deal. I think this would solve
the problem on 2.4 for pci hotplug, as ACPI is already "cheating" and
doing this right now...
thanks,
greg k-h
next prev parent reply other threads:[~2002-11-01 0:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 19:29 RFC: bare pci configuration access functions ? Lee, Jung-Ik
2002-11-01 1:02 ` Greg KH [this message]
2002-11-01 1:55 ` Lee, Jung-Ik
2002-11-01 2:11 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-11-01 2:39 Lee, Jung-Ik
2002-11-01 2:48 ` Greg KH
2002-11-01 4:45 Lee, Jung-Ik
2002-11-01 4:52 Lee, Jung-Ik
2002-11-01 5:38 ` Greg KH
2002-11-04 20:17 Lee, Jung-Ik
2002-11-04 21:30 ` Greg KH
2002-11-04 22:30 Lee, Jung-Ik
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=20021101010241.GE12405@kroah.com \
--to=greg@kroah.com \
--cc=jung-ik.lee@intel.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