From: Greg KH <greg@kroah.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: PCI Hotplug Drivers for 2.5
Date: Thu, 24 Oct 2002 06:12:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805225@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805223@msgid-missing>
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:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 5:10 [Linux-ia64] Re: PCI Hotplug Drivers for 2.5 Greg KH
2002-10-24 5:59 ` KOCHI, Takayoshi
2002-10-24 6:12 ` Greg KH [this message]
2002-10-24 11:49 ` Matthew Wilcox
2002-10-24 14:52 ` Jeff Garzik
2002-10-24 16:24 ` [Linux-ia64] " Lee, Jung-Ik
2002-10-24 16:37 ` Lee, Jung-Ik
2002-10-24 16:46 ` [Linux-ia64] " Greg KH
2002-10-24 16:54 ` Greg KH
2002-10-24 17:39 ` KOCHI, Takayoshi
2002-10-24 17:40 ` [Linux-ia64] " Lee, Jung-Ik
2002-10-24 17:52 ` [Linux-ia64] " Jeff Garzik
2002-10-24 17:59 ` [Linux-ia64] " Matthew Wilcox
2002-10-24 18:19 ` Lee, Jung-Ik
2002-10-24 18:39 ` Lee, Jung-Ik
2002-10-24 22:06 ` [Linux-ia64] " Greg KH
-- strict thread matches above, loose matches on Subject: below --
2002-10-24 18:19 [Linux-ia64] " Lee, Jung-Ik
2002-10-24 17:40 Lee, Jung-Ik
2002-10-24 17:59 ` [Linux-ia64] " Matthew Wilcox
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=marc-linux-ia64-105590709805225@msgid-missing \
--to=greg@kroah.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.