http://bugs.freedesktop.org/show_bug.cgi?id=14939
Ian Romanick <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |NOTABUG
--- Comment #1 from Ian Romanick <[EMAIL PROTECTED]> 2008-03-17 11:22:57 PST
---
Confusing though this behavior may be, it is technically correct. You have to
understand what each piece of information really means.
The server extension string means "the server supports all the required bits to
make this extension work."
The client extension string means "the client library supports the *protocol*
to make this extension work." The value of this string depends only on what
the client-side library can do.
In the case of direct rendering there is a third component, the direct
rendering driver, that is not accounted for in either of these two strings.
Once a GL context is created and made current, the client-side library can know
what its capabilities are. If there are extensions listed in the client
library extension string that the direct rendering driver does not support,
they will be subtracted before calculating the final GLX extensions.
In this particular case, it means that the server supports GLX_EXT_tfp, the
client library supports the protocol for GLX_EXT_tfp, but the direct rendering
driver does not support GLX_EXT_tfp.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
