-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roland Scheidegger wrote:
> Indeed this show up every once in a while. A driconf option might be a > good idea, but it doesn't solve the problem really for the hardware > which indeed does support GL_CLAMP, unless you'd also introduce an > option to make it non-conformant GL_CLAMP_TO_EDGE there too (which was > suggested in the past). So the only real solution is to tell the app > writers to fix their code. If you'd want to fix this in the driver > without requiring user intervention, you'd need app detection (ugh). We can do that with driconf, right? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGwJtnX1gOwKyEAw8RAsdJAJ0aimAwaWdjPsVK3RfJJ5DACKmC4wCfX6Vf 4cGqeamMtvFA3ffAbmHirFo= =ssMK -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
