From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Misc fixes for 2.6.27
Date: Tue, 02 Sep 2008 01:01:19 +0200 [thread overview]
Message-ID: <87sksjwjwg.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080901153517.2f8b1ef8@infradead.org> (Arjan van de Ven's message of "Mon, 1 Sep 2008 15:35:17 -0700")
Arjan van de Ven <arjan@infradead.org> writes:
> On Tue, 02 Sep 2008 00:32:16 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
>
>> David Woodhouse <dwmw2@infradead.org> writes:
>> > +
>> > +static struct dmi_system_id __initdata intel_iommu_dmi_table[] = {
>> > + { /* Some DG33BU BIOS revisions advertised
>> > non-existent VT-d */
>>
>> Are you sure it's non existent? A G33 chipset should have it in
>> hardware I thought.
>
> nope they don't/
> later ones and some other models do though, but not the G33
I see. But presumably that chipset will be in other motherboards
too and that BIOS bug might be also wider spread. So it would be still
better to key off an PCI-ID or similar.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-09-01 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 20:14 Misc fixes for 2.6.27 David Woodhouse
2008-09-01 22:32 ` Andi Kleen
2008-09-01 22:35 ` Arjan van de Ven
2008-09-01 23:01 ` Andi Kleen [this message]
2008-09-01 23:16 ` Arjan van de Ven
2008-09-02 6:19 ` Andi Kleen
2008-09-02 8:23 ` David Woodhouse
2008-09-03 10:53 ` Blacklist DMAR on Intel G31/G33 chipsets David Woodhouse
2008-09-03 12:09 ` Andi Kleen
2008-09-03 12:22 ` David Woodhouse
2008-09-04 8:54 ` [PATCH] " David Woodhouse
2008-09-05 18:34 ` Ingo Molnar
2008-09-05 18:47 ` David Woodhouse
2008-09-06 15:49 ` Ingo Molnar
2008-09-07 8:20 ` David Woodhouse
2008-09-07 15:35 ` [2.6.27 PATCH] " David Woodhouse
2008-09-09 18:39 ` Jesse Barnes
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=87sksjwjwg.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=arjan@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).