I'm afraid that relying on glxinfo will only make the lists incomplete. I'm sure I won't run glxinfo for every Mesa release and every GPU I have. I guess somebody else will have to maintain extension lists for radeon if we want to have radeon there.
What I like about GL3.txt that your solution lacks: * small incremental updates * can easily say that an extension is supported by all drivers * no need to run glxinfo * core extensions divided into groups based on the GL version * real driver names like "radeonsi" instead of weird names like "Gallium 0.4 on AMD SUMO" Marek On Wed, Mar 26, 2014 at 3:24 PM, Ilia Mirkin <imir...@alum.mit.edu> wrote: > Hello, > > As the outcome of a discussion yesterday on #dri-devel > (http://people.freedesktop.org/~cbrill/dri-log/index.php?channel=dri-devel&date=2014-03-25 > starting around 16:30), I've created a small page that lists all > extensions/limits supported by core/compat profiles, per driver: > > http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html > > The more astute members of the crowd might notice a distinct > similarity to the apple version[1], but I never claimed to be a > designer :) The nice thing about this implementation is that you just > run a program (listed at the top of that page) to parse glxinfo -l -s > output, and stick it as a js source on the page (and the generated > file calls a 'register' function to register its configs). > > There are a few shortcomings -- I'm not completely happy with the > headers (might have to switch to the apple way), there's no history > support, and it's very lacking in driver and version info (I just ran > it on the hw/sw I had easily available). However I'm confident I can > resolve all these, and I don't think they really impact the prototype > evaluation. > > Do people think this sort of resource is useful? Counter-productive? > Are you happy with the raw information presented (even if you may be > unhappy about the specific way in which it is presented)? Any other > feedback? > > If it's useful, I'll reach out to the various driver teams to get them > to provide relevant glxinfo's and fill it out some more. Perhaps even > look into a version that can receive glxinfo uploads. But I don't > really want to put in more effort if people don't find it useful/it > won't get used. > > Let me know what you think (and feel free to send me the output of > parse-glxinfo.py for your setup). > > Cheers, > > -ilia > > [1] https://developer.apple.com/graphicsimaging/opengl/capabilities/ _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
