radeon_cursor

[Thomas Winischhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michel Dänzer wrote:
| 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.


So, is it possible that other driver functions are being interrupted by
that mouse thread?

I have a slightly different problem: It currently write an X driver for
USB2VGA dongles. The kernel driver for this device provides a device
file to/from which all hardware access goes to/comes from.

Using the HW cursor, I get lockups quite frequently (because the kernel
device blocks concurrent read/writes). Using the SW cursor works just fine.

My suspiction is that the HW cursor's position setting gets hung in the
wait queue, producing a "classic" race.

Thomas

- --
Thomas Winischhofer
Vienna/Austria
thomas AT winischhofer DOT net	       *** http://www.winischhofer.net
twini AT xfree86 DOT org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB5k72zydIRAktyUcRAj1zAJ9CsAJS/mz8XXgu3QKIs1Xeu2MDKgCfcxgc
fKGIk8oKacqRDse+6dUMY3A=
=geyH
-----END PGP SIGNATURE-----