[alsa-devel] About HDMI audio driver

Douglas Pearless Douglas.Pearless at pearless.co.nz
Tue Jan 12 11:54:37 CET 2010

Is there any progress here as I'd like to use the audio over HDMI on my 
GT220 ...

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 at suse.de]
> Sent: Tuesday, December 29, 2009 4:32 PM
> To: Wei Ni
> Cc: alsa-devel at 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 at alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

More information about the Alsa-devel mailing list