On Sun, 14 Jul 2002 19:59:08 +0100
José Fonseca <[EMAIL PROTECTED]> wrote:

> On Sat, Jul 13, 2002 at 08:12:26PM -0400, Leif Delgass wrote:
> > On Sat, 13 Jul 2002, Leif Delgass wrote:
> > 
> > > On Sun, 14 Jul 2002, José Fonseca wrote:
> > > 
> > > > But the fact remains that the reads from GUI_STAT aren't reliable. I
> > > > wonder if the chip creats some transient values...
> > > 
> > > I wonder if always reading FIFO_STAT before GUI_STAT would make a
> > > difference.  The register reference says that the GUI_ACTIVE bit in
> > > GUI_STAT would be set if the FIFO is not empty, but all the sample code I
> > > recall looking at waits for idle by reading FIFO_STAT to make sure the
> > > last 16 slots are not filled, and _then_ reads GUI_STAT.  It always seemed
> > > like overkill, but maybe reading FIFO_STAT somehow updates GUI_STAT.
> > 
> > I looked at the idle function in the DDX, and it only reads FIFO_STAT for 
> > chips earlier than the VTB.  It relies on the GUI_FIFO bits of GUI_STAT 
> > for all Rage Pro chips and above, so it seems unlikely that reading 
> > FIFO_STAT would make a difference.
> 
> Ok. Let's try the following then: call do_wait_for_idle when the engine
> is given as idle on ring_tick. (This basically consists of checking
> FIFO_STAT and then GUI_STAT again). 
> 
> If the chip generates transient "idles" during operation then this
> should catch it (or at least it should be really unlikely to miss it). If 
> the chip generates transient "busys" while in idle (which somehow seems more 
> unlikely) then the error will happen again.
> 
> Felix, please try the patch attached. I'm also gonna see if I can

Ok, I will apply it. But since the errors were very rare, it will take
some time to be sure. Is there a way to make a patch that can print a
log message when a transient idle is generated in a situation when it
shoudn't and try to recover from it the way your patch does? Then if one
sees such a message and the programme didn't crash one could be sure.

> reproduce it (by the look of its webpages, TORCS seems a nice way to
> spend sometime ;-). I'll also redo the other "extra safety check" that
> was failing before on my system to see if it goes away too.

Yeah, it's a nice programme, but I get only between 8 and 13 fps at
640x480.

> 
> José Fonseca
> 

Felix

               __\|/__    ___     ___     ___
__Tschüß_______\_6 6_/___/__ \___/__ \___/___\___You can do anything,___
_____Felix_______\Ä/\ \_____\ \_____\ \______U___just not everything____
  [EMAIL PROTECTED]    >o<__/   \___/   \___/        at the same time!


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to