From: Shawn Bohrer <shawn.bohrer@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: 3.7 HDMI channel map regression
Date: Sun, 17 Feb 2013 11:01:11 -0600 [thread overview]
Message-ID: <20130217170111.GA21967@lintop> (raw)
In-Reply-To: <s5h621rcp8y.wl%tiwai@suse.de>
On Sun, Feb 17, 2013 at 09:34:53AM +0100, Takashi Iwai wrote:
> At Sat, 16 Feb 2013 18:22:25 -0600,
> Shawn Bohrer wrote:
> >
> > On Mon, Jan 28, 2013 at 08:52:05PM -0600, Shawn Bohrer wrote:
> > > On Mon, Jan 28, 2013 at 09:56:33AM +0100, Takashi Iwai wrote:
> > > > At Sun, 27 Jan 2013 19:18:27 -0600,
> > > > Shawn Bohrer wrote:
> > > > >
> > > > > Hi Takashi,
> > > > >
> > > > > I recently updated my HTPC from 3.6.11 to 3.7.2 and this caused my RL
> > > > > and FC channels to swap, and my RR and LFE channels to swap for PCM
> > > > > audio. Doing a git bisect identified
> > > > > d45e6889ee69456a4d5b1bbb32252f460cd48fa9 "ALSA: hda - Provide the
> > > > > proper channel mapping for generic HDMI driver" as the commit that
> > > > > caused my channels to swap. The commit doesn't revert cleanly on
> > > > > 3.7.4, and I haven't really looked to see what the correct fix might
> > > > > be.
> > > > >
> > > > > Some info that may be relevant, the sound card is a:
> > > > >
> > > > > 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset
> > > > > Family High Definition Audio Controller (rev 04)
> > > > >
> > > > > The machine is running Fedora 18 and audio goes over HDMI to a 5.1
> > > > > receiver. I'm not really sure what other info you might need, but
> > > > > let me know if you need something else or have any patches you would
> > > > > like me to test.
> > > >
> > > > OK, it's the first time to get a bug report about this.
> > > > Could you tell me how did you test it (i.e. which application, which
> > > > sound backend)? Can you confirm that it's reproduced via speaker-test
> > > > program in alsa-utils package?
> > >
> > > I originally noticed the problem when all of the dialog started coming
> > > out of my rear left speaker in MythTV after the kernel update. Then I
> > > started using the Gnome 3 sound configuration gui in the system
> > > settings which has a speaker test and I assume is using pulseaudio.
> > > Running 'speaker-test -c6 -l1 -twav' also reproduces the problem.
> > >
> > > For reference here are the versions of the various packages that I'm
> > > running:
> > >
> > > alsa-utils-1.0.26-1.fc18.x86_64
> > > alsa-firmware-1.0.25-2.fc18.noarch
> > > alsa-plugins-pulseaudio-1.0.26-2.fc18.x86_64
> > > alsa-lib-devel-1.0.26-2.fc18.x86_64
> > > alsa-lib-1.0.26-2.fc18.x86_64
> > > alsa-tools-firmware-1.0.26.1-1.fc18.x86_64
> > > pulseaudio-gdm-hooks-2.1-5.fc18.x86_64
> > > pulseaudio-libs-2.1-5.fc18.x86_64
> > > pulseaudio-libs-glib2-2.1-5.fc18.x86_64
> > > pulseaudio-module-x11-2.1-5.fc18.x86_64
> > > pulseaudio-module-bluetooth-2.1-5.fc18.x86_64
> > > pulseaudio-2.1-5.fc18.x86_64
> > > pulseaudio-utils-2.1-5.fc18.x86_64
> >
> > Hi Takashi,
> >
> > Any updates on this issue? I'd really like to see this issue fixed
> > and am happy to help in any way I can. Until this gets fixed I'm
> > stuck on a 3.6.* kernel.
>
> There is one fix in sound git tree regarding the HDMI channel map, but
> it's queued for 3.9 kernel (then backported to stable tree).
> Try sound.git tree or wait for a while until the upstream merge
> process above is done.
Thanks Takashi, I just tested the sound.git master branch and this
does indeed fix my issue. I'll look forward to this going into 3.9.
--
Shawn
prev parent reply other threads:[~2013-02-17 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 1:18 3.7 HDMI channel map regression Shawn Bohrer
2013-01-28 8:56 ` Takashi Iwai
2013-01-29 2:52 ` Shawn Bohrer
2013-02-17 0:22 ` Shawn Bohrer
2013-02-17 8:34 ` Takashi Iwai
2013-02-17 17:01 ` Shawn Bohrer [this message]
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=20130217170111.GA21967@lintop \
--to=shawn.bohrer@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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).