On Thu, May 30, 2002 at 01:10:48AM +0100, Tim Smith wrote: > Hmmm. The following may be useful information: > > I've added some traces to read the free space in the FIFO each time > COMMIT_RING() happens, and also in radeon_do_wait_for_fifo() to trace out > the min/max number of FIFO slots it found in the loop if it failed. > > After the hefty call to radeon_cp_cmdbuf() mentioned in a previous post, > here's the trace I get:
I've just generated *Error* out of fifo with q3 in a window, hitting ` to get the mouse and either maximising a konsole over the top or just switching to another desktop. I'd just set supposedly 28mb of ring buffer too. Now X c r a w l s at this point, but switching back to q3 you can play quake, frame rates seem fine, with just the chattering of continual *Error* out of fifo messages being written until you quit the game. -- Michael. _______________________________________________________________ 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
