From: Matthew Wilcox <willy@debian.org>
To: "Lee, Jung-Ik" <jung-ik.lee@intel.com>
Cc: "'Greg KH'" <greg@kroah.com>,
"'KOCHI, Takayoshi'" <t-kouchi@mvf.biglobe.ne.jp>,
"Luck, Tony" <tony.luck@intel.com>,
pcihpd-discuss@lists.sourceforge.net,
linux ia64 kernel list <linux-ia64@linuxia64.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-ia64] RE: PCI Hotplug Drivers for 2.5
Date: Thu, 24 Oct 2002 18:59:14 +0100 [thread overview]
Message-ID: <20021024185914.Z27461@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <72B3FD82E303D611BD0100508BB29735046DFF45@orsmsx102.jf.intel.com>; from jung-ik.lee@intel.com on Thu, Oct 24, 2002 at 10:40:05AM -0700
On Thu, Oct 24, 2002 at 10:40:05AM -0700, Lee, Jung-Ik wrote:
> **resource management**
> Non-ACPI platforms uses $HRT/EBDA, pcibios_*(), SMBIOS, etc. for slot
> enumeration/configuration.
> DIG64/ACPI, and SHPC requires ACPI for this. IPF platforms only have ACPI
> _CRS, _PRT, _HPP, _BBN, _STA, _ADR, _SUN, etc on the namespace for PHP, and
> we have to use them. (as a side note, this functionality is common for other
> hotplug-* as mentioned in first mail. No API will be common for
> hotplug-everything, but functionality is common and has not to be
> duplicated)
> **event management in terms of controller/slot operations **
> ACPI provides only _EJ0, _PS?, _STA, etc for slot operations but these are
> not mandatory. That means, we can use either ACPI method or controller
> driver.
> intcphp driver has not enabled ACPI method based solution but uses
> controller driver.
> intcphp driver is also capable of performing ACPI method based solution
> since it works on ACPI namespace. This is why acpiphp and intcphp could be
> sharing resource management and event management.
Sounds like we want a library of ACPI code that can be used by individual
drivers rather than an ACPI driver with pluggable event management
functions then.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-10-24 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 16:24 PCI Hotplug Drivers for 2.5 Lee, Jung-Ik
2002-10-24 16:46 ` Greg KH
2002-10-24 17:40 ` Lee, Jung-Ik
2002-10-24 17:59 ` Matthew Wilcox [this message]
2002-10-24 22:06 ` Greg KH
2002-10-24 17:39 ` KOCHI, Takayoshi
2002-10-24 17:52 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 18:19 [Linux-ia64] " Lee, Jung-Ik
2002-10-24 4:33 Lee, Jung-Ik
2002-10-24 5:10 ` Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH
2002-10-24 11:49 ` [Linux-ia64] " Matthew Wilcox
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=20021024185914.Z27461@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=greg@kroah.com \
--cc=jung-ik.lee@intel.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=t-kouchi@mvf.biglobe.ne.jp \
--cc=tony.luck@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).