From: Thomas Richter <thor@math.tu-berlin.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: i835GM flicker on panning
Date: Mon, 23 Sep 2013 00:33:04 +0200 [thread overview]
Message-ID: <523F7020.702@math.tu-berlin.de> (raw)
In-Reply-To: <16566_1379880205_523F4D0D_16566_5011_1_CAKMK7uFNAhahpURH-LFj=x+8D2W7Z8y_-9OKhnJ_O4g7hyqu1Q@mail.gmail.com>
On 22.09.2013 22:03, Daniel Vetter wrote:
> Hm, that sounds a bit more like the ddx is having fun with rendering.
> Have you tried switching the backed from to either SNA or UXA? Also
> adding relevant mailing lists ...
>
No, whether I use uxa or sna makes no difference, same problem. I don't
think it's rendering related. The rendering is ok (except for some
defects in tuxracer if sna is used instead of uxa).
Greetings,
Thomas
next prev parent reply other threads:[~2013-09-22 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 13:14 i915 pipe A assertion failure (expected on, current off) Meelis Roos
2013-09-21 15:29 ` Meelis Roos
2013-09-21 15:48 ` Daniel Vetter
2013-09-21 16:03 ` Ville Syrjälä
2013-09-22 6:02 ` Meelis Roos
[not found] ` <4319_1379778790_523DC0E3_4319_13540_1_CAKMK7uHynzChMurTLAYMfeRF07aDJxes-6eSO1iDbrET8xD84Q@mail.gmail.com>
2013-09-22 17:06 ` i835GM flicker on panning Thomas Richter
2013-09-22 20:03 ` Daniel Vetter
2013-09-22 21:50 ` [Intel-gfx] " Chris Wilson
[not found] ` <16566_1379880205_523F4D0D_16566_5011_1_CAKMK7uFNAhahpURH-LFj=x+8D2W7Z8y_-9OKhnJ_O4g7hyqu1Q@mail.gmail.com>
2013-09-22 22:33 ` Thomas Richter [this message]
2013-09-23 7:32 ` Daniel Vetter
[not found] ` <17822_1379921548_523FEE8C_17822_1617_1_20130923073242.GA32145@phenom.ffwll.local>
2013-09-23 8:30 ` Thomas Richter
2013-09-23 10:21 ` Thomas Richter
2013-09-24 9:02 ` Daniel Vetter
2013-09-24 9:02 ` [Intel-gfx] " Daniel Vetter
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=523F7020.702@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@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.