radeon_cursor

[Michel Dänzer]

On Sun, 2005-01-02 at 15:19 -0500, Vladimir Dergachev wrote:
> 
>   My understanding is that the cursor update runs in a separate thread (as 
> the mouse still works when the server is otherwise locked up).

I've been fooled by this before as well, but no. Only mouse movement is
handled asynchronously.


>   However, CURSOR_SWAPPING_START() does not contain anything to wait for 
> engine idle, which seems to imply that we can be writing cursor data while 
> the engine is busy.

Yes.

>   This is indeed what I see with R300 - when glxtest is running full speed
> I get a lockup when mouse crosses window boundaries (this involves 
> changing cursor shape because of window manager).

Have you verified that this doesn't happen with SW cursor as well?


-- 
Earthling Michel Dänzer      |     Debian (powerpc), X and DRI developer
Libre software enthusiast    |   http://svcs.affero.net/rm.php?r=daenzer