All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	David Woodhouse <dwmw2@infradead.org>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Misc fixes for 2.6.27
Date: Tue, 2 Sep 2008 08:19:20 +0200	[thread overview]
Message-ID: <20080902061920.GK18288@one.firstfloor.org> (raw)
In-Reply-To: <20080901161639.5215db63@infradead.org>

On Mon, Sep 01, 2008 at 04:16:39PM -0700, Arjan van de Ven wrote:
> On Tue, 02 Sep 2008 01:01:19 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
> 
> > 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.
> > 
> 
> it would be nice, no doubt, unfortunately this code runs (and needs to
> run) before the PCI subsystem is initialized...

early quirks handles these cases. Check out early-quirks.c

-Andi

-- 
ak@linux.intel.com

  reply	other threads:[~2008-09-02  6:16 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
2008-09-01 23:16       ` Arjan van de Ven
2008-09-02  6:19         ` Andi Kleen [this message]
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=20080902061920.GK18288@one.firstfloor.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 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.