server, client and general GLX extensions and version numbers

[Ian Romanick]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ioannis Nousias wrote:
> Running glxinfo, there are 3 sections for GLX extensions. The "server",
> "client" and another one (general?). Each of them has its own version
> number and and each of them has different number and mixture of
> extensions. Now, what I'd like to know is what do each of those sections
> represent and which part of Xorg, Mesa or whatever else provides them.

The third list is the list of extensions that are actually usable.  With
a couple minor exceptions, this third list is the union of the other two
lists.  As you note below, and extension has to be supported by both the
client and the server in order to be actually usable (i.e., listed in
the third list).

> I have 1.2 for the server, 1.4 for the client and 1.2 for the third one

Right.  The usable GLX version is the highest version supported by
*both* the client and the server.  If the server only supports 1.2, you
only get 1.2.

> the reason I'm asking this is because I have a problem with the
> GLX_EXT_texture_from_pixmap. It appears in the "server" and "client"
> section, but not in the general one, causing compiz to fail.

Hmm...since GLX_EXT_texture_from_pixmap isn't supported for direct
rendering, it shouldn't appear in the client list either.  I suspect
that if you run 'LIBGL_ALWAYS_INDIRECT=y glxinfo',
GLX_EXT_texture_from_pixmap will appear in all three lists.  My guess is
that compiz is asking for a direct rendering context, but it should not.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFdyCvX1gOwKyEAw8RAvQWAKCez5EqyDTEiufh59dLMzq6B6OBbQCfQZn8
yimRSB7ulBvJeM/oFZEswis=
=hFWi
-----END PGP SIGNATURE-----