Ian Romanick <[email protected]> writes: > On 08/08/2013 03:59 AM, Eric Anholt wrote: >> Previously, we were asserting that each driver specified an NConfigOptions >> exactly equal to the number of options they supplied, leading to frequent >> bugs when people would forget to adjust the value when adjusting driver >> options. Instead, just overallocate the table by a bit and leave sanity >> checking to the assert in findOption(). > > This makes sense. I thought part of the reason for __driNConfigOptions > being exact was that it was used by external driconf GUI tools. Will > this change break those tools?
I spent an embarassingly long time trying to find how the external tool
used the config symbols, only to find out that it doesn't. driconf
calls out to xdriinfo, which does a
glXGetProcAddress("glXGetDriverConfig"), and parses the XML returned
From calling the returned function. It's like a sane interface! (except
for not checking for an extension string trying all this)
pgpLliH2uKKgC.pgp
Description: PGP signature
_______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
