From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bhelgaas@google.com>
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,
stable@kernel.org, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 2/2] PNP: work around Dell 1536/1546 BIOS MMCONFIG bug that breaks USB
Date: Fri, 6 Jan 2012 12:05:24 -0800 [thread overview]
Message-ID: <20120106120524.7801c73a@jbarnes-desktop> (raw)
In-Reply-To: <20120105212724.3965.30193.stgit@bhelgaas.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
On Thu, 05 Jan 2012 14:27:24 -0700
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.
>
applied these two, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-06 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 21:27 [PATCH 1/2] x86, amd: factor out MMCONFIG discovery Bjorn Helgaas
2012-01-05 21:27 ` [PATCH 2/2] PNP: work around Dell 1536/1546 BIOS MMCONFIG bug that breaks USB Bjorn Helgaas
2012-01-05 21:30 ` Bjorn Helgaas
2012-01-05 21:30 ` Bjorn Helgaas
2012-01-06 8:49 ` Ingo Molnar
2012-01-06 8:49 ` Ingo Molnar
2012-01-06 17:18 ` Bjorn Helgaas
2012-01-06 20:05 ` Jesse Barnes [this message]
2012-01-12 6:52 ` [PATCH 1/2] x86, amd: factor out MMCONFIG discovery Eric Dumazet
2012-01-12 13:56 ` Bjorn Helgaas
2012-01-12 13:56 ` 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=20120106120524.7801c73a@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=dann.frazier@canonical.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa.salimbas@canonical.com \
--cc=mingo@redhat.com \
--cc=stable@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.