> > While working on egl_g3d, i slowly define an interface that abstracts the > native display. The interface suits the need of EGL. And I believe it > suits > the need of GLX in its current form. Eventually, it might evolve into > `struct pipe_display` that can be shared. But that is not my current > focus. >
Yes, it suits the needs of GLX, except for adding a function to support MESA_copy_sub_buffer. Some additions somewhere are also likely to be needed to support the various SGI vsync extensions that I'm currently not attempting to support. > Back to the GLX API. Reading the code in state_trackers/glx/xlib/, it > seems > you can implement GLX by providing a `struct xm_driver`. A direction I > would > suggest is to implement xm_driver using x11 native_display. Or the other > way > around, have state_trackers/glx/xlib/ use native_display, and implement a > native_display through xm_driver. Once that is done, you might consider > improve the x11 native display and eventually deprecate winsys/xlib/. > The code that I sent you and will make public once it fully implements GLX, implements GLX over the native_display interface without any use of the XMesa code (except the GLX dispatcher, which is cloned and modified to build a libGL.so that loads GLX drivers). I'd suggest to just deprecate the xm_driver code, and replace its use with GLX over native_display. As you say, the native code has no native dependency on EGL except for _eglLog, which is replaced in the patch I sent you with log.c and log.h. My code is current part of egl_g3d but it could possibly be put outside (possibly by putting the native_display code somewhere like src/gallium/display and having two separate egl_g3d and glx_g3d modules).
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
