linux-kernel - Re: 3.8-rc1 patch_cirrus 4.0 regression...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 05 Feb 2013 17:34:15 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Daniel J Blueman <daniel@...ra.org>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	alsa-devel@...a-project.org
Subject: Re: 3.8-rc1 patch_cirrus 4.0 regression...

At Wed, 6 Feb 2013 00:29:54 +0800,
Daniel J Blueman wrote:
> 
> On 6 February 2013 00:16, Takashi Iwai <tiwai@...e.de> wrote:
> > At Wed, 6 Feb 2013 00:10:30 +0800,
> > Daniel J Blueman wrote:
> >>
> >> Hi Takashi,
> >>
> >> The v3.8-rc kernels have regressed from v3.7 with the quad-speaker
> >> arrangement on my Macbook Pro 10,1 - only the higher-frequency
> >> speakers work despite the front and rear channels being exposed in the
> >> mixer.
> >
> > Interesting.  So you have a machine with 4.0 built-in speaker instead
> > of 2.1?  Then we need to add a device-specific flag for it.  Currently
> > the driver assumes 2.1 system blindly because majority of machines
> > have that.
> >
> > FWIW, the codec parser code has been totally rewritten for 3.9, so any
> > patch to 3.8 won't be applied to 3.9 (and vice versa)...
> >
> > Could you give alsa-info.sh output on 3.8 kernel?  Then I'll try to
> > cook it for 3.9 (and maybe backport to 3.8).
> 
> Here's the output from the current alsa-info.sh on 3.8-rc6 with the
> two cited patches reverted [1]; let me know if you'd like 3.8-rc6
> pure.

Thanks.

> The sound is pretty impressive for a laptop when the low-frequecy
> speakers are enabled.

Which program are you using for testing the surrounds?
I'm interested in it because the commit you reverted is basically
providing only an additional information for the channel map, and it
doesn't change anything else.  It implies that some applications are
really referring to the chmap info.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/