https://bugs.kde.org/show_bug.cgi?id=369317
Martin Gräßlin <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Martin Gräßlin <mgraess...@kde.org> ---
> That is not true, glFenceSync is provided by the driver and a simple test
> program based on the gles2 test of epoxy is able to call it without issue on
> the same system.
Your test program is not creating a pure OpenGL ES context - sorry to say so.
You create an OpenGL context through GLX and then the compatibility extension.
But KWin is doing proper GLES using EGL and creating an OpenGL ES context
directly. It's not using GLX! It is possible that the driver reports different
things depending on how the context is created. Especially as the way you
created it loads libgl.so instead of libgles.so.
I'm sorry, but the code you attached doesn't show that there is something wrong
in KWin. Heck our code works on hardware which doesn't have OpenGL at all -
e.g. the Nexus 5 or Odroid. Of course it uses proper OpenGL ES and epoxy knows
it's using OpenGL ES.
--
You are receiving this mail because:
You are watching all bug changes.
