Also, I have no idea why the code in radeon_cursor.c that writes images directly into framebuffer memory works - according to the manual any writes into framebuffer while GUI is active should cause a hard lock.
However, I could not produce any lockups with it, and so left it as is.
I can see no difference at all with this latest change, i.e. no regressions, but the lockup is still there.
I think we can safely assume that there is more than one issue.
For example, I am often seeing about 2-sec delay upon the start of a GL app (all 2d updates are frozen). The delay always happens upon the first GL context after a cold reboot, and it is often not present on successive launches of GL apps.
I just tried to check for "partly covered window lockup" bug - glxgears appears to be entirely indifferent to whether anything is covering it.
As for gl-117 - I just tried it and it segfaults due to undefined functions to handle vertex buffers.
best
Vladimir Dergachev
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
