From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100510] [radeon] Heavy artifacts during hw accelerated playback of wmv files
Date: Fri, 31 Mar 2017 13:33:50 +0000 [thread overview]
Message-ID: <bug-100510-502-duc88uXmfu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100510-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1211 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100510
Christian König <deathsimple@vodafone.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #130615|0 |1
is obsolete| |
--- Comment #5 from Christian König <deathsimple@vodafone.de> ---
Created attachment 130618
--> https://bugs.freedesktop.org/attachment.cgi?id=130618&action=edit
Hack number 2 for testing
Ok, just as I expected we suddenly don't put buffers into VRAM any more and the
UVD block has an undocumented requirement for WMV playback that those buffers
needs to be in VRAM.
No idea why user space is broken, but the kernel should catch such cases and
force them into VRAM when the hardware needs that.
Please revert the last hack and try this one. It should only the first and
second buffer into VRAM.
If that doesn't work try to change the if so that the first,second and third
buffer are forced into VRAM etc....
I need to know which one is needed in VRAM here.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2814 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-31 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 10:06 [Bug 100510] [radeon] Heavy artifacts during hw accelerated playback of wmv files bugzilla-daemon
2017-03-31 11:39 ` bugzilla-daemon
2017-03-31 11:44 ` bugzilla-daemon
2017-03-31 11:53 ` bugzilla-daemon
2017-03-31 13:07 ` bugzilla-daemon
2017-03-31 13:33 ` bugzilla-daemon [this message]
2017-04-03 9:32 ` bugzilla-daemon
2017-04-12 10:12 ` bugzilla-daemon
2017-04-12 10:12 ` bugzilla-daemon
2017-04-12 15:05 ` bugzilla-daemon
2017-04-12 17:15 ` bugzilla-daemon
2017-05-17 10:00 ` bugzilla-daemon
2017-05-17 14:42 ` 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-100510-502-duc88uXmfu@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