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. -- Leif Delgass http://www.retinalburn.net ------------------------------------------------------- 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
