From: Chris Wilson <chris@chris-wilson.co.uk>
To: Keith Packard <keithp@keithp.com>, Matthias Hopf <mhopf@suse.de>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Dont use hardware acceleration on Sandybridge rev 07 hardware or earlier.
Date: Sun, 21 Nov 2010 09:03:05 +0000 [thread overview]
Message-ID: <5b55a1$inmn1b@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <yunwro7s4wp.fsf@aiko.keithp.com>
On Sat, 20 Nov 2010 19:59:34 -0800, Keith Packard <keithp@keithp.com> wrote:
> On Sat, 20 Nov 2010 16:17:40 +0100, Matthias Hopf <mhopf@suse.de> wrote:
>
> > I know, I know. The patch is (one of) the results of the Novell-HP-Intel
> > workshop in Taipei this week. It turned out that rev07 is too unstable.
> > Keith and Eric can probably comment on this. Better than I can.
>
> There's a work-around in the kernel for pre rev-8 hardware that ensures
> every time the blt ring is advanced by the CPU, the first command
> executes a batch buffer. So the hardware is obviously quite broken.
>
> This workaround doesn't work perfectly, and the GPU will still lock up
> when executing commands out of the blt ring from time to time. As pre
> rev-8 hardware is all pre-production, the workarounds should be removed
> From the driver and all acceleration disabled.
Ah ha! If it's the BLT workaround, then yes that can die in a very hot
fire. Thanks for the explanation.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-11-21 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 3:29 [PATCH] Don't use hardware acceleration on Sandybridge rev 07 hardware or earlier Matthias Hopf
2010-11-19 21:47 ` [PATCH] Dont " Chris Wilson
2010-11-20 15:17 ` Matthias Hopf
2010-11-21 3:59 ` Keith Packard
2010-11-21 9:03 ` Chris Wilson [this message]
2010-11-24 3:13 ` Zou, Nanhai
2010-12-05 11:44 ` Chris Wilson
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='5b55a1$inmn1b@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keithp@keithp.com \
--cc=mhopf@suse.de \
/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