"Brian S. Julin" <[EMAIL PROTECTED]> wrote: > 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 principle yes, but you's need to sync the framebuffer contents with the accelerated drawing operations as well, as otherwise the next flush would overwrite already drawn contents. > 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. Ah - I see. > Does someone know the original reason why the DGA target kept a private > implementation of the XFDGA protocol extension? This is due to a horrid versionning nightmare while the XFree 3->4 Transition, where we found that many systems had broken headers and would not compile right. CU, ANdy -- = Andreas Beck | Email : <[EMAIL PROTECTED]> =
