Eric Anholt 759033703c Remove the exaAsyncPixmapGCOps mostly-unaccelerated ops vector, and always ...

plug in the accelerated one, even if the destination pixmap is
    currently offscreen. This was a leftover from when kaa originally got
    accelerated offscreen pixmap support, and its only concievable use was
    to avoid a little overhead on ops to in-system pixmaps that weren't
    going to get migrated. At this point, we probably care more about just
    getting everything accelerated that we easily can, which should happen
    with the new migration support.

2006-03-30 21:44:36 +00:00

..

exa_accel.c

Don't do an extra fallback path for CopyWindow while swappedOut, since

2006-03-30 21:25:43 +00:00

exa_migration.c

Change EXA so that exaMoveOutPixmap() retains the framebuffer copy of the

2006-03-16 18:43:55 +00:00

exa_offscreen.c

Do a first pass of doxygen documentation of EXA. This removes the

2006-03-09 23:18:15 +00:00

exa_priv.h

Remove the exaAsyncPixmapGCOps mostly-unaccelerated ops vector, and always

2006-03-30 21:44:36 +00:00

exa_render.c

Move migration logic to a new function, exaDoMigration(). This is largely a

2006-03-14 21:30:12 +00:00

exa_unaccel.c

Remove the exaAsyncPixmapGCOps mostly-unaccelerated ops vector, and always

2006-03-30 21:44:36 +00:00

exa.c

Remove the exaAsyncPixmapGCOps mostly-unaccelerated ops vector, and always

2006-03-30 21:44:36 +00:00

exa.h

Add more doxygen documentation, including notes on WaitMarker() and

2006-03-15 00:13:52 +00:00

Makefile.am

Move EXA implementation up to the top level and remove its XFree86

2006-02-16 00:14:11 +00:00