Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Sat, 2014-07-05 at 10:53 +0300, Pekka Paalanen wrote: On Fri, 04 Jul 2014 08:45:00 +0100 Steven Newbury st...@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. signature.asc Description: This is a digitally signed message part ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Sat, 2014-07-05 at 10:53 +0300, Pekka Paalanen wrote: On Fri, 04 Jul 2014 08:45:00 +0100 Steven Newbury st...@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. signature.asc Description: This is a digitally signed message part ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Saturday, July 05, 2014 01:04:02 PM Emil Velikov wrote: On 5 July 2014 08:53, Pekka Paalanen ppaala...@gmail.com wrote: On Fri, 04 Jul 2014 08:45:00 +0100 Steven Newbury st...@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. 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? 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 IMHO waffle [1] would be a better bet here. Build it once and control the platfrom/api via a command line arg and/or env var. There is a minor catch though - waffle needs to stop explicit linking against libGL libEGL libGLES... and dlopen only the required the library. -Emil [1] https://github.com/waffle-gl/waffle In fact Waffle already includes a wflinfo program, which supports GLX/EGL+X11/Wayland/GBM/Android and GL/ES1/ES2/ES3 today. Improving wflinfo seems like the way to go. There are a couple of obvious improvements that could be made: 1. It doesn't print out all the same information that glxinfo does (missing limits, visuals), and it could do a better job of pretty-printing. 2. The UI is obnoxious: running plain wflinfo generates the terse message: Wflinfo usage error: --platform is required (see wflinfo --help) Ideally, I'd like it to provide some sort of useful information. One option would be to print a summary of what's currently supported on your system: Vendor: Intel Open Source Technology Center Renderer: Mesa DRI Intel(R) Haswell Mobile Supported Window Systems: - EGL 1.5: Wayland(-p wayland) - EGL 1.5: X11
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On 7 July 2014 00:22, Kenneth Graunke kenn...@whitecape.org wrote: On Saturday, July 05, 2014 01:04:02 PM Emil Velikov wrote: On 5 July 2014 08:53, Pekka Paalanen ppaala...@gmail.com wrote: On Fri, 04 Jul 2014 08:45:00 +0100 Steven Newbury st...@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. 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? 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 IMHO waffle [1] would be a better bet here. Build it once and control the platfrom/api via a command line arg and/or env var. There is a minor catch though - waffle needs to stop explicit linking against libGL libEGL libGLES... and dlopen only the required the library. -Emil [1] https://github.com/waffle-gl/waffle In fact Waffle already includes a wflinfo program, which supports GLX/EGL+X11/Wayland/GBM/Android and GL/ES1/ES2/ES3 today. Improving wflinfo seems like the way to go. There are a couple of obvious improvements that could be made: 1. It doesn't print out all the same information that glxinfo does (missing limits, visuals), and it could do a better job of pretty-printing. 2. The UI is obnoxious: running plain wflinfo generates the terse message: Wflinfo usage error: --platform is required (see wflinfo --help) Ideally, I'd like it to provide some sort of useful information. One option would be to print a summary of what's currently supported on your system: Vendor: Intel Open Source Technology Center Renderer: Mesa DRI Intel(R) Haswell Mobile Supported Window Systems:
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Fri, 04 Jul 2014 08:45:00 +0100 Steven Newbury st...@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. 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? 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 Thanks, pq ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On 5 July 2014 08:53, Pekka Paalanen ppaala...@gmail.com wrote: On Fri, 04 Jul 2014 08:45:00 +0100 Steven Newbury st...@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. 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? 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 IMHO waffle [1] would be a better bet here. Build it once and control the platfrom/api via a command line arg and/or env var. There is a minor catch though - waffle needs to stop explicit linking against libGL libEGL libGLES... and dlopen only the required the library. -Emil [1] https://github.com/waffle-gl/waffle Thanks, pq ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Thu, 2014-07-03 at 10:47 +0200, Andreas Boll wrote: 2014-07-03 7:39 GMT+02:00 Steven Newbury st...@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? signature.asc Description: This is a digitally signed message part ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Fri, Jul 4, 2014 at 3:37 AM, Steven Newbury st...@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 st...@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 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
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! :-) signature.asc Description: This is a digitally signed message part ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
2014-07-02 21:59 GMT+02:00 Brian Paul bri...@vmware.com: On 07/02/2014 01:04 PM, 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? Sounds great. Also I'd like to get these 3 patches included in the new release. Reviewed-by: Brian Paul bri...@vmware.com Do you need me to push these patches? -Brian Thanks! I have pushed these patches myself. Andreas. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
2014-07-03 3:09 GMT+02:00 Ilia Mirkin imir...@alum.mit.edu: On Wed, Jul 2, 2014 at 3:04 PM, Andreas Boll andreas.boll@gmail.com 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? Not an objection, but since there's like one of these every 2 years, perhaps someone would be willing to go through the various GL4 extensions and add prints for the interesting limits? Or do people feel that the current code + the below patches capture all the interesting stuff? -ilia Sure, I just wanted to get the patches from the ML merged and make a new release. If people want me to wait with the release, please speak. Otherwise I can make further releases when required. We don't have to wait another 2 years for the next release ;-) Andreas. P.S.: If someone could point me the interesting limits which are missing, I could write a patch. 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(+) -- 2.0.0 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
2014-07-03 7:39 GMT+02:00 Steven Newbury st...@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. Andreas. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
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(+) -- 2.0.0 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On 07/02/2014 01:04 PM, 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? Sounds great. Also I'd like to get these 3 patches included in the new release. Reviewed-by: Brian Paul bri...@vmware.com Do you need me to push these patches? -Brian ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Wed, Jul 2, 2014 at 3:04 PM, Andreas Boll andreas.boll@gmail.com 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? Not an objection, but since there's like one of these every 2 years, perhaps someone would be willing to go through the various GL4 extensions and add prints for the interesting limits? Or do people feel that the current code + the below patches capture all the interesting stuff? -ilia 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(+) -- 2.0.0 ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] [PATCH demos 0/3] demos release plan and glxinfo: Print more limits
On Wed, 2014-07-02 at 21:04 +0200, Andreas Boll wrote: I'dliketomakeanewdemosreleaseonFriday,July4th. ThelastreleasewasonFebruary24th,2013.Additionallythis releaseisneededtofixthebuildwithmesa10.2.(fdo#78101) Anyobjections? AlsoI'dliketogetthese3patchesincludedinthenewrelease. Andreas. FredrikHöglund(3): glxinfo:PrintXFB,TBO,andUBOlimits glxinfo:PrintGL_ARB_vertex_attrib_bindinglimits glxinfo:PrintGL_EXT_texture_arraylimits src/xdemos/glinfo_common.c|30++ 1filechanged,30insertions(+) What about extendingeglinfoto haveswitches toenable printing glxinfo style output for each supportedAPI?* signature.asc Description: This is a digitally signed message part ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
