Michel Dänzer wrote: > Indeed. The X server's GetTimeInMillis() might be more convenient > than gettimeofday() (and would also work with an elfloader X server > ;). Ah yes. That was just a quick hack :-). The question is, what should the timeout value be?
>> For determining if the chip has locked up I just used the >> ZPASS_DATA reg (assuming that as long as the chip outputs fragments >> it has not locked up - of course you could hack up some gl test >> program where all fragments fail the z test, > > Will this still increase if the depth buffer/test is disabled? Yes. It may not be a good choice however, the reg might even be different on r300. >> but I'm not sure there's a better reg to monitor activity - ring >> ptr might be another possibility, but I think this can point at the >> same location for a long time too (for instance when drawing using >> the idx buf command). > > One of the performance counters might be better. Which one did you have in mind? Don't they need to be configured first? Sounds like a good idea though, or maybe that ring ptr would do too, I think chances aren't that great that it is really stuck at the same place for a long time. Roland -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel