<HTML><HEAD> <META http-equiv=Content-Type content='text/html; charset=windows-1252'> <title>Samsung Enterprise Portal mySingle</title> <style> P, td, li {font-family:Arial, arial; font-size:9pt; margin-top:5px;margin-bottom:5px;} body{font-family:Arial, arial; font-size:9pt;}</style> </HEAD><BODY>Tried with the code from git. I see the GLX extension listed in xdpyinfo output. But again Xephyr returns no configs in response to X_GLXGetVisualConfigs. Has anyone used GLX with Xephyr? It will be very hepful to know how... Configuration options to xserver: --with-mesa-source=path_to_mesa_git_code --enable-kdrive --enable-xephyr Btw, can someone update the wiki for Xephyr, Xserver. They still refer to CVS, and thats how i started with CVS. http://www.freedesktop.org/wiki/Software/Xserver ------- Original Message ------- Sender : KAMALNEET SINGH<kamalneet.s@samsung.com> Engineer/SISO(DCD)/Samsung Electronics Date : Jun 29, 2007 19:32 Title : glx with Xephyr Hi :-) I want to know whether glx is functional with Xephyr. xdpyinfo lists GLX as an extension, but on running a GLX application, Xephyr returns no configs in response to X_GLXGetVisualConfigs. I tried with Ubuntu 7.04's Xephyr and also compiled from CVS xserver module. I compiled with --enable-glx --with-mesa-source=path_to_mesa_6.5.2 xserver didn't compile with mesa 7.0 and 6.5.3. With 6.5.2 also, i had to make some changes in xserver (cvs code) to make it compile. The changes are: adding some mesa files to GL/mesa/Makefile.am, removing extension suffix from some function names. And to solve the unresolved mgl symbols, had to comment out some entries in the glapi table in xserver's glx. Can that be a cause of the problem? If glx is not functional with Xephyr as of now, I am ready to put in some time to make it work, but I would need guidance :-) I'm not so clear about it, but I was looking for server-based GL instead of software mesa so that we could share context across applications, does it make sense? We don't need hardware acceleration, so any simple way out? Thanks :-) </BODY></HTML>