<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:andreas.boll.dev@gmail.com" title="Andreas Boll <andreas.boll.dev@gmail.com>"> <span class="fn">Andreas Boll</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [radeonsi] vdpau playback issues, skipping & looping"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73191">bug 73191</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [radeonsi] vdpau playback issues, skipping & looping"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73191#c42">Comment # 42</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [radeonsi] vdpau playback issues, skipping & looping"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73191">bug 73191</a>
from <span class="vcard"><a class="email" href="mailto:andreas.boll.dev@gmail.com" title="Andreas Boll <andreas.boll.dev@gmail.com>"> <span class="fn">Andreas Boll</span></a>
</span></b>
<pre>Fixed with the following commits:
commit 3f98053fc94a964930c73c43154daddfd7824e7c
Author: Marek Olšák <<a href="mailto:marek.olsak@amd.com">marek.olsak@amd.com</a>>
Date: Mon Jan 13 14:13:01 2014 +0100
vdpau: flush the context before exporting the surface v2
Bugzilla (bug needs XBMC changes as well):
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [radeonsi] vdpau playback issues, skipping & looping"
href="show_bug.cgi?id=73191">https://bugs.freedesktop.org/show_bug.cgi?id=73191</a>
When VL uploads vertex buffers, it uses PIPE_TRANSFER_DONTBLOCK, which
always
flushes the context in the winsys if the buffer being mapped is busy. Since
I added handling of DISCARD_RANGE, DONTBLOCK has had no effect when
combined
with DISCARD_RANGE and I think the context isn't flushed anywhere else,
so no commands are submitted to the GPU until the IB is full, which takes
a lot of frames.
Using DISCARD_RANGE is not the only way to trigger this bug. The other way
is to reallocate the vertex buffer before every upload.
BTW, I'm not sure if this is the right place for flushing, but it does fix
the bug.
v2 (chk): move the flush to the right place.
Signed-off-by: Christian König <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>>
Tested-by: StrangeNoises (<a href="mailto:rachel@strangenoises.org">rachel@strangenoises.org</a>)
commit db54fca9b86aa124447d11d2bdbe359a2742cfd5
Author: Christian König <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>>
Date: Tue Jan 28 15:22:05 2014 +0100
st/vdpau: add flush on unmap
Flush the context when we unmap a buffer, otherwise VDPAU might
start rendering the next frame while we still reference that buffer.
Signed-off-by: Christian König <<a href="mailto:christian.koenig@amd.com">christian.koenig@amd.com</a>>
Tested-by: StrangeNoises (<a href="mailto:rachel@strangenoises.org">rachel@strangenoises.org</a>)
Additionally cherry-picked to 10.1 branch.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>