On Wed, Dec 04, 2002 at 03:52:39PM -0800, magenta wrote: > On Wed, Dec 04, 2002 at 02:21:30PM -0800, Ian Romanick wrote: > > > > As far as I can tell, there is no way either an app or a wrapper library > > could communicate this information to the driver. Yet, shipping "high end" > > drivers support and demanding users expect this level of > > application-to-driver tuning. > > A wrapper library doesn't have to communicate any information to the driver > - it just intercepts the function calls and turns them into something based > on the user's preference.
I completely understand how the wrapper idea works. I'm just saying that there is a large number of demonstrably interesting cases that the wrapper cannot possibly support... > Or, for a more complex idea, let's say the user wants to force wireframe > rendering and FSAA. Probably the easiest way for this to happen is for the > wrapper library to have something like: ...and this is one of them. There is NO OpenGL extension for super-sampling style FSAA (the only kind that most cards support). Given that, there is NOTHING that the wrapper library could possibly do to silently promote regular visuals to FSAA visuals. There's enough cases that the wrapper couldn't cover that we'd have to implement something in the driver anyway. For example, one of the current env vars tells the Radeon driver to not use HW TCL. How could the wrapper do that? -- 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
