From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86351] HDMI audio garbled output on Radeon R9 280X
Date: Mon, 06 Jul 2015 05:29:00 +0000 [thread overview]
Message-ID: <bug-86351-2300-FD4d3xQOgj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86351-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=86351
--- Comment #13 from Lorenzo Bona <lorenz.bona@gmail.com> ---
(In reply to Alex Deucher from comment #12)
> What are the pci ids of the audio devices on the GPU? Does adding or
> updating your audio devices' entries in the hda driver like the following
> patch does help?
>
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=650474fb737c3e0ea0f6ab8e43c2cd161080ce5c
PCI id is 1002:aab0 and is already in that file.
Line 2237 and 2238.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-06 5:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 19:22 [Bug 86351] New: HDMI audio garbled output on Radeon R9 280X bugzilla-daemon
2014-10-15 19:22 ` [Bug 86351] " bugzilla-daemon
2014-10-15 19:23 ` bugzilla-daemon
2015-01-11 11:53 ` bugzilla-daemon
2015-01-11 12:20 ` bugzilla-daemon
2015-01-12 21:51 ` bugzilla-daemon
2015-01-13 16:18 ` bugzilla-daemon
2015-01-13 16:23 ` bugzilla-daemon
2015-01-13 16:41 ` bugzilla-daemon
2015-01-13 17:42 ` bugzilla-daemon
2015-07-04 22:31 ` bugzilla-daemon
2015-07-04 22:31 ` bugzilla-daemon
2015-07-06 2:58 ` bugzilla-daemon
2015-07-06 5:29 ` bugzilla-daemon [this message]
2015-07-10 22:10 ` bugzilla-daemon
2015-07-13 5:47 ` bugzilla-daemon
2015-08-26 19:19 ` bugzilla-daemon
2015-08-26 22:00 ` bugzilla-daemon
2015-09-15 15:19 ` bugzilla-daemon
2015-11-21 11:08 ` bugzilla-daemon
2016-01-30 22:31 ` bugzilla-daemon
2016-03-23 19:17 ` bugzilla-daemon
2016-03-23 19:58 ` bugzilla-daemon
2016-03-23 22:18 ` bugzilla-daemon
2016-03-28 21:36 ` bugzilla-daemon
2016-04-27 18:45 ` bugzilla-daemon
2017-03-24 0:56 ` bugzilla-daemon
2017-03-24 10:37 ` bugzilla-daemon
2017-03-24 11:22 ` bugzilla-daemon
2017-03-25 13:22 ` bugzilla-daemon
2018-01-23 18:05 ` bugzilla-daemon
2018-05-18 18:16 ` bugzilla-daemon
2018-05-31 7:09 ` bugzilla-daemon
2018-05-31 17:31 ` bugzilla-daemon
2019-03-23 8:27 ` bugzilla-daemon
2019-03-23 19:20 ` 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-86351-2300-FD4d3xQOgj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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).