dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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, 09 May 2016 14:09:18 +0000	[thread overview]
Message-ID: <bug-85241-2300-vUREuKuAW1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85241-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=85241

mirh <mirh@protonmail.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mirh@protonmail.ch

--- Comment #4 from mirh <mirh@protonmail.ch> ---
Created attachment 215621
  --> https://bugzilla.kernel.org/attachment.cgi?id=215621&action=edit
TV was attached before booting.

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7403c515c49c033fec33df0814fffdc977e6acdc
I read this should be supposed to improve HDMI audio (it landed in 4.6-rc5). 

For as much as I have no problem with sound though, I'm still getting "no
speaker allocation for ELD" warnings. 

Also, I wouldn't know if the last EDID error is related or not (could just be
driver queried the interface before I could completely remove the cable)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-05-09 14:09 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
2014-10-06 18:21 ` bugzilla-daemon
2015-07-31 18:57 ` bugzilla-daemon
2016-05-09 14:09 ` bugzilla-daemon [this message]
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-vUREuKuAW1@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