Luc Verhaegen 59f9fb4b8c XAA PixmapOps: Sync before accessing unwrapped callbacks. ... When using any XAAPixmapOps, we call into unknown but freshly unwrapped callbacks (like fb ones). Unlike the XAA*Fallback calls, we did so without syncing first, exposing us to all kinds of synchronisation issues. I believe that the rendering errors appeared now because *PaintWindow vanished (e4d11e58), and we just use miPaintWindow instead. This takes a less direct route to the hw and ends up at PolyFillRectPixmap, which very often left drawing artifacts. We now sync accordingly, and no longer get the rendering artifacts i was methodically reproducing on radeonhd, radeon, unichrome... Also, in order to allow driver authors to remove extensive syncing or flushing to hide this issue, create XAA_VERSION_ defines, put them in xaa.h and bump the patchlevel. (novell bug #435791)		2008-11-07 19:13:58 +01:00
..
dmx	dmx: avoid hilarious #define Xcalloc xcalloc game.	2008-10-17 10:19:11 +10:30
kdrive	kdrive: Bye bye Xvesa	2008-11-05 11:39:46 -05:00
vfb	Unifdef AIX.	2008-07-23 13:37:42 -04:00
xfree86	XAA PixmapOps: Sync before accessing unwrapped callbacks.	2008-11-07 19:13:58 +01:00
xnest	xnest: I'm sure xfree works fine, even if we're 64 bit.	2008-11-04 16:01:42 +10:30
xquartz	XQuartz: Make LS parse our version properly... it didn't like our CFBundleVersion	2008-11-06 14:49:54 -08:00
xwin	xalloc+memset(0) -> xcalloc	2008-10-06 15:36:51 -04:00
Makefile.am	Remove xgl.	2008-06-12 16:00:50 -04:00