From: Chris Wilson <chris@chris-wilson.co.uk>
To: Peter Clifton <pcjc2@cam.ac.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Corruption in glxgears with Compiz
Date: Fri, 22 Oct 2010 20:29:40 +0100 [thread overview]
Message-ID: <5b55a1$ien4q1@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <1287774644.17191.9.camel@pcjc2lap>
On Fri, 22 Oct 2010 20:10:44 +0100, Peter Clifton <pcjc2@cam.ac.uk> wrote:
> As an additional data-point, with the bug manifesting, if you go to
> "expose" mode, (Win+E for default config), you find the corruption is
> absent. It only appears to be present when the glxgears window is not
> scaled by the window manager.
My guess is that it is a double application of the drawable offset when
doing a CopyRegion swapbuffers. Does the corruption move in relation to
the window as it moves?
This suggests that [my] recent changes to the ddx are to blame, and
certainly a bisection on -intel might help - though it's probably just as
easy to test before the shadow+dri changes to confirm.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-10-22 19:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 12:53 Corruption in glxgears with Compiz Peter Clifton
2010-10-22 13:39 ` Chris Wilson
2010-10-22 14:04 ` Alexey Fisher
2010-10-22 19:10 ` Peter Clifton
2010-10-22 19:29 ` Chris Wilson [this message]
2010-10-22 19:38 ` Peter Clifton
2010-10-22 20:41 ` Peter Clifton
2010-10-23 3:35 ` Peter Clifton
2010-10-23 4:07 ` Peter Clifton
2010-10-23 8:23 ` Alexey Fisher
2010-10-23 9:10 ` Chris Wilson
2010-10-23 9:43 ` Alexey Fisher
2010-10-23 10:07 ` Chris Wilson
2010-10-23 11:42 ` Peter Clifton
2010-10-23 17:48 ` Chris Wilson
2010-10-23 18:33 ` Peter Clifton
2010-10-24 23:06 ` Peter Clifton
2010-10-22 19:13 ` Peter Clifton
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$ien4q1@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pcjc2@cam.ac.uk \
/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