From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73191] [radeonsi] vdpau playback issues, skipping & looping
Date: Tue, 11 Feb 2014 12:05:04 +0000 [thread overview]
Message-ID: <bug-73191-502-oNKfhpugXJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73191-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 971 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73191
--- Comment #36 from Kertesz Laszlo <laszlo.kertesz@gmail.com> ---
> As I already tested with this commit applied to XBMC (was already in the now
> defunct amd branch and I picked it up), looking at what I used and what you
> have, I think mesa git makes the most difference (kernel?). It may be worth
> backporting what is needed to 10.1 so that most people can benefit it as
> soon as it's released. The second flush patch (st/vdpau: add flush on unmap)
> is at least missing from 10.1 branch (but is not sufficient as I applied it
> manually on top of orginal rc1 tarball).
Might be. I built mesa about an hour or less before i built xbmc, kernel is
3.14 rc1+, almost rc2.
That commit was the last in the FernetMenta's xbmc git at that point (thats why
i saw it). Note that i re-cloned the whole xbmc git from scratch before
building it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1815 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-02-11 12:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 18:32 [Bug 73191] New: [radeonsi] vdpau playback issues, skipping & looping bugzilla-daemon
2014-01-09 4:28 ` [Bug 73191] " bugzilla-daemon
2014-01-10 1:58 ` bugzilla-daemon
2014-01-10 8:51 ` bugzilla-daemon
2014-01-10 11:05 ` bugzilla-daemon
2014-01-10 11:24 ` bugzilla-daemon
2014-01-10 11:42 ` bugzilla-daemon
2014-01-10 18:50 ` bugzilla-daemon
2014-01-10 19:18 ` bugzilla-daemon
2014-01-10 19:38 ` bugzilla-daemon
2014-01-11 10:21 ` bugzilla-daemon
2014-01-11 11:22 ` bugzilla-daemon
2014-01-11 11:45 ` bugzilla-daemon
2014-01-11 11:55 ` bugzilla-daemon
2014-01-11 16:21 ` bugzilla-daemon
2014-01-11 19:06 ` bugzilla-daemon
2014-01-11 19:16 ` bugzilla-daemon
2014-01-11 19:33 ` bugzilla-daemon
2014-01-11 19:35 ` bugzilla-daemon
2014-01-11 19:40 ` bugzilla-daemon
2014-01-11 19:41 ` bugzilla-daemon
2014-01-12 0:56 ` bugzilla-daemon
2014-01-12 7:11 ` bugzilla-daemon
2014-01-12 14:51 ` bugzilla-daemon
2014-01-28 3:44 ` bugzilla-daemon
2014-01-28 12:02 ` bugzilla-daemon
2014-01-28 12:06 ` bugzilla-daemon
2014-01-28 13:07 ` bugzilla-daemon
2014-01-28 13:47 ` bugzilla-daemon
2014-01-28 13:58 ` bugzilla-daemon
2014-01-28 22:37 ` bugzilla-daemon
2014-02-04 6:59 ` bugzilla-daemon
2014-02-04 12:02 ` bugzilla-daemon
2014-02-09 17:29 ` bugzilla-daemon
2014-02-10 20:27 ` bugzilla-daemon
2014-02-11 8:57 ` bugzilla-daemon
2014-02-11 12:05 ` bugzilla-daemon [this message]
2014-02-11 12:10 ` bugzilla-daemon
2014-02-11 12:16 ` bugzilla-daemon
2014-02-11 12:26 ` bugzilla-daemon
2014-02-11 12:48 ` bugzilla-daemon
2014-02-12 20:01 ` bugzilla-daemon
2014-02-24 19:28 ` bugzilla-daemon
2014-02-25 9:36 ` 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-73191-502-oNKfhpugXJ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.