From: Douglas Pearless <Douglas.Pearless@pearless.co.nz>
To: alsa-devel@alsa-project.org
Subject: Re: About HDMI audio driver
Date: Tue, 12 Jan 2010 23:54:37 +1300 [thread overview]
Message-ID: <4B4C54ED.9020600@pearless.co.nz> (raw)
In-Reply-To: <6B4D417B830BC44B8026029FD256F7F1BEBFFFD038@HKMAIL01.nvidia.com>
Is there any progress here as I'd like to use the audio over HDMI on my
GT220 ...
Cheers
Douglas.
On 29/12/2009 9:43 p.m., Wei Ni wrote:
> Ok, thanks for your reply.
> Happy holidays!
>
> Thanks
> Wei.
>
> -----Original Message-----
> From: Takashi Iwai [mailto:tiwai@suse.de]
> Sent: Tuesday, December 29, 2009 4:32 PM
> To: Wei Ni
> Cc: alsa-devel@alsa-project.org; Peer Chen
> Subject: Re: About HDMI audio driver
>
> At Tue, 29 Dec 2009 15:56:32 +0800,
> Wei Ni wrote:
>
>> Hi, Takashi
>> I'm a nvidia engineer. We plan to develop the new hdmi audio driver for the new chipset. It support the latest HD Audio Specification.
>> I download the latest kernel source, it has patch_intelhdmi.c. And this file have many defines and routines for HDMI operations.
>> If I develop hdmi driver, it also need to define the same functions in patch_nvhdmi.c, it seems not very well.
>> Do you have plan to change these codes to common code? I think these codes are common for HDMI audio.
>>
> Well, ideally, we merge all three patch_*hdmi.c into one, say,
> patch_hdmi.c. The merging of patch_atihdmi.c would be trivial, but
> nvidia one would need a bit more changes to add codec-specific
> setups.
>
> So, it'd be nice if you implement the newer code in that direction.
>
>
>> BTW I have a another question.
>> Because the standard ALSA channel mapping is different with the Windows setting. So we could use channel-slot assignment (verb 0x734) to fix.
>> How can I know the audio is using ALSA setting or Windows setting? Does there have any mechanism to support this operation?
>>
> Right now there is no "Windows" setting on ALSA.
> The channel map is fixed as FL/FR/RL/RR/C/LFE/SL/SR.
>
> I have a plan to add an API for querying / changing the channel map, but
> it's still a vaporware.
>
> BTW, I'm on vacation from tomorrow until Jan. 10. So the reply may be
> delayed.
>
>
> thanks,
>
> Takashi
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain
> confidential information. Any unauthorized review, use, disclosure or distribution
> is prohibited. If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2010-01-12 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 7:56 About HDMI audio driver Wei Ni
2009-12-29 8:31 ` Takashi Iwai
2009-12-29 8:43 ` Wei Ni
2010-01-12 10:54 ` Douglas Pearless [this message]
2010-02-03 6:54 ` VDR User
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=4B4C54ED.9020600@pearless.co.nz \
--to=douglas.pearless@pearless.co.nz \
--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).