From: Bjorn Helgaas <bhelgaas@google.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
thuban@singularity.fr, dann frazier <dann.frazier@canonical.com>,
Lisa Salimbas <lisa.salimbas@canonical.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Len Brown <lenb@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 2/2] PNP: work around Dell 1536/1546 BIOS MMCONFIG bug that breaks USB
Date: Fri, 6 Jan 2012 10:18:49 -0700 [thread overview]
Message-ID: <CAErSpo57X-rqHgGPk0JsLLjNOAd9TKPSXotx7srcavuSEdCS0w@mail.gmail.com> (raw)
In-Reply-To: <20120106084901.GD14188@elte.hu>
On Fri, Jan 6, 2012 at 1:49 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Bjorn Helgaas <bhelgaas@google.com> wrote:
>
>> On Thu, Jan 5, 2012 at 2:27 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
>> > Some Dell BIOSes have MCFG tables that don't report the entire
>> > MMCONFIG area claimed by the chipset. If we move PCI devices into
>> > that claimed-but-unreported area, they don't work.
>> >
>> > This quirk reads the AMD MMCONFIG MSRs and adds PNP0C01 resources as
>> > needed to cover the entire area.
>>
>> PNP stuff usually goes through Len's ACPI tree, but this is
>> really x86-specific, and these two patches need to go
>> together, so I think it would make sense to put them both in
>> the x86 tree. Len, do you object?
>
> I'd really suggest the PCI tree for this - mmconfig is really
> PCI related.
OK, Jesse, would you like to pick up these two patches?
Bjorn
parent reply other threads:[~2012-01-06 17:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20120106084901.GD14188@elte.hu>]
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=CAErSpo57X-rqHgGPk0JsLLjNOAd9TKPSXotx7srcavuSEdCS0w@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=dann.frazier@canonical.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lisa.salimbas@canonical.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thuban@singularity.fr \
/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;
as well as URLs for NNTP newsgroup(s).