<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [REGRESSION, bisected] Wayland revert commit breaks fullscreen frame updates" href="https://bugs.freedesktop.org/show_bug.cgi?id=98833#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [REGRESSION, bisected] Wayland revert commit breaks fullscreen frame updates" href="https://bugs.freedesktop.org/show_bug.cgi?id=98833">bug 98833</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to Eero Tamminen from <a href="show_bug.cgi?id=98833#c7">comment #7</a>) > -> Frame buffer count option has no effect at all in EGL/Wayland, VSync > option maps to eglSwapInterval() call. That makes sense. > Is there something minimal like glxgears for Wayland, which sources I could > easily modify to do screen updates similarly to the test-suite I'm using? Yup, there is <a href="https://cgit.freedesktop.org/wayland/weston/tree/clients/simple-egl.c">https://cgit.freedesktop.org/wayland/weston/tree/clients/simple-egl.c</a> It's a whole program almost in one source file. You might want to change the redraw() function to not use a clock but rather a frame counter to advance the animation, otherwise racing at high rates the difference between consecutive frames might be too small to notice. Maybe it can already reproduce the problem when you run it fullscreen, opaque, and swapinterval=0? I see there are some left-overs of frame callback handling, but it does not actually use frame callbacks manually. I was going to say you'd need to remove that logic, but it's already gone. All throttling is left for eglSwapBuffers().</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>