alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Nvidia HDMI and four codecs
Date: Tue, 01 Feb 2011 09:10:19 +0100	[thread overview]
Message-ID: <4D47BFEB.8040602@canonical.com> (raw)

I've seen a few Nvidia HDMI's recently which have four HDMI codecs 
connected to the same HDA controller. The problem is that we don't know 
which one(s) of these four that is the real one. So people will have to 
try devices "hdmi:Nvidia,0", "hdmi:Nvidia,1", "hdmi:Nvidia,2" and 
"hdmi:Nvidia,3" to figure out which one is the right one. (And by 
empirical testing we know that it isn't always the first one.)

Thinking PulseAudio and/or "Just Works", this is not good enough, so is 
there a way to know beforehand which one of these four that is actually 
physically connected?

I'd love BIOS to provide a good codec probe mask, a pin config default, 
or something similar, but given a codec-proc I can't see any difference 
between the real ones and the unconnected ones, so I don't know how to 
fix up the driver without hardcoding/quirking every one of them. Any hints?

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

             reply	other threads:[~2011-02-01  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  8:10 David Henningsson [this message]
2011-02-01 16:36 ` Nvidia HDMI and four codecs Stephen Warren
2011-02-02  8:03   ` David Henningsson
2011-02-03 20:35     ` Stephen Warren
2011-02-04  7:27       ` David Henningsson
2011-02-04 23:25         ` Stephen Warren
2011-02-07  9:15           ` David Henningsson

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=4D47BFEB.8040602@canonical.com \
    --to=david.henningsson@canonical.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).