-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Paul wrote: > Ian Romanick wrote: >> From: Ian Romanick <[email protected]> >> >> Several changes are made to program parameter limits. Several of the >> non-NATIVE limits are set higher. All of the NATIVE limits are set to >> zero in the core Mesa code. Each driver must set the actual value in >> its context creation routine. If the NATIVE value remains zero, this >> indicates that hardware shaders may not be supported. >> >> Each of the preceeding changes matches the bahavior of Apple's shader >> assembler, so it seems safe. >> >> Finally, we limit the value of MaxEnvParams to be no greater than >> MaxNativeAttribs. At least one case has been found where an >> application does the wrong thing if MaxNativeAttribs < MaxEnvParams. >> >> See also bugzilla #23490. > > Looks good, Ian. Just curious: what app(s) actually query these limits?
I don't know for sure. Unlike figuring out which extensions are used by an application, there isn't way to externally (i.e., using strings and grep) check this. Any app that uses more that the defined minimum maximums damn well should! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqV3wIACgkQX1gOwKyEAw+ETQCgkunzOUxkG7BloscCczwVg2Be vBkAnAj58csLvAq6nodzWHpca+AQVBvS =oGAI -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
