Re: [Mesa-dev] Add OpenSWR to GL3.txt?

In lieu of GL3.txt being updated, is there some way for me to get an idea about what OpenSWR supports without digging through the code / building tests? FWIW, as an outsider I use mesamatrix to get a very nice overview on what the different renderers support. I consider that valuable. On Wed,

Re: [Mesa-dev] Add OpenSWR to GL3.txt?

https://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html When swr makes it into a release, I'll be sure to add it in. This shows what extensions each hardware group has. Note that this isn't necessarily 1:1 with driver - a single driver might support several iterations of hardware, and

Re: [Mesa-dev] Add OpenSWR to GL3.txt?

Typically, if you expose the cap bits so that support for some extension is announced you'd consider it done. That does not necessarily mean that all the corresponding piglit tests are passing, but of course you should generally not announce support for features which don't really work (but you

Re: [Mesa-dev] Add OpenSWR to GL3.txt?

It is whatever you (i.e. driver maintainer) want it to be. GL3.txt is mainly for coordinating development and letting people know who's working on what (less so of late though). If you plan on exposing GL 4.0+, it can be a nice TODO list. Otherwise there's not an immense amount of value. -ilia

Re: [Mesa-dev] Add OpenSWR to GL3.txt?

What is the criteria for marking an extension “done”? Passing some percentage (all?) of relevant piglit tests? -Tim > On May 10, 2016, at 10:31 PM, Andrew J wrote: > > Is there any possibility that OpenSWR can be added to GL3.txt [1] so > others can get an idea of what

[Mesa-dev] Add OpenSWR to GL3.txt?

Is there any possibility that OpenSWR can be added to GL3.txt [1] so others can get an idea of what things OpenSWR supports? GL3.txt is what mesamatrix [2] uses, so adding OpenSWR to GL3.txt would add it there as well. [1] https://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt [2]