From: rajesh.shah@intel.com
To: gregkh@suse.de, ink@jurassic.park.msu.ru, ak@suse.de,
len.brown@intel.com, akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
acpi-devel@lists.sourceforge.net
Subject: [patch 0/2] Collecting host bridge resources - take 2
Date: Thu, 02 Jun 2005 15:41:47 -0700 [thread overview]
Message-ID: <20050602224147.177031000@csdlinux-1> (raw)
ACPI hotplug code now uses the PCI core to allocate and manage
resources for hot-plug devices. To work correctly, this requires
all bridges to report resources they are decoding in their
pci_bus structure. We already do this for PCI-PCI bridges, but
not for host bridges. This patchset reads and stores host bridge
resources reported by ACPI BIOS for i386 and x86_64 systems.
This is the 2nd version of this patchset. The major change is
that it increases the number of resource pointers in the pci_bus
structure and eliminates the need to have a boot time parameter
to enable the code.
Andrew, if you add this to the next -mm, please also drop the
previous version this patchset (i386-collect-host-bridge-resources.patch
and x86_64-collect-host-bridge-resources.patch).
Rajesh
--
next reply other threads:[~2005-06-02 22:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 22:41 rajesh.shah [this message]
2005-06-02 22:41 ` [patch 1/2] Increase the number of PCI bus resources rajesh.shah
2005-06-02 22:41 ` [patch 2/2] i386/x86_64: collect host bridge resources v2 rajesh.shah
2005-06-28 11:51 ` Ivan Kokshaysky
2005-06-28 18:21 ` Kristen Accardi
2005-06-28 20:03 ` Ivan Kokshaysky
2005-06-30 16:05 ` Greg KH
2005-07-01 0:33 ` 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=20050602224147.177031000@csdlinux-1 \
--to=rajesh.shah@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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