From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Ben Widawsky <ben@bwidawsk.net>,
intel-gfx@lists.freedesktop.org, stable <stable@vger.kernel.org>,
Bernard Kilarski <bernard.r.kilarski@intel.com>
Subject: Re: [PATCH] drm/i915: [GEN7] Use HW scheduler for fixed function shaders
Date: Mon, 21 May 2012 07:56:15 -0700 [thread overview]
Message-ID: <20120521075615.0afbdd79@jbarnes-desktop> (raw)
In-Reply-To: <CAKMK7uHHuRwTdc2bPCj=9sr=GOQXLcWz=Yh8Za44_cU=pz-iRA@mail.gmail.com>
On Sun, 20 May 2012 21:24:15 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Apr 18, 2012 at 5:33 PM, Daniel Vetter <daniel@ffwll.ch> wrote:
> > Jesse, can you also please check whether we need the same thing on vlv?
> > atm the the clock gating functions are almost identical safe for this wrt
> > touching registers in the gt core.
>
> Prod.
>
> Now that you have a vlv, no more excuses ;-)
I've got one more: I'm waiting on a dediprog so I can upgrade the
BIOS. The machine is stable unless I try to use gfx at the moment
because a BIOS change prevented the GPU from coming out of reset.
I was able to do some work on the VGA console side of things (adding a
couple of needed workarounds); hopefully I'll be able to refresh this
patchset this week or next and do the sprite stuff too.
Bernard's team may have one for testing by now too though; so they can
provide an answer on this thread.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-05-21 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 1:41 [PATCH] drm/i915: [GEN7] Use HW scheduler for fixed function shaders Ben Widawsky
2012-04-15 14:55 ` Eugeni Dodonov
2012-04-15 17:14 ` Ben Widawsky
2012-04-18 15:33 ` Daniel Vetter
2012-05-20 19:24 ` Daniel Vetter
2012-05-21 14:56 ` Jesse Barnes [this message]
2012-04-16 23:18 ` Kenneth Graunke
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=20120521075615.0afbdd79@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=ben@bwidawsk.net \
--cc=bernard.r.kilarski@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--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 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.