[Bug 84944] tearing on radeonsi vdpau deinterlacer

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Oct 21 01:35:21 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=84944

--- Comment #11 from warpme at o2.pl ---
(In reply to Christian König from comment #9)
> (In reply to warpme from comment #7)
> > (In reply to Christian König from comment #5)
> > > The deinterlacer is hardware independent and so it's rather unlikely that it
> > > is the source of the problem.
> > > 
> > > Can you grab a trace of MythTV with VDPAU_TRACE=1 in the environment once
> > > with and once without deinterlacing enabled? This way we can see what MythTV
> > > is actually doing.
> > 
> > Adding VDPAU_TRACE=1 causes stop working VDPAU (MythTV switches to ffmpeg).
> > I can try to investigate this - if You believe it is worth.... 
> 
> Yes, we should definitely investigate what MythTV is doing here.
> 
> > For me results from tests Michel suggested shows issue is within GLAMOR as
> > Brazos without GLAMOR works OK while Brazos with GLAMOR NOK. As Kabini by
> > default requires GLAMOR - by default I have issue on Kabini. 
> 
> EXA on Brazos is tear free most of the time because we sync operations to
> the vblank using a hack. That hack isn't supported on GLAMOR and so GLAMOR
> operations are not synced to vblank at all (Michel knows more about this).
> 
> But the root cause is something completely different, cause GLAMOR shouldn't
> be used in the first place in this situation.

Well - radeonsi can't work here without glamor. Forcing EXA gives following in
xorg log:

(WW) RADEON(0): EXA not supported, using glamor

> 
> GLAMOR is made to accelerate things like window movements and text drawing.
> For fullscreen video playback there should be a page flip operation used.
> 
> Please try to investigate what MythTV is actually doing different here to
> cause the page flipping to not work correctly.

mythtv does exactly the same on Kabini like on Brazos. I'm using exactly the
same PXE booted image. Also all configs are the same as I'm simply booting the
same OS image + configs just on 2 different HW platforms. I believe all HW
depended things are purely and only internal to xserver and mesa.

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.... 

br

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20141021/2a58dc0d/attachment-0001.html>


More information about the dri-devel mailing list