From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 0/3] pci_root: track downstream bus range for _CBA
Date: Thu, 04 Feb 2010 18:29:39 +0000 [thread overview]
Message-ID: <201002041129.40116.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20091110170802.10645.91272.stgit@bob.kio>
On Tuesday 10 November 2009 10:11:28 am Bjorn Helgaas wrote:
> The PCI Firmware Spec requires BIOS to use _CBA, not MCFG, to report
> MMCONFIG regions of hot-pluggable host bridges. Therefore, if the
> hardware and firmware support host bridge hotplug, we will encounter
> _CBA even if Linux itself doesn't support hotplug.
>
> These patches make the pci_root driver keep track of the downstream
> bus range and make it available so arch-specific code can register
> MMCONFIG regions if necessary.
I think these patches got forgotten, but I still think they're
worthwhile. I'd be glad to refresh them if necessary.
Bjorn
next prev parent reply other threads:[~2010-02-04 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 17:11 [PATCH v2 0/3] pci_root: track downstream bus range for _CBA Bjorn Helgaas
2009-11-10 17:11 ` [PATCH v2 1/3] ACPI: pci_root: show entire downstream bus range Bjorn Helgaas
2009-11-10 17:11 ` [PATCH v2 2/3] ACPI: pci_root: save " Bjorn Helgaas
2009-11-10 17:11 ` [PATCH v2 3/3] ACPI: pci_root: pass acpi_pci_root to arch-specific Bjorn Helgaas
2010-02-04 18:29 ` Bjorn Helgaas [this message]
2010-03-09 21:42 ` [PATCH v2 0/3] pci_root: track downstream bus range for _CBA Bjorn Helgaas
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=201002041129.40116.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-pci@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