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: Wed, 12 Apr 2017 17:15:14 +0000 [thread overview]
Message-ID: <bug-100510-502-56FQHm6EC3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100510-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 505 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100510
--- Comment #9 from Christian König <deathsimple@vodafone.de> ---
(In reply to Michel Dänzer from comment #8)
> Thanks, but I actually receive updates via the dri-devel mailing list.
>
> Do we know yet which flags are getting passed to radeon_bo_open for the
> BO(s) in question?
No, so far I've concentrated on figuring out what's going on inside the kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1466 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-04-12 17:15 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
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 [this message]
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-56FQHm6EC3@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.