From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73191] [radeonsi] vdpau playback issues, skipping & looping
Date: Sat, 11 Jan 2014 19:16:35 +0000 [thread overview]
Message-ID: <bug-73191-502-0WXsVKhkjb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73191-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 912 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=73191
--- Comment #16 from Rachel Greenham <rachel@strangenoises.org> ---
It remains interesting (maybe) that you're having problems with 10.0.1 and I
don't.
Looking at the commit, with an outside eye, it seems to be consolidating bits
of code that were split out for different cards into a single implementation.
So is it possible this bug actually arose some time back, only affecting a few
cards (eg: yours) but after the consolidation it affects more cards (eg: now
including mine too).
We're both south-islands hd7000-series cards, but not the exact same. Idunno,
just my observations.
Can you take a video like the one I did (maybe just for consistency using the
video sample I uploaded, linked in an earlier comment), so we can actually all
see and confirm it's the same problem?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1708 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-01-11 19:16 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 [this message]
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
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-0WXsVKhkjb@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.