[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1220444531.2985.124.camel@pmac.infradead.org>
Date: Wed, 03 Sep 2008 13:22:11 +0100
From: David Woodhouse <dwmw2@...radead.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: linux-kernel@...r.kernel.org, arjan@...radead.org,
"Sankaran, Rajesh" <rajesh.sankaran@...el.com>,
"Bork, Jon" <jon.bork@...el.com>
Subject: Re: Blacklist DMAR on Intel G31/G33 chipsets
On Wed, 2008-09-03 at 14:09 +0200, Andi Kleen wrote:
> > @@ -114,6 +128,10 @@ static struct chipset early_qrk[] __initdata = {
> > PCI_CLASS_BRIDGE_PCI, PCI_ANY_ID, QFLAG_APPLY_ONCE, via_bugs },
> > { PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_K8_NB,
> > PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, fix_hypertransport_config },
> > +#ifdef CONFIG_DMAR
> > + { PCI_VENDOR_ID_INTEL, 0x29c0,
> > + PCI_CLASS_BRIDGE_HOST, PCI_ANY_ID, 0, intel_g33_dmar },
> > +#endif
>
> Are you sure 0x29c0 is only used on the G31/G33?
And P35 and P31, but nothing with an IOMMU, I believe. The G35 is
8086:2980.
But still I'd be slightly happier using a DMI match on the only
_motherboard_ we've seen so far with this BIOS bug. We can easily add
new motherboards if it does show up elsewhere.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@...el.com Intel Corporation
--
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/
Powered by blists - more mailing lists