I think starting from docs/spec/MESA_query_renderer.txt and replacing GLX with EGL would be a good starting point. You can probably delete the existing "Issues" section, and add a line "See also issues in GLX_MESA_query_renderer extension." Then we can add issues specific to the EGL version of the extension to the new document. The EGL enums will probably be different, so maybe replace the enum values with 0xXXXX for now.
The GLX implementation uses DRI infrastructure for most of the real work. It should be pretty easy to copy most of src/glx/dri_common_query_renderer.c over to EGL. On 08/27/2018 10:35 PM, Veluri Mithun wrote: > --- > docs/specs/EGL_MESA_query_renderer.txt | 58 ++++++++++++++++++++++++++ > 1 file changed, 58 insertions(+) > create mode 100644 docs/specs/EGL_MESA_query_renderer.txt > > diff --git a/docs/specs/EGL_MESA_query_renderer.txt > b/docs/specs/EGL_MESA_query_renderer.txt > new file mode 100644 > index 0000000000..0fa9b33d00 > --- /dev/null > +++ b/docs/specs/EGL_MESA_query_renderer.txt > @@ -0,0 +1,58 @@ > +Name > + > + MESA_query_renderer > + > +Name Strings > + > + EGL_MESA_query_renderer > + > +Contact > + > + Rob Clark <robdclark 'at' gmail.com> > + Nicolai Hähnle <Nicolai.Haehnle 'at' amd.com> > + > +Contibutors > + > + Veluri Mithun <velurimithun38 'at' gmail.com> > + > +Status > + > + XXX - Not complete yet!!! (draft) > + > +Version > + > + Version 1, 2018-08-24 > + > +Number > + > + EGL Extension ### > + > +Dependencies > + > + > + > +New Procedures and Functions > + > + Bool EGLQueryRendererIntegerMESA(EGLDisplay *dpy, int screen, > + int renderer, int attribute, > + unsigned int *value); > + > +Overview > + > + This extension provides the applications to qurey the details > + of the all renderers available for a particular display and > + screen. > + > +IP Status > + > + > + > +New Tokens > + > + > + > +Revision History > + > + > + > + > _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
