public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Richter <thor@math.tu-berlin.de>
To: 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 10:30:15 +0200	[thread overview]
Message-ID: <523FFC17.1090403@math.tu-berlin.de> (raw)
In-Reply-To: <17822_1379921548_523FEE8C_17822_1617_1_20130923073242.GA32145@phenom.ffwll.local>

Hi Daniel, hi others,

>> 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).
>
> Can you please test with
>
>         Option "LinearFramebuffer" "true"?

Did. Still flickers. I'm not quite sure, but it seems to me that there 
is at least one change (but allow me to test): If I'm now panning from 
left to right (move the mouse to the right), then the screen is stable. 
If I move it to the left, I get the flicker. Which is pretty strange.

Unless I'm completely mistaken, the tiled mode created flicker no matter 
whether I scrolled left to right or right to left, it just depended on 
the position. Wierd.

Greetings,
	Thomas


  parent reply	other threads:[~2013-09-23  8:31 UTC|newest]

Thread overview: 13+ 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
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 [this message]
2013-09-23 10:21             ` Thomas Richter
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=523FFC17.1090403@math.tu-berlin.de \
    --to=thor@math.tu-berlin.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox