From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108937] [radeonsi, RX480] VAAPI H.264 decoder produces garbage on YouTube in Chromium with h264ify
Date: Wed, 05 Dec 2018 08:45:51 +0000 [thread overview]
Message-ID: <bug-108937-502-dEsn7Rerdz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108937-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 693 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108937
--- Comment #7 from network723@rkmail.ru ---
(In reply to Christian König from comment #4)
> Alternatively update the applications.
>
> The problem is that the driver exposes 10bit RGB and the applications
> selects that for some reason but actually can't handle it correctly.
Could you please confirm that it is a bug of application and not Mesa? I had an
argument with my favorite distro's maintainers on this, and their point is that
other drivers (intel and nouveau) don't have this problem. Do these drivers
even expose 10bit color configs?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1680 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-12-05 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 9:25 [Bug 108937] [radeonsi, RX480] VAAPI H.264 decoder produces garbage on YouTube in Chromium with h264ify bugzilla-daemon
2018-12-04 9:27 ` bugzilla-daemon
2018-12-04 20:53 ` bugzilla-daemon
2018-12-05 0:26 ` bugzilla-daemon
2018-12-05 7:38 ` bugzilla-daemon
2018-12-05 7:39 ` bugzilla-daemon
2018-12-05 7:41 ` bugzilla-daemon
2018-12-05 8:45 ` bugzilla-daemon [this message]
2018-12-05 8:52 ` 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-108937-502-dEsn7Rerdz@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