EXA support for the MGA driver - Offscreen memory problems
tilman at code-monkey.de
Tue Sep 5 07:50:28 PDT 2006
I'm trying to complete EXA support for MGA (or rather, finish porting
the kdrive code), but I've got problems related to offscreen memory.
If I set the EXA_OFFSCREEN_PIXMAPS flag, the composite hooks will break.
This can be seen easily cause I'm getting an corrupted mouse cursor
(using a xcursor theme; it's rendering an 32 bpp ARGB cursor onto my 16
bpp desktop). There's other render ops that fail, but it's probably
irrelevant which ones. Unsetting the EXA_OFFSCREEN_PIXMAPS flags makes
everything work nicely.
I'm pretty sure that memoryBase, memorySize, offScreenBase are
initialized properly. The offscreen memory area doesn't overlap the area
that's used to draw/control the hardware cursor. Disabling the hardware
cursor doesn't influence the rendering.
I disabled DRI and XVideo support just to make sure that these aren't
messing with the offscreen memory, but that didn't help either.
Now, the funky thing is, that this problem doesn't occur reliably, but
it's somewhat random --- sometimes after a reboot it works well,
sometimes it doesn't. It won't change without rebooting though.
I think this means that the card might not be initialized properly,
Any advice what might cause the offscreen memory problems? Or is there
no point in trying to track that one down when it seems like there's an
initialization problem somewhere?
Thanks in advance, this is getting pretty annoying ;)
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the xorg