[Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits

[Ilia Mirkin]

On Fri, Jul 4, 2014 at 3:37 AM, Steven Newbury <steve at snewbury.org.uk> wrote:
> On Thu, 2014-07-03 at 10:47 +0200, Andreas Boll wrote:
>> 2014-07-03 7:39 GMT+02:00 Steven Newbury <steve at snewbury.org.uk>:
>> >  On Wed, 2014-07-02 at 21:04 +0200, Andreas Boll wrote:
>> > >
>> > >  I'd like to make a new demos release on Friday, July 4th.
>> > >  The last release was on February 24th, 2013. Additionally this
>> > >  release is needed to fix the build with mesa 10.2. (fdo#78101)
>> > > >
>> > >  Any objections?
>> > > >
>> > >  Also I'd like to get these 3 patches included in the new
>> > > release.
>> > > >
>> > >  Andreas.
>> > > >
>> > > >
>> > >  Fredrik Höglund (3):
>> > >    glxinfo: Print XFB, TBO, and UBO limits
>> > >    glxinfo: Print GL_ARB_vertex_attrib_binding limits
>> > >    glxinfo: Print GL_EXT_texture_array limits
>> > > >
>> > >   src/xdemos/glinfo_common.c | 30 ++++++++++++++++++++++++++++++
>> > >   1 file changed, 30 insertions(+)
>> > > >
>> > >
>> >  What about extending eglinfo to have switches to enable printing
>> > glxinfo
>> >  style output for each supported API?
>> > >
>>
>> Sounds good, feel free to send a patch.
>> Although I'm not planning to hold off this release.
>> I can make further releases when required.
>>
>>
> I've been giving this some more thought, it occurs to me that since
> there's already es1_info/es2_info progs, what's really needed is an
> EGL version of glxinfo/wglinfo (egl_glinfo?) which should be able to
> share the glinfo_common code.
>
> While digging though the existing code I noticed the above mentioned
> es*_info program only works with X11 EGL, that should probably be
> improved too...
>
> Shall I see if I can code something up to get glinfo output through
> EGL?  Would this be he best approach?

I'm sure I'm missing something, but what's wrong with eglinfo?

http://cgit.freedesktop.org/mesa/demos/tree/src/egl/opengl/eglinfo.c

It doesn't share the glinfo_common code, but that should be easily
arranged, I would think.

  -ilia