[Bug 36326] [uxa 915GM] Characters sometimes have horizontal lines through them (glyph font corruption)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 14 07:00:48 PST 2012


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |NEW
            Summary|[915GM] Characters          |[uxa 915GM] Characters
                   |sometimes have horizontal   |sometimes have horizontal
                   |lines through them (glyph   |lines through them (glyph
                   |font corruption)            |font corruption)
            Product|DRI                         |xorg
            Version|XOrg CVS                    |git
          Component|DRM/Intel                   |Driver/intel

--- Comment #65 from Chris Wilson <chris at chris-wilson.co.uk> ---
To be honest, I had hoped that this would have proven to be the unfenced-BLT
bug. The known w/a for UXA is to enable DebugWait, which implies that UXA is
not handling its domains correctly.

The most likely candidate is:

diff --git a/src/intel_uxa.c b/src/intel_uxa.c
index 76a3146..40e3b67 100644
--- a/src/intel_uxa.c
+++ b/src/intel_uxa.c
@@ -1379,8 +1379,8 @@ Bool intel_uxa_init(ScreenPtr screen)
        }

        /* PutImage */
-       intel->uxa_driver->put_image = intel_uxa_put_image;
-       intel->uxa_driver->get_image = intel_uxa_get_image;
+       //intel->uxa_driver->put_image = intel_uxa_put_image;
+       //intel->uxa_driver->get_image = intel_uxa_get_image;

        intel->uxa_driver->prepare_access = intel_uxa_prepare_access;
        intel->uxa_driver->finish_access = intel_uxa_finish_access;

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20121214/4138518b/attachment.html>


More information about the intel-gfx-bugs mailing list