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.
No, this is code by Gareth, I think, to deal with apps like 'clearspd' that
just queue up clears in a tight loop. Without throttling, the behaviour is bad.
However, I can think of a dozen different ways to get similar bad behaviour
without calling glClear either.
Keith
-------------------------------------------------------
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
