From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84944] tearing on radeonsi vdpau deinterlacer
Date: Tue, 21 Oct 2014 10:06:00 +0000 [thread overview]
Message-ID: <bug-84944-502-jcMDdcSbXy@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84944-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 940 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84944
--- Comment #14 from warpme@o2.pl ---
(In reply to Christian König from comment #13)
>
> 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.
Indeed - infrastructure for flipping seems to be ready:
[837858.379] (II) RADEON(0): KMS Pageflipping: enabled
[837858.379] (II) RADEON(0): SwapBuffers wait for vsync: enabled
[837858.389] (II) RADEON(0): Output HDMI-0 using monitor section Monitor1
>
> The question is why the heck do we fallback to a copy operation with glamor
> when deinterlacing is enabled?
If You believe we should do some tests with added debug outputs - I'm more than
happy to do so :-)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1787 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-10-21 10:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 17:35 [Bug 84944] New: tearing on radeonsi vdpau deinterlacer bugzilla-daemon
2014-10-12 17:35 ` [Bug 84944] " bugzilla-daemon
2014-10-15 6:58 ` bugzilla-daemon
2014-10-19 19:41 ` bugzilla-daemon
2014-10-20 7:38 ` bugzilla-daemon
2014-10-20 8:09 ` bugzilla-daemon
2014-10-20 16:54 ` bugzilla-daemon
2014-10-20 17:23 ` bugzilla-daemon
2014-10-20 19:19 ` bugzilla-daemon
2014-10-20 20:53 ` bugzilla-daemon
2014-10-21 2:07 ` bugzilla-daemon
2014-10-21 8:35 ` bugzilla-daemon
2014-10-21 8:44 ` bugzilla-daemon
2014-10-21 8:48 ` bugzilla-daemon
2014-10-21 10:06 ` bugzilla-daemon [this message]
2014-10-22 9:43 ` bugzilla-daemon
2014-10-22 16:41 ` bugzilla-daemon
2014-10-23 1:39 ` bugzilla-daemon
2014-10-23 8:10 ` bugzilla-daemon
2014-10-23 8:35 ` bugzilla-daemon
2014-10-23 14:48 ` bugzilla-daemon
2014-10-24 1:54 ` bugzilla-daemon
2014-10-24 15:28 ` bugzilla-daemon
2014-10-26 12:16 ` bugzilla-daemon
2014-10-26 16:16 ` bugzilla-daemon
2014-10-26 20:44 ` bugzilla-daemon
2014-10-28 10:12 ` bugzilla-daemon
2014-11-11 9:53 ` bugzilla-daemon
2014-11-13 7:26 ` bugzilla-daemon
2014-11-13 13:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-84944-502-jcMDdcSbXy@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox