It is definitely an option, and it is supported on older GPUs with a dedicated 2D acceleration block, we just didn't write any R600 code for that option
The 3D engine is not a particularly good match for the common XAA functions, and modern apps seem to make more use of the operations offered by EXA. Since we already use the 3D engine for most of the EXA functions, and since 6xx/7xx only have a 3D engine, we only implemented EXA and not XAA for those GPU generations. There was some discussion about whether we should implement XAA later, but I don't know what the right answer is there.
Alex mentioned that turning off Composite (Option "NoEXAComposite" in the Device section of your conf file) frequently eliminated the corruption.
monraaf, could you try that option if you have not already done so ?
The 3D engine is not a particularly good match for the common XAA functions, and modern apps seem to make more use of the operations offered by EXA. Since we already use the 3D engine for most of the EXA functions, and since 6xx/7xx only have a 3D engine, we only implemented EXA and not XAA for those GPU generations. There was some discussion about whether we should implement XAA later, but I don't know what the right answer is there.
Alex mentioned that turning off Composite (Option "NoEXAComposite" in the Device section of your conf file) frequently eliminated the corruption.
monraaf, could you try that option if you have not already done so ?
Comment