From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: re-enable rc6 for ironlake
Date: Wed, 27 Apr 2011 23:03:14 +0100 [thread overview]
Message-ID: <1bdc18$kd76j0@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20110427142009.710aae54@jbarnes-vaio.home>
On Wed, 27 Apr 2011 14:20:09 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Wed, 27 Apr 2011 08:49:28 +0100
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> > On Fri, 18 Mar 2011 16:12:48 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> > > The previous patches should fix enough of the known issues to try
> > > re-enabling rc6 for general consumption
> >
> > Yay, and they bring back the old bugs! :)
> >
> > So upon enabling fbc on a 2560x1440 external panel, it goes blank again.
> > The same symptoms as prompted disabling fbc last year. Can anyone confirm
> > this bad behaviour?
>
> Re-enabling rc6 causes problems when you enable fbc?
Yes, I'm pretty sure that's the causal link. Disabling the LVDS makes the
external DP go haywire, with fbc enabled for the external, but worked fine
until we tried to enable rc6 again. If I remember my bugs correctly, pure
fbc failures resulted in a stripy display, whereas this is a solid
corruption. And I'm pretty certain this is the same bug that convinced me
to disable rc6 the last time.
> We should probably just enable fbc on the pipe connected to the
> internal panel (if any) and keep it disabled otherwise.
On Arrandale, fbc is potentially a bigger win than rc6 - but is also a
potential loss - right?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-27 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 23:12 [PATCH 0/4] Re-enable RC6 on Ironlake Ben Widawsky
2011-03-18 23:12 ` [PATCH 1/4] drm/i915: fix ilk rc6 teardown locking Ben Widawsky
2011-03-19 7:44 ` Chris Wilson
2011-03-19 18:38 ` [PATCH v2 " Ben Widawsky
2011-03-19 18:46 ` [PATCH " Keith Packard
2011-03-20 1:14 ` [PATCH v2 1/5] " Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 2/5] drm/1915: ringbuffer wait for idle function Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 3/5] drm/i915: fix rc6 initialization on Ironlake Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 4/5] drm/i915: debugfs for context information Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 5/5] drm/i915: re-enable rc6 for ironlake Ben Widawsky
2011-03-18 23:12 ` [PATCH 2/4] drm/i915: fix rc6 initialization on Ironlake Ben Widawsky
2011-03-19 7:55 ` Chris Wilson
2011-03-20 0:07 ` Ben Widawsky
2011-03-18 23:12 ` [PATCH 3/4] drm/i915: debugfs for context information Ben Widawsky
2011-03-18 23:12 ` [PATCH 4/4] drm/i915: re-enable rc6 for ironlake Ben Widawsky
2011-04-27 7:49 ` Chris Wilson
2011-04-27 21:20 ` Jesse Barnes
2011-04-27 22:03 ` Chris Wilson [this message]
2011-04-27 22:49 ` Jesse Barnes
2011-04-28 17:10 ` Ben Widawsky
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='1bdc18$kd76j0@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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).