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 18:48:41 -0800 [thread overview]
Message-ID: <20021101024841.GD13031@kroah.com> (raw)
In-Reply-To: <72B3FD82E303D611BD0100508BB29735046DFF6C@orsmsx102.jf.intel.com>
On Thu, Oct 31, 2002 at 06:39:26PM -0800, Lee, Jung-Ik wrote:
>
> Platform management, early console access, acpi, hotplug io-node w/ root,...
> pci_bus based access is useless before pci driver is initialized.
> All exceptions will be forced to use fake structs...
> Sounds we need to be ready to live with all exceptions here too :)
> Or just to make them all happy with that simple bare functions.
Ok, let's make them happy with bare functions, _if_ we have to. Places
that do not have to will be gleefully pointed out and mocked :)
> OK, if simple and pure pci config access is not possible in Linux land,
> let pci driver fake itself, not everyone else :)
> Just export the two APIs like pci_config_{read|write}(s,b,d,f,s,v),
> or the ones in acpi driver. Hide the fake pci_bus manipulation in them.
> This way is way better than having everyone fake pci driver ;-)
I agree. But can we do this for all archs? I don't know, and look
forward to your patch proving this will work. Without all arch support
of this, I can't justify only exporting the functions for i386 and ia64.
thanks,
greg k-h
next prev parent reply other threads:[~2002-11-01 2:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 2:39 RFC: bare pci configuration access functions ? Lee, Jung-Ik
2002-11-01 2:48 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 22:30 Lee, Jung-Ik
2002-11-04 20:17 Lee, Jung-Ik
2002-11-04 21:30 ` Greg KH
2002-11-01 4:52 Lee, Jung-Ik
2002-11-01 5:38 ` Greg KH
2002-11-01 4:45 Lee, Jung-Ik
2002-10-31 19:29 Lee, Jung-Ik
2002-11-01 1:02 ` Greg KH
2002-11-01 1:55 ` Lee, Jung-Ik
2002-11-01 2:11 ` Greg KH
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=20021101024841.GD13031@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