I just noticed that you are using a 2d BITBLT to temporarily stall the command regulator for a moment.
I believe the XAA implementation in all current via 2d X server drivers out there assume that they are reasonably alone in using the 2d engine and that they expext that some registers are not changed by other applications. This will probably at least break the accelerated X server pixmap cache, unless used 2d engine registers are restored after the BITBLT.
I will change the dummy bitblt to use ROP_D (0xAA) so that I can blit to any framebuffer location without changing its content. Also, the new bitblt will only modify the SRCPOS, DSTPOS, DIMENSION, and CMD registers, all of which are overwritten by DDX for each bitblt.
I plan to clean up the unichrome 2D driver with respect to this, but I'm not sure when this will happen.
W respect to our previous discussion regarding the Mpeg2 decoder I'll try programming it using the 2D commands. It might work. Thanks for the info.
Is there any chance of having a command stream completion interrupt implementation?
/Thomas
------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel