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

[Steven Newbury]

On Sat, 2014-07-05 at 10:53 +0300, Pekka Paalanen wrote:
> On Fri, 04 Jul 2014 08:45:00 +0100
> Steven Newbury <steve at snewbury.org.uk> wrote:
>  
> >  On Fri, 2014-07-04 at 03:40 -0400, Ilia Mirkin wrote:
> > >  On Fri, Jul 4, 2014 at 3:37 AM, Steven Newbury
> > >   wrote:
> > > >   On Thu, 2014-07-03 at 10:47 +0200, Andreas Boll wrote:
> > > > >   2014-07-03 7:39 GMT+02:00 Steven Newbury
> > > > >  :
> > > > > >    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.
> >  Of course it's an option to extend eglinfo with switches to select
> >  API, but there is already es*_info, which is what made me thing it
> >  might be the better approach.  I'm perfectly happy to hack on 
> > eglinfo
> >  instead! :-)
>  
> For me personally, the problem with eglinfo has been that it does
> not create any GL context, so cannot report any GL info either. In
> the past, the problem was that you needed window system specific
> code to create the EGLDisplay and maybe the window too.
>  
Agreed.  All the existing *info programs are either window system 
specific or assume X11, except eglinfo which gets away with it by not 
creating a context.  Through Mesa though it is necessary to have the 
default EGL platform/driver working or have EGL_PLATFORM/DRIVER set 
appropriately.

This does at least allow selection between Mesa implementations.

> EGL_DEFAULT_DISPLAY just won't work everywhere, and in Mesa it
> might pick a wrong window system, and the window system will
> affect at least EGL capabilities.
>  
> Do we now have an acceptable plan of writing a multi-window-system
> capable *info program, or are we still stuck with *info programs
> written for specific window systems?
>  
Multi-platform systems such as Wayland+XWayland will have potentially 
multiple working EGL implementations, both platform and drivers, even 
just within the Mesa framework, each with potentionally different 
capabilities.  This means the user must run the right *info program or 
at least specify which to use, otherwise a "work anywhere" *info 
should detect what is available from what is possible (given linked 
libraries).

> I'd really like one that works e.g. on Wayland, and preferably does
> not do anything very Mesa specific. Would also be very cool to
> use the new extensions allowing to be explicit on which window
> system you are intending to use, rather than rely on the EGL
> implementation guessing based on your EGLNativeDisplay value.
>  
> The other complication with writing a multi-API *info program is,
> that you need to link to a different library depending on the API
> you choose: libGLESv1_CM vs. libGLESv2 vs. libGL...
>  
> Libepoxy to the rescue?
> https://github.com/anholt/libepoxy
>  
>  
I need to look at this.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20140706/b44535fc/attachment.sig>