linux-kernel - Re: [PATCH 2/2] PNP: work around Dell 1536/1546 BIOS MMCONFIG bug that breaks USB

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Jan 2012 09:49:01 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, thuban@...gularity.fr,
	dann frazier <dann.frazier@...onical.com>,
	Lisa Salimbas <lisa.salimbas@...onical.com>,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	Len Brown <lenb@...nel.org>
Subject: Re: [PATCH 2/2] PNP: work around Dell 1536/1546 BIOS MMCONFIG bug
 that breaks USB


* Bjorn Helgaas <bhelgaas@...gle.com> wrote:

> On Thu, Jan 5, 2012 at 2:27 PM, Bjorn Helgaas <bhelgaas@...gle.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.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/