From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Set persistent-mode for SNB framebuffer compression
Date: Mon, 04 Jul 2011 19:18:11 +0100 [thread overview]
Message-ID: <aefc95$m7c3d@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1309782957-9978-1-git-send-email-chris@chris-wilson.co.uk>
On Mon, 4 Jul 2011 13:35:57 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Persistent mode is intended for use with front-buffer rendering, such as
> X, where it is necessary to detect writes to the scanout either by the
> GPU or through the CPU's fence, and recompress the dirty regions on the
> fly. (By comparison to the back-buffer rendering, the scanout is always
> recompressed after a page-flip.)
>
> This fixes the missing rendering oft triggered in the past, but easily
> reproduced by using mutter with sna, for which the current workaround is
> to disable fbc entirely.
Hah. Spoke too soon, actually testing it, it seems the fix was due to the
little buglet in the first patch which had the effect of disabling FBC.
Oh well, it was a nice idea.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-07-04 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 19:48 [PATCH] drm/i915: set persistent mode for fbc Ben Widawsky
2011-07-02 7:16 ` Chris Wilson
2011-07-03 11:01 ` Chris Wilson
2011-07-03 15:32 ` Ben Widawsky
2011-07-04 12:35 ` [PATCH] drm/i915: Set persistent-mode for SNB framebuffer compression Chris Wilson
2011-07-04 18:18 ` Chris Wilson [this message]
2011-07-04 21:22 ` Ben Widawsky
2011-07-04 18:23 ` Keith Packard
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='aefc95$m7c3d@orsmga001.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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.