From: Rajesh Shah <rajesh.shah@intel.com>
To: Paul Ionescu <i_p_a_u_l@yahoo.com>
Cc: acpi-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Re: [RFC/Patch 0/12] ACPI based root bridge hot-add
Date: Mon, 21 Mar 2005 11:14:49 -0800 [thread overview]
Message-ID: <20050321111449.A5052@unix-os.sc.intel.com> (raw)
In-Reply-To: <pan.2005.03.19.13.50.15.938352@yahoo.com>; from i_p_a_u_l@yahoo.com on Sat, Mar 19, 2005 at 03:50:16PM +0200
On Sat, Mar 19, 2005 at 03:50:16PM +0200, Paul Ionescu wrote:
>
> Does this mean that when it will be ported for i386, I will be able to
> really use my Docking Station ?
No. The current patches only trigger when a _root_ bridge is
hot-added, not a PCI to PCI bridge (which is what the docking
station is). The code to support p2p bridge hotplug will benefit
from these patches but more code is needed to support that.
> Does it rescan the DSDT to find new additions to ACPI devices ?
>
It scans the ACPI namespace under the root bridge that was added.
Any pci devices underneath are scanned and added, but there isn't
any code to look for non-PCI devices there.
Rajesh
next prev parent reply other threads:[~2005-03-21 19:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-18 21:38 [RFC/Patch 0/12] ACPI based root bridge hot-add Rajesh Shah
2005-03-18 21:48 ` [Patch 1/12] " Rajesh Shah
2005-03-18 21:59 ` [Patch 2/12] Fix pci_enable_device() for p2p bridges Rajesh Shah
2005-03-18 22:02 ` [patch 03/12] Make pcibios_fixup_bus() hot-plug safe Rajesh Shah
2005-03-18 22:04 ` [patch 04/12] Prevent duplicate bus numbers when scanning PCI bridge Rajesh Shah
2005-03-18 22:07 ` [patch 05/12] Take the PCI lock when modifying pci bus or device lists Rajesh Shah
2005-03-18 22:09 ` [patch 06/12] Link newly created pci child bus to its parent on creation Rajesh Shah
2005-03-18 22:11 ` [patch 07/12] Make the PCI remove routines safe for failed hot-plug Rajesh Shah
2005-03-19 5:14 ` Greg KH
2005-03-18 22:14 ` [patch 08/12] Remove hot-plugged devices that could not be allocated resources Rajesh Shah
2005-03-18 22:16 ` [patch 09/12] Read bridge resources when fixing up the bus Rajesh Shah
2005-03-18 22:18 ` [patch 10/12] Allow ACPI .add and .start operations to be done independently Rajesh Shah
2005-03-18 22:20 ` [patch 11/12] Export the interface to get PCI id for an ACPI handle Rajesh Shah
2005-03-18 22:22 ` [patch 12/12] ACPI based root bridge hot-add Rajesh Shah
2005-03-19 5:13 ` [RFC/Patch 0/12] " Greg KH
2005-03-21 18:04 ` Rajesh Shah
2005-03-21 18:27 ` Greg KH
2005-03-31 19:06 ` Len Brown
2005-03-19 13:50 ` Paul Ionescu
2005-03-21 19:14 ` Rajesh Shah [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-21 20:34 [ACPI] " Paul Ionescu
2005-03-21 22:57 ` Rajesh Shah
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=20050321111449.A5052@unix-os.sc.intel.com \
--to=rajesh.shah@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=i_p_a_u_l@yahoo.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