From: Greg KH <greg@kroah.com>
To: "KOCHI, Takayoshi" <t-kouchi@mvf.biglobe.ne.jp>
Cc: jung-ik.lee@intel.com, tony.luck@intel.com,
pcihpd-discuss@lists.sourceforge.net, linux-ia64@linuxia64.org,
linux-kernel@vger.kernel.org
Subject: Re: PCI Hotplug Drivers for 2.5
Date: Wed, 23 Oct 2002 23:12:36 -0700 [thread overview]
Message-ID: <20021024061236.GJ19557@kroah.com> (raw)
In-Reply-To: <20021024145839.OAHRC0A82654.59A07363@mvf.biglobe.ne.jp>
On Wed, Oct 23, 2002 at 10:59:34PM -0700, KOCHI, Takayoshi wrote:
> Hi,
>
> On Wed, 23 Oct 2002 22:10:08 -0700
> Greg KH <greg@kroah.com> wrote:
>
> > Also, why doesn't the ACPI PCI hotplug driver work for your machines?
> > I've seen it work on a very wide range of processors (i386 and ia64),
> > and manufacturers, and any specific issues with your hardware would
> > probably be better addressed with patches to the existing ACPI driver.
>
> The ACPI spec provides very limited control of actual hardware
> (With ACPI, we don't have common method for controlling such as Bus
> speed, LED etc.).
> So if a hardware comes with well-documented hotplug controller, we
> can achieve finer control over the hardware.
Ah, I didn't realize this. So for some machines (like IBM's x440), we
should stick with using the hotplug controller driver, instead of using
the ACPI driver. Sounds reasonable to me.
> The SHPC specification defines it still depends on ACPI for managing
> resources, etc. So resource management portion can be and *should be*
> shared with all PCI hotplug drivers that use ACPI for resource
> management.
>
> I think the most important thing is everyone agree on the direction
> in which we should go before we code anything, in order not to waste
> our time.
I think we now all agree that resource management should move into a
place where it can be shared by all pci hotplug drivers, right?
If so, anyone want to propose some common code? I think the stuff in
the ACPI driver that was pulled from the Compaq driver is a great start.
I can try to pull this into the core myself, but if the Intel developers
have the time, and energy, I would greatly appreciate their help (or
anyone else who wants to join in.)
thanks,
greg k-h
next prev parent reply other threads:[~2002-10-24 6:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 4:33 PCI Hotplug Drivers for 2.5 Lee, Jung-Ik
2002-10-24 5:10 ` Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH [this message]
2002-10-24 11:49 ` [Linux-ia64] " Matthew Wilcox
2002-10-24 14:52 ` Jeff Garzik
2002-10-24 16:54 ` Greg KH
2002-10-24 17:44 ` [Pcihpd-discuss] " Scott Murray
2002-10-24 21:49 ` Greg KH
2002-10-24 22:22 ` Scott Murray
2002-10-25 15:37 ` Ivan Kokshaysky
2002-10-25 22:02 ` Scott Murray
2002-10-25 22:25 ` Russell King
2002-10-26 23:36 ` Scott Murray
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 16:24 Lee, Jung-Ik
2002-10-24 16:46 ` Greg KH
2002-10-24 17:40 ` Lee, Jung-Ik
2002-10-24 22:06 ` Greg KH
2002-10-24 17:39 ` KOCHI, Takayoshi
2002-10-24 17:52 ` Jeff Garzik
2002-10-24 16:37 Lee, Jung-Ik
2002-10-24 18:39 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=20021024061236.GJ19557@kroah.com \
--to=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).