I'm thinking of re-unifying the X targets.
In the case of x vs xlib, it strikes me that the back-buffer/flushing behavior and the Xlib accel behavior could cooexist happily as two options in the same driver, what when both enabled would provide the best performance in the genaral cases (same host or network). In the case of the DGA target, it appears to me that XQueryExtension() is a core Xlib function and could be used to enable/disable DGA support. Default behavior would then be to check to see if DGA will work, and if not, simultaneously draw in memory and using X primitives and turn on flushing if/when the directbuffer is aquired. Does someone know the original reason why the DGA target kept a private implementation of the XFDGA protocol extension? I am trying to decide between this and having helper .so's that insulate the main xlib sublib from requiring symbols from X11/Xfree86 extension sublibs, with perhaps some patchup functions for badly implemented commands. -- Brian
