From: "Grover, Andrew" <andrew.grover@intel.com>
To: "Lee, Jung-Ik" <jung-ik.lee@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: "'Greg@kroah.com'" <Greg@kroah.com>
Subject: RE: bare pci configuration access functions ?
Date: Thu, 31 Oct 2002 13:07:08 -0800 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A492@orsmsx119.jf.intel.com> (raw)
> From: Lee, Jung-Ik [mailto:jung-ik.lee@intel.com]
> Some kernel drivers/components such as hotplug
> pci/io-node drivers,
> ACPI driver, some console drivers, etc **need bare pci
> configuration space
> access** before either pci driver is initialized or struct pci_dev is
> constructed.
>
> ACPI needs this for ACPI/PCI population, hotplug pci driver
> for populating
> hot-added pci hierarchy. As more drivers are cross ported
> over to wider
> architectures, this would become wider need. Help me if
> others need this
> too.
When the PCI Config stuff got revamped a few months ago, Greg KH, myself,
and some other people discussed this, and the conclusion seemed to be that
it was less ugly to make the code that needs bare PCI config access use fake
structs, than to have the bare functions exposed. Greg, am I remembering
correctly?
Regards -- Andy
next reply other threads:[~2002-10-31 21:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 21:07 Grover, Andrew [this message]
2002-10-31 21:23 ` Greg KH
2002-10-31 23:40 ` Kai Germaschewski
2002-10-31 22:00 Grover, Andrew
2002-10-31 22:11 ` Greg KH
2002-10-31 22:50 ` Scott Murray
2002-10-31 23:46 ` Greg KH
2002-11-01 0:23 ` Scott Murray
2002-10-31 23:37 ` KOCHI, Takayoshi
2002-10-31 23:54 ` Greg KH
2002-11-01 0:23 ` KOCHI, Takayoshi
2002-11-01 1:13 ` Greg KH
2002-11-01 2:07 Grover, Andrew
2002-11-01 2:45 ` 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=EDC461A30AC4D511ADE10002A5072CAD04C7A492@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=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
all inboxes | Powered by JetHome®