On Tue, 11 Apr 2006, Mark Vojkovich wrote:
This is probably either a r128 driver bug or a bug in the
acceleration architecture (XAA). If you had access to a non-ATI
video card that would be an interesting test. What might fix
the problem without resorting to "NoAccel" is to prevent XAA
from putting pixmaps in videoram. You can do that with:
Option "XaaNoOffscreenPixmaps"
If this was a r128 driver bug related to rendering to offscreen
videoram or if this was an XAA problem related to rendering to
backing store's backing pixmap, that would probably fix the problem.
If it were a problem with XAA breaking backing store's wrappers,
it probably wouldn't. But there may be other causes - perhaps
that driver disables something else when disabling acceleration.
From looking through driver code, it does appear that "NoAccel"
also disables some things related to 3D.
I think it likely this is an issue with the driver's handling of scissors.
See if the problem disappears when you set both ...
Option "XaaNoScanlineCPUToScreenColorExpandFill"
... and ...
Option "XaaNoScanlineImageWriteRect"
If this works, the driver's other XAA primitives will need to be changed to
reset the scissors to their default values.
Marc.
+----------------------------------+-----------------------------------+
| Marc Aurele La France | work: 1-780-492-9310 |
| Academic Information and | fax: 1-780-492-1729 |
| Communications Technologies | email: tsi@xxxxxxxxxxx |
| 352 General Services Building +-----------------------------------+
| University of Alberta | |
| Edmonton, Alberta | Standard disclaimers apply |
| T6G 2H1 | |
| CANADA | |
+----------------------------------+-----------------------------------+
XFree86 developer and VP. ATI driver and X server internals.
_______________________________________________
Devel@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/devel
