<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - tearing on radeonsi vdpau deinterlacer" href="https://bugs.freedesktop.org/show_bug.cgi?id=84944#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - tearing on radeonsi vdpau deinterlacer" href="https://bugs.freedesktop.org/show_bug.cgi?id=84944">bug 84944</a> from <a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> Christian König</a> <pre>(In reply to warpme from <a href="show_bug.cgi?id=84944#c11">comment #11</a>) > Maybe Kabini's xserver log output about "EXA not supported" is clue here? Is > EXA supported on Kabini at all? > > heh - I spent great time to adding glamor to carefully minimized minimyth2 > image - just because on many places it is stated that mesa's radeonsi > mandatory requires glamor.... Sorry you misunderstood me: Glamor is mandatory on SI, there is not support for EXA. This is correct. But glamor shouldn't be used in this situation because we have only one fullscreen application on the screen. In this situation page flipping should be used by the X server without any copy operation required by glamor. Page flipping operations are tear free, so what we see here is that without deinterlacing the graphics stack uses page flipping and with deinterlacing it uses glamor with of course results in badly tearing of the video. The question is why the heck do we fallback to a copy operation with glamor when deinterlacing is enabled? Deinterlacing is independent of displaying the video so this makes no sense.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>