On Mon, 2002-09-30 at 02:07, Brian Paul wrote:
> Felix Kühling wrote:
> > Hello,
> >
> > Modifying the frame throttling code in r200_ioctl.c I removed
> > R200_MAX_OUTSTANDING which is no longer needed there. It is, however,
> > still used in r200Clear:
> >
> > if ( rmesa->sarea->last_clear - clear <= R200_MAX_OUTSTANDING+1 ) {
> > break;
> > }
> >
> > The corresponding radeonClear uses a macro RADEON_MAX_CLEARS. There is a
> > macro R200_MAX_CLEARS defined in r200_ioctl.c, too. But it is never used.
> > Did I step on a bug here? Should I change this to
> >
> > if ( rmesa->sarea->last_clear - clear <= R200_MAX_CLEARS ) {
> > break;
> > }
> >
> > Regards,
> > Felix
> >
>
> What's the story with throttling in glClear? I hope we're not using
> glClear as a frame counter of some sort. Applications don't necessarily
> have to call glClear at all. Other apps may call glClear several times per
> frame.
RADEON_MAX_CLEARS is 256, so that shouldn't be a problem? OTOH if the
r200 driver uses R200_MAX_OUTSTANDING (which is 2) instead, that could
be limiting...
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
-------------------------------------------------------
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
