From: David Woodhouse <dwmw2@infradead.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
"Sankaran, Rajesh" <rajesh.sankaran@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
Adam Jackson <ajax@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] iommu/intel: disable DMAR for g4x integrated gfx
Date: Mon, 21 Jan 2013 13:03:48 -0600 [thread overview]
Message-ID: <1358795028.5523.6.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1358722213-2075-1-git-send-email-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
On Sun, 2013-01-20 at 23:50 +0100, Daniel Vetter wrote:
> DMAR support on g4x/gm45 integrated gpus seems to be totally busted.
> So don't bother, but instead disable it by default to allow distros to
> unconditionally enable DMAR support.
Acked-By: David Woodhouse <David.Woodhouse@intel.com>
It *really* winds me up that we never bother to test this hardware
before we ship it.
But I'm even *more* disappointed that we can't even diagnose it and
publish coherent errata *after* the fact. I'd really like to see each
quirk which disables features referencing a specific published erratum.
We really ought to be able to manage at least *that* much.
Rajesh?
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2013-01-21 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 22:50 [PATCH] iommu/intel: disable DMAR for g4x integrated gfx Daniel Vetter
2013-01-21 19:03 ` David Woodhouse [this message]
2013-01-22 22:39 ` Daniel Vetter
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=1358795028.5523.6.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=ajax@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rajesh.sankaran@intel.com \
--cc=stable@vger.kernel.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