From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rajesh Shah Date: Fri, 18 Mar 2005 22:34:10 +0000 Subject: FW: [RFC/Patch 0/12] ACPI based root bridge hot-add Message-Id: <20050318143410.A1753@unix-os.sc.intel.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Cc: linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org I just sent out a series of acpi based root bridge hot-add patches. I realized that I didn't send the explanation to all the mailing lists, sorry. Rajesh ----- Forwarded message from Rajesh Shah ----- > Date: Fri, 18 Mar 2005 13:38:57 -0800 > From: Rajesh Shah > To: gregkh@suse.de > Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org, > pcihpd-discuss@lists.sourceforge.net > Subject: [RFC/Patch 0/12] ACPI based root bridge hot-add > > Here is a series of patches to support ACPI hot-add of a root > bridge hierarchy. The added hierarchy may contain other p2p > bridges and end/leaf I/O devices too. The root bridge itself is > assumed to have been assigned resource ranges, but the p2p > bridges and end devices are not required to be initialized by > firmware. Most of the code changes are to make the existing code > flows suitable for such a hierarchy of bridges & devices. > > This code supports hot-add on ia64 only for now.It does not yet > support I/O APIC hot-add, which is needed to make this fully > functional. The patches are against 2.6.11-mm4 (plus the patch > needed for ia64 to boot). I've tested to make sure this does not > break end/leaf device hotplug on the hotplug capable ia64 box I have. > > Thanks, > Rajesh ----- End forwarded message -----