From: "samuelchemla@orange.fr" <samuelchemla@orange.fr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA HDMI output not detected
Date: Thu, 23 Oct 2014 22:44:10 +0200 [thread overview]
Message-ID: <5449689A.20806@orange.fr> (raw)
In-Reply-To: <s5h8uk6yd8f.wl-tiwai@suse.de>
Hi,
there is no ELD file in /proc/asound nor /proc/asound/card0
On the EDID side, do you mean any EDID from any HDMI screen ?
I thought EDID file was screen dependant.
I know the screen is HDMI sound capable because I am using it with a
raspberry without problem... :-)
Regards,
Sam
On 23/10/2014 18:14, Takashi Iwai wrote:
> At Wed, 22 Oct 2014 19:46:58 +0200,
> samuelchemla@orange.fr wrote:
>> Hi guys,
>>
>> I opened a bug about HDMI sound output not detected on an NVIDIA optimus
>> laptop.
>> I don't know if HDMI sound card detection is up to ALSA, the kernel or
>> the video driver.
> Actually all of three are involved fairly tightly.
>
>> Could anyone give me a clue so the bug can be routed to its correct
>> destination?
>> Link to the bug:
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653
> You should start checking EDID on the video side and ELD on the audio
> side. ALSA driver shows the connection and ELD status in proc files
> and control elements. If EDID is given, but ELD (or monitor
> connection state) isn't, usually it's a video driver problem, e.g. the
> audio register bit isn't set properly.
>
>
> Takashi
prev parent reply other threads:[~2014-10-23 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 17:46 ALSA HDMI output not detected samuelchemla
2014-10-23 16:14 ` Takashi Iwai
2014-10-23 20:44 ` samuelchemla [this message]
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=5449689A.20806@orange.fr \
--to=samuelchemla@orange.fr \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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