From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106490] VA-API video deconding broken for Chromium on Mesa 18.0.3
Date: Thu, 18 Oct 2018 14:04:00 +0000 [thread overview]
Message-ID: <bug-106490-502-AWbrGLZQGo@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106490-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 617 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106490
--- Comment #6 from Tomáš Chvátal <tomas.chvatal@gmail.com> ---
This might be possible duplicate of:
https://bugs.freedesktop.org/show_bug.cgi?id=104597
I can reproduce this too on openSUSE with Mesa 18.1. The issue itself is
exposed only on Radeon driver not on intel/nouveau.
The workaround of course works, but I think there must be some bug in Mesa
radeonsi code as the intel/nouveau both manage to play stuff properly using the
libva and the conversion to opengl.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1562 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:[~2018-10-18 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 16:31 [Bug 106490] VA-API video deconding broken for Chromium on Mesa 18.0.3 bugzilla-daemon
2018-05-14 10:31 ` bugzilla-daemon
2018-05-22 10:40 ` bugzilla-daemon
2018-05-22 10:47 ` bugzilla-daemon
2018-05-22 11:11 ` bugzilla-daemon
2018-06-23 1:18 ` bugzilla-daemon
2018-10-18 14:04 ` bugzilla-daemon [this message]
2018-12-15 12:03 ` bugzilla-daemon
2019-04-01 10:11 ` 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-106490-502-AWbrGLZQGo@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.