[Bug 98036] [BYT] constant screen flicker and rendering errors [regression]

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Nov 7 12:28:33 UTC 2016


https://bugs.freedesktop.org/show_bug.cgi?id=98036

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #16 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 767a222e47cc13239d38018887f911fec06169ea
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Nov 7 11:01:28 2016 +0000

    drm/i915: Limit Valleyview and earlier to only using mappable scanout

    Valleyview appears to be limited to only scanning out from the first 512MiB
    of the Global GTT. Lets presume that this behaviour was inherited from the
    display block copied from g4x (not Ironlake) and all earlier generations
    are similarly affected, though testing suggests different symptoms. For
    simplicity, impose that these platforms must scanout from the mappable
    region. (For extra simplicity, use HAS_GMCH_DISPLAY even though this
    catches Cherryview which does not appear to be limited to the low
    aperture for its scanout.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161107/917c73f4/attachment.html>


More information about the intel-gfx-bugs mailing list