Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anssi Hannula <anssi.hannula@iki.fi>
To: VDR User <user.vdr@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Bug in setting channels, related to recent ELD/EDID changes?
Date: Tue, 11 Jan 2011 22:47:33 +0200	[thread overview]
Message-ID: <4D2CC1E5.5020105@iki.fi> (raw)
In-Reply-To: <AANLkTinPbj6K8Lw9PiCsHrqRBT=fwj6YvCrnOh7YK3YB@mail.gmail.com>

On 11.01.2011 22:37, VDR User wrote:
> First, THANK YOU for addressing this!  However, I have a couple
> questions.  Which solution was implemented; a true/false switch
> controlling the behavior between the old _working_ method, or the new
> ELD restricted one?  Or, this module parameter thing that was
> mentioned?
> 
> As a user having to deal with the frustration of this problem, I
> absolutely think the true/false switch is the best solution as it's
> set-and-forget.  Set it one time, get the behavior you _want_, and not
> have to bother with it again.  With the module parameter thing, it
> sounds like you have to change module parameters according to what you
> want at the moment.  Or is it that the true/false switch is controlled
> by a module param?  Maybe I've misinterpreted it but it's not very
> clear.

Yes, it is a true/false switch controlled by a module parameter.

> So I grab alsa git, but how do I use the fix to restore the old behavior?

Set the module parameter static_hdmi_pcm of snd-hda-codec-hdmi to 1.

For example, by adding this into /etc/modprobe.conf:
options snd-hda-codec-hdmi static_hdmi_pcm=1

For the record, this is the commit:
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commitdiff;h=5eedd1422c2fc79c2f9ed8b71056b97570f95572

-- 
Anssi Hannula

  reply	other threads:[~2011-01-11 20:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-23  2:22 Bug in setting channels, related to recent ELD/EDID changes? VDR User
2010-12-23  5:48 ` Anssi Hannula
2010-12-23  7:13   ` VDR User
2011-01-02 10:16     ` Anssi Hannula
2011-01-04 16:41       ` VDR User
2011-01-04 18:46         ` James Courtier-Dutton
2011-01-06  8:43           ` VDR User
2011-01-10 19:13           ` VDR User
2011-01-10 19:51       ` Takashi Iwai
     [not found]         ` <3a46493bd2a1ec3b74c89cb6970c9ab0.squirrel@mail.onse.fi>
     [not found]           ` <s5hk4icjy2t.wl%tiwai@suse.de>
2011-01-11 16:33             ` Anssi Hannula
2011-01-11 16:42               ` Takashi Iwai
2011-01-11 16:54                 ` Anssi Hannula
     [not found]             ` <s5hbp3nkj1z.wl%tiwai@suse.de>
2011-01-11 16:58               ` Anssi Hannula
2011-01-11 17:34                 ` Takashi Iwai
2011-01-11 20:37                   ` VDR User
2011-01-11 20:47                     ` Anssi Hannula [this message]
2011-01-12  6:37                       ` VDR User
2011-01-12  6:47                         ` Takashi Iwai
2011-01-22  2:53                       ` VDR User
2011-01-24 13:32                         ` Takashi Iwai

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=4D2CC1E5.5020105@iki.fi \
    --to=anssi.hannula@iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    --cc=user.vdr@gmail.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