From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85241] audio over HDMI on AMD E-350 with radeon driver
Date: Mon, 29 Sep 2014 15:00:36 +0000 [thread overview]
Message-ID: <bug-85241-2300-BhUKSKNpOO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85241-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85241
Alex Deucher <alexdeucher@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexdeucher@gmail.com
--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
Are you actually seeing a problem with the audio playback or is this bug
strictly about the messaged in the kernel log. If there is a playback problem,
can you bisect to indentify what commit caused the regression? Also, please
attach files directly to this bug rather than using pastebin. The messages are
due to your monitor not providing a speaker allocation block. I think 3.14 was
probably the first kernel were we actually tried to query the monitor for the
speaker allocation block from the monitor. The gfx driver passes this
information to the audio driver and the audio driver uses it to properly set up
the speaker layout.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-09-29 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 14:36 [Bug 85241] New: audio over HDMI on AMD E-350 with radeon driver bugzilla-daemon
2014-09-28 14:36 ` [Bug 85241] " bugzilla-daemon
2014-09-29 15:00 ` bugzilla-daemon [this message]
2014-10-06 18:21 ` bugzilla-daemon
2015-07-31 18:57 ` bugzilla-daemon
2016-05-09 14:09 ` bugzilla-daemon
2016-08-15 6:05 ` 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-85241-2300-BhUKSKNpOO@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 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.