From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110702] segfault in radeonsi HEVC hardware decoding with yuv420p10le
Date: Fri, 21 Jun 2019 08:12:01 +0000 [thread overview]
Message-ID: <bug-110702-502-oC5TZm5dxl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110702-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 357 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110702
--- Comment #12 from Pierre-Eric Pelloux-Prayer <pierre-eric.pelloux-prayer@amd.com> ---
Can you try the branch from
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1154 and report if it
fixes the issue for you?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1267 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-06-21 8:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 19:48 [Bug 110702] segfault in radeonsi HEVC hardware decoding bugzilla-daemon
2019-05-18 5:47 ` bugzilla-daemon
2019-05-19 14:36 ` bugzilla-daemon
2019-05-20 19:03 ` [Bug 110702] segfault in radeonsi HEVC hardware decoding with yuv420p10le bugzilla-daemon
2019-05-25 15:17 ` bugzilla-daemon
2019-06-15 8:02 ` bugzilla-daemon
2019-06-17 13:53 ` bugzilla-daemon
2019-06-17 16:03 ` bugzilla-daemon
2019-06-18 5:44 ` bugzilla-daemon
2019-06-19 13:11 ` bugzilla-daemon
2019-06-19 13:14 ` bugzilla-daemon
2019-06-19 13:30 ` bugzilla-daemon
2019-06-21 8:12 ` bugzilla-daemon [this message]
2019-06-22 1:00 ` bugzilla-daemon
2019-06-28 11:35 ` bugzilla-daemon
2019-06-28 22:41 ` bugzilla-daemon
2019-07-09 9:35 ` 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-110702-502-oC5TZm5dxl@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;
as well as URLs for NNTP newsgroup(s).