From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92827] Tonga: No Sound over HDMI with connected AV receiver
Date: Thu, 19 May 2016 17:25:22 +0000 [thread overview]
Message-ID: <bug-92827-502-eFJbpaGhRS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92827-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 513 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92827
--- Comment #3 from Maximilian Böhm <winlux@gmail.com> ---
At least something to await for! Would be neat to put this info somewhere in a
non-dev press release. I fiddled many hours with this issue without knowing
anything about the state of HDMI audio on AMDGPU. There must be countless
frustrated users, even more when you think of the Ubuntu 16.04 shift away from
fglrx.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1301 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:[~2016-05-19 17:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 0:31 [Bug 92827] Tonga: No Sound over HDMI with connected AV receiver bugzilla-daemon
2016-05-19 16:33 ` bugzilla-daemon
2016-05-19 16:40 ` bugzilla-daemon
2016-05-19 17:25 ` bugzilla-daemon [this message]
2017-10-15 18:46 ` bugzilla-daemon
2017-11-24 17:12 ` bugzilla-daemon
2017-11-24 19:28 ` bugzilla-daemon
2018-02-04 15:28 ` bugzilla-daemon
2018-02-04 19:27 ` bugzilla-daemon
2018-02-05 11:41 ` bugzilla-daemon
2018-02-09 0:28 ` bugzilla-daemon
2018-02-12 16:45 ` bugzilla-daemon
2018-02-12 20:17 ` bugzilla-daemon
2019-11-19 8:06 ` 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-92827-502-eFJbpaGhRS@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).