On Mon, 14 Mar 2005, Adam K Kirchhoff wrote:
Michel DÃnzer wrote:
On Mon, 2005-03-14 at 18:05 -0500, Vladimir Dergachev wrote:
I am unsure of how to fix it though, as the call *is* needed, we should not be reading from registers with engine busy.
Something may be needed, but probably not a wait for idle (which may never succeed on an SMP system). Other things you could try:
* Keep track of the hardware state in the driver, so you don't have to read the registers all the time. * Read/write the registers via MM_INDEX/MM_DATA instead of directly.
I'm curious if either of this helps.
Well, I thought I'd also point out that this solves the lockups I was experiecing with the r300 driver, too :-)
Really ? And you can move cursor freely on r300 without lockups ?
This would mean that on r300 this fix is not needed, but rv350 locks up without it.
best
Vladimir Dergachev
Adam
------------------------------------------------------- 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_ide95&alloc_id396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel