From: Thomas Richter <thor@math.tu-berlin.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>, linux-kernel@vger.kernel.org
Subject: i835GM flicker on panning
Date: Sun, 22 Sep 2013 19:06:24 +0200 [thread overview]
Message-ID: <523F2390.5030702@math.tu-berlin.de> (raw)
In-Reply-To: <4319_1379778790_523DC0E3_4319_13540_1_CAKMK7uHynzChMurTLAYMfeRF07aDJxes-6eSO1iDbrET8xD84Q@mail.gmail.com>
Hi folks, hi Daniel,
there is still an issue with flicker on panning with the 835GM chipset.
As already explained, the flicker only appears if the panning position
satisfies certain alignment constraints, in specific. As long as the
plane pointer is aligned to 64 byte boundaries, everything works correctly.
I tried now to add a parameter to the kernel to adjust the watermark
level of the chipset and see whether this makes any difference with
regards to the flicker. However, it does not. It seems that the trouble
is not there.
However, I noticed something interesting: If I use a non-native mode of
the display, i.e. enable the scaling feature of the DVO, everything
works, and no flicker ever appears. However, in these situations the
resolution is also lower than that of the native display, and hence the
issue may also be related to the PLL clock.
I also noticed that if I invert the display, i.e. use the rotation
feature, even in the native resolution, nothing flickers, though panning
is rather slow.
Does this somehow ring a bell? Can I somehow force the driver to use the
same logic for the regular display as for the inverted display to avoid
the flicker?
Any help would be appreciated.
Greetings,
Thomas
next prev parent reply other threads:[~2013-09-22 17:17 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 ` Thomas Richter [this message]
2013-09-22 20:03 ` i835GM flicker on panning 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
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=523F2390.5030702@math.tu-berlin.de \
--to=thor@math.tu-berlin.de \
--cc=daniel.vetter@ffwll.ch \
--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