> > Obviously :-) Otherwise the trace in my last mail would have indicated a > crash, but it recovered from that. > > It does seem like a good idea to know how much we just gave the card to do > though, so we have some idea to how long to wait next time we do wait. > > It may be significant is that the problem I'm getting occurs the first time > it does do_cp_idle() when the FIFO was not *already* empty. This is to say, > if it has to wait at all, it will go all funny. > > I checked out the new stuff and ran with RADEON_DEBUG_SANITY, and it didn't > flag anything, though the fix for the tuxkart hang seems to have made the > wireframe highlight boxes it uses to indicate the currently selected object > spray lines randomly around the screen.
Yes, it's not a proper fix. I'm going on holidays from tomorrow, if I can't get something decent committed before then, I'll at least clean up the spindlies.. Keith _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
