I sent this message once, but I accidentally just sent it to Brian, so here
goes...
On Thu, Oct 17, 2002 at 01:16:13PM -0600, Brian Paul wrote:
> In the DRI drivers we keep a bitfield to determine if/why we need a software
> fallback. I suppose IsFast() could return a similar bitfield but coming up
> with a set of meaningful bits at the right granularity would be a challenge
> too.
Interesting. We could define a minimal set of useful things to track and
leave the rest to layered extensions. In that vein, I think that using a
bit mask is a bad idea. That limits us to 32 events and would make adding
layered extensions difficult.
An API like the following could work:
void ResetFallbackFlagsMESA( void );
void GetFallbackFlagsivMESA( const enum * pnames, boolean * params );
Another option would be to have counters instead of simple flags. There
could be problems with interpreting the meanings of different counters
(i.e., a small number fallbacks for texture3D is a lot worse than a large
number of TCL fallbacks). Still, it's extra information that apps might
find useful.
This seems like a really good topic for discussion in Monday's IRC meeting.
:) Allen, is there any chance you could join us Monday?
--
Smile! http://antwrp.gsfc.nasa.gov/apod/ap990315.html
-------------------------------------------------------
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
