lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <523F2390.5030702@math.tu-berlin.de>
Date:	Sun, 22 Sep 2013 19:06:24 +0200
From:	Thomas Richter <thor@...h.tu-berlin.de>
To:	Daniel Vetter <daniel.vetter@...ll.ch>,
	linux-kernel@...r.kernel.org
Subject: i835GM flicker on panning

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ