On Tue, 2005-03-15 at 09:53 -0500, Alex Deucher wrote: > On Mon, 14 Mar 2005 22:14:25 -0500 (EST), Vladimir Dergachev > <[EMAIL PROTECTED]> wrote: > > > > This would mean that on r300 this fix is not needed, but rv350 locks up > > without it. > > In that case perhaps it makes sense to only wait for idle on rv3xx. I > don't know if it makes sense to break one setup to fix another.
Certainly not, but I don't think the wait for idle makes sense in the first place. There is no rule that you have to wait for idle before reading a register, and the fglrx driver doesn't do anything like that. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- 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
