<p><br>
On Feb 8, 2012 8:38 PM, "Chris Wilson" <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> wrote:<br>
><br>
> On Wed, 8 Feb 2012 19:49:54 +0000, Robert Bragg <<a href="mailto:robert@sixbynine.org">robert@sixbynine.org</a>> wrote:<br>
> > This adds the "GLX_" prefix to the string we pass to<br>
> > __glXEnableDirectExtension() otherwise it doesn't match the name we have<br>
> > in known_glx_extensions[] in glxextensions.c and doesn't get enabled.<br>
> ><br>
> > This mistake wasn't noticed before since GLX_INTEL_swap_event was being<br>
> > implicitly enabled for GLX v1.4 but that was changed in commit<br>
> > d3f7597bc9f6d5<br>
> ><br>
> > Signed-off-by: Robert Bragg <<a href="mailto:robert@sixbynine.org">robert@sixbynine.org</a>><br>
><br>
> This sounds related to<br>
> <a href="https://bugs.freedesktop.org/show_bug.cgi?id=43667">https://bugs.freedesktop.org/show_bug.cgi?id=43667</a><br>
> -Chris</p>
<p>I don't think this will fix that bug, the driver they are using is reporting the extension it's just that it has some odd startup behaviour.</p>
<p>kind regards,<br>
- Robert</p>
<p>><br>
> --<br>
> Chris Wilson, Intel Open Source Technology Centre<br>
</p>