On Sun, 22 Aug 2010 12:05:45 +0100, Chris Wilson
wrote:
> The calculation seem backwards as they compute the number of entries
> that would be drained during a memory fetch, and but return the opposite
> value.
>
> This fixes a common flicker [or even completely scrambled display] on
> high reso
The calculation seem backwards as they compute the number of entries
that would be drained during a memory fetch, and but return the opposite
value.
This fixes a common flicker [or even completely scrambled display] on
high resolution outputs (e.g. 1920x1080 with 915GM). However, as we do not
adju
