alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mohammad Bahathir Hashim <bahathir@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: HDMI on HDA device=3
Date: Wed, 10 Nov 2010 03:12:42 +0000 (UTC)	[thread overview]
Message-ID: <ibd2j9$8he$1@dough.gmane.org> (raw)
In-Reply-To: alpine.LNX.2.00.1011091853230.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, 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;
>
> No, 1.7 but 1.1 (hw device 7 is logical device 1 - aka second device - for 
> hdmi).
>
>  						Jaroslav
>
> -----
> Jaroslav Kysela <perex@perex.cz>
> Linux Kernel Sound Maintainer
> ALSA Project, Red Hat, Inc.

Yup, I tried both -ao alsa:device=hdmi=1.1 and -ao alsa:device=1.7,
but, I got same or similar errors.

Thanks :)

      reply	other threads:[~2010-11-10  3:12 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
2010-11-09 17:54       ` Jaroslav Kysela
2010-11-10  3:12         ` Mohammad Bahathir Hashim [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='ibd2j9$8he$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).