All of lore.kernel.org
 help / color / mirror / Atom feed
From: VDR User <user.vdr@gmail.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "mailing list: alsa-dev" <alsa-devel@alsa-project.org>
Subject: Re: NVIDIA HDMI surround sound is broken starting with kernel 2.6.36
Date: Mon, 31 Jan 2011 10:37:05 -0800	[thread overview]
Message-ID: <AANLkTikx4pVSHanCeDymo_0oDEE41TFiddNFhg5gh-NZ@mail.gmail.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0310C8E1CB@HQMAIL01.nvidia.com>

On Mon, Jan 31, 2011 at 9:51 AM, Stephen Warren <swarren@nvidia.com> wrote:
>> Also, even though the eld file is removed, the eld info is _not_
>> updated when stopping alsa & unloading drivers, then reloading.  A
>> reboot is required to get the eld info to update.  This is why I cold
>> boot the pc for each test.
>
> The NVIDIA graphics driver reads the monitor's EDID and passed the ELD
> information to the audio HW, from whence it is read by the ALSA driver.
> The EDID is only read when the X server is started, or perhaps when you
> click the "detect displays" button in the nvidia-settings utility.
>
> Hence, restarting X (e.g. logout/login), or using nvidia-settings, is
> probably sufficient to update the ELD data; no reboot required.

That explains why the ELD info isn't updated, although doesn't explain
the actual problem of missing channels.  I do think it's worthy to
rethink that behavior in the Nvidia driver.  The reason being that
many users, like myself, are using an htpc environment where the
audio/video output is connected directly to a tv or home theater
receiver.  In my case it's a receiver that is turned on/off as needed.
 There is no keyboard, mouse, or anything other then an IR remote
control to navigate the software I'm running.  To click "detect
displays" would mean digging the box out of its current location and
connecting a monitor & mouse to it just to do so.  Extremely
inconvenient.  I would guess that the best solution would be the
Nvidia driver having the ability to update the ELD info upon request.
There's got to be method of detecting things like receivers being
turned on/off.

Maybe another thread should be started regarding that issue since
we're getting away from the problem of missing channels.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2011-01-31 18:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 17:38 NVIDIA HDMI surround sound is broken starting with kernel 2.6.36 VDR User
2011-01-31 17:51 ` Stephen Warren
2011-01-31 18:37   ` VDR User [this message]
2011-02-04  0:08 ` 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=AANLkTikx4pVSHanCeDymo_0oDEE41TFiddNFhg5gh-NZ@mail.gmail.com \
    --to=user.vdr@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.