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;
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 init(ScreenPtr screen)
index 76a3146..40e3b67 100644
--- a/src/intel_uxa.c
+++ b/src/intel_uxa.c
@@ -1379,8 +1379,8 @@ Bool intel_uxa_
}
/* PutImage */ uxa_driver- >put_image = intel_uxa_ put_image; uxa_driver- >get_image = intel_uxa_ get_image; >uxa_driver- >put_image = intel_uxa_ put_image; >uxa_driver- >get_image = intel_uxa_ get_image;
- intel->
- intel->
+ //intel-
+ //intel-