From: Mohammad Bahathir Hashim <bahathir@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: HDMI on HDA device=3
Date: Tue, 9 Nov 2010 17:04:12 +0000 (UTC) [thread overview]
Message-ID: <ibbuuc$4ar$1@dough.gmane.org> (raw)
In-Reply-To: alpine.LNX.2.00.1011091739060.29422@eeebox2.perex-int.cz
On 2010-11-09, Jaroslav Kysela <perex@perex.cz> wrote:
> On Tue, 9 Nov 2010, Mohammad Bahathir Hashim wrote:
>
>> On 2010-11-09, David Henningsson <david.henningsson@canonical.com> wrote:
>>> I have seen a few HDMIs which share the HDA controller with the onboard
>>> sound card, but the codecs are different, e g the onboard one is at
>>> address #0 and the HDMI is at address #3 - or even #3, #7, #8 and #9 in
>>> some cases.
>>>
>>> Now, if the user specifies the device string hdmi:x (where x is card
>>> name/number), I'd like it to kind of autodetect this and use DEV=3
>>> instead of DEV=0, and without breaking the cards where the hdmi is a
>>> separate card with a codec at address #0. However, it still seems like
>>> the device is at DEV=3 somehow.
>>>
>>> Now, looking at /usr/share/alsa/cards/HDA-Intel.conf, I notice that
>>> there are entries HDA-Intel.pcm.hdmi.0 which sets DEV=3, so it seems
>>> like someone already thought of this. However, just using "hdmi:x" does
>>> not trigger "DEV=3". I'm still not grepping all of the alsa lisp
>>> architecture stuff, so could someone explain to me how the
>>> HDA-Intel.pcm.hdmi.0 entry relates to the "hdmi:x" alsa device string?
>>>
>>
>> I am not sure about Intel HDMI, but, in my case with MacbookPro 6,2
>> (15" Mid 2010); the HDMI audio stream via NVIDIA HDMI can only be
>> started if I use hw:1,7 (or Mplayer's -ao alsa:device=hw=1.7). No
>
> This should be equal to '-ao alsa:device=hdmi=1.1' (hdmi:1,1 in ALSA
> naming).
>
> Jaroslav
>
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, Red Hat, Inc.
Ok, I tried the -ao alsa:device=hdmi=1.7 ... but, MPlayer complains;
[AO_ALSA] alsa-lib: confmisc.c:1286:(snd_func_refer) Unable to find
definition
'cards.HDA-Intel.pcm.hdmi.7:CARD=1,AES0=4,AES1=130,AES2=0,AES3=2'
[AO_ALSA] alsa-lib: conf.c:4154:(_snd_config_evaluate) function
snd_func_refer returned error: No such file or directory [AO_ALSA]
alsa-lib: conf.c:4633:(snd_config_expand) Evaluate error: No such file
or directory
[AO_ALSA] alsa-lib: pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM
hdmi:1,7 [AO_ALSA] Playback open error: No such file or directory
Failed to initialize audio driver 'alsa:device=hdmi=1.7' Could not
open/initialize audio device -> no sound.
In other words, in current default alsa configuration, 'hdmi' keyword
is only for Intel HDMI HDA. But, for MacbookPro6,2 , I need to use
NVIDIA HDMI. That's why (-ao alsa:device=hw=1.7) is much better
option; for more generic purposes. :)
Thank you.
next prev parent reply other threads:[~2010-11-09 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 14:42 HDMI on HDA device=3 David Henningsson
2010-11-09 14:58 ` Jaroslav Kysela
2010-11-09 15:16 ` David Henningsson
2010-11-09 16:38 ` Jaroslav Kysela
2010-11-09 16:24 ` Mohammad Bahathir Hashim
2010-11-09 16:40 ` Jaroslav Kysela
2010-11-09 17:04 ` Mohammad Bahathir Hashim [this message]
2010-11-09 17:54 ` Jaroslav Kysela
2010-11-10 3:12 ` Mohammad Bahathir Hashim
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='ibbuuc$4ar$1@dough.gmane.org' \
--to=bahathir@gmail.com \
--cc=alsa-devel@alsa-project.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).