On 12 Dec 2001, Sergey V. Udaltsov wrote: > > I think the point is (but I could be wrong) whether this is > > user-configurable without recoding/recompiling anything, and it seems the > > answer is no. > That's bad. Definitely this is not high-priority issue, but it would be > nice to have ability to enable/disable extensions without recompiling > apps/drivers/etc. Well written apps should be able to determine which > extensions are available (shouldn't them?) so it could be interesting to > play with apps using different subsets of extensions.
I should point out that with the mach64 driver, there are some things still left to be implemented in the Mesa code, as it's still in development. I've also had problems with multitexturing and texture blending modes in other apps with this driver. So although the extension is currently exported by the driver, it probably still needs some work to get it working right: AGP texture uploads are not yet supported, for example. Many apps have a way to disable certain GL extensions, so that can be used as a workaround when available. At this stage though, it's probably best to try and find problems and fix the driver where possible. If an extension is exported, but doesn't work to spec, it's a bug. The ability to have the driver hide supported gl extensions could be useful too, but the app could always just refuse to work without them. :) --Leif --- Leif Delgass http://www.retinalburn.net _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
