From: Anssi Hannula <anssi.hannula@iki.fi>
To: Stephen Warren <swarren@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ANNOUNCE: NVIDIA HDMI audio documentation
Date: Sat, 05 Feb 2011 22:05:15 +0200 [thread overview]
Message-ID: <4D4DAD7B.20406@iki.fi> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310C8EA6D@HQMAIL01.nvidia.com>
On 04.02.2011 00:37, Stephen Warren wrote:
> I have written a document re: how to understand and trouble-shoot issues
> with audio-over-HDMI on NVIDIA GPUs. It's available at:
>
> ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html
>
> The intent is to provide all the support information I've given various
> people on support forums in a centralized place.
>
> Hope this helps!
A nice document, thanks :)
A couple of comments:
> Early chipsets (ION an earlier) do not support PD or ELD information. In
> this case, the ALSA driver assumes that a monitor is always attached,
> and supports "basic audio” (stereo 16-bit PCM only).
The ALSA driver actually assumes that the monitor supports everything.
> 10.3. Under-Enumeration of Logical Devices
This section misses one patch:
http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=e6d5dcf1f625984605d362338d71162de45a6c60
> 12.4. Verify Your ELD Is Valid
This section has "44100 48000 88200" multiple times. Maybe one should
mention that those are currently shown incorrectly (as per "[alsa-devel]
HDA - hdmi_show_short_audio_desc puts wrong rates in eld#N"). Maybe also
in chapter 10, though it is a very minor issue (it just affects the
display, not the actual used values).
--
Anssi Hannula
next prev parent reply other threads:[~2011-02-05 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 22:37 ANNOUNCE: NVIDIA HDMI audio documentation Stephen Warren
2011-02-05 20:05 ` Anssi Hannula [this message]
2011-02-07 17:39 ` Stephen Warren
2011-02-07 20:49 ` Anssi Hannula
2011-02-07 20:53 ` Stephen Warren
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=4D4DAD7B.20406@iki.fi \
--to=anssi.hannula@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=swarren@nvidia.com \
/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).