summaryrefslogtreecommitdiff
path: root/src/glx
diff options
context:
space:
mode:
authorIan Romanick <idr@us.ibm.com>2005-08-05 19:13:51 +0000
committerIan Romanick <idr@us.ibm.com>2005-08-05 19:13:51 +0000
commit6bc24c5c0560844e481b76600991665cc076eb2c (patch)
tree54724f11e892e576be4b826d3bac5394b7d0a437 /src/glx
parent126c89e35fb5179fe077f7593f31ea874c89dd65 (diff)
In order to create the set of available extensions, we have to know if
direct-rendering is possible on a given screen. It is not possible to determine this by just looking at driDisplay.private in the display structure. However, it is possible to determine this by looking at driScreen.private in the screen structure. This field is only non-NULL if a DRI driver has been successfully loaded and bootstrapped. Once we get to that point, we know that direct-rendering is at least theoretically possible. This fixes bugzilla #2875.
Diffstat (limited to 'src/glx')
-rw-r--r--src/glx/x11/glxcmds.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/glx/x11/glxcmds.c b/src/glx/x11/glxcmds.c
index fbb6e7b368..093deab3b9 100644
--- a/src/glx/x11/glxcmds.c
+++ b/src/glx/x11/glxcmds.c
@@ -1269,7 +1269,7 @@ PUBLIC const char *glXQueryExtensionsString( Display *dpy, int screen )
__glXCalculateUsableExtensions(psc,
#ifdef GLX_DIRECT_RENDERING
- (priv->driDisplay.private != NULL),
+ (psc->driScreen.private != NULL),
#else
GL_FALSE,
#endif