linux-kernel - Re: Thinkpad hda regression in 3.3

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] [day] [month] [year] [list]

Message-ID: <s5hsjg1oah0.wl%tiwai@suse.de>
Date:	Wed, 18 Apr 2012 07:49:47 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Josh Boyer <jwboyer@...hat.com>
Cc:	Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org, kernel-team@...oraproject.org,
	kevin@...ye.com, cwickert@...oraproject.org
Subject: Re: Thinkpad hda regression in 3.3

At Tue, 17 Apr 2012 20:23:36 -0400,
Josh Boyer wrote:
> 
> On Fri, Apr 13, 2012 at 02:08:14PM -0400, Josh Boyer wrote:
> > On Fri, Apr 13, 2012 at 06:07:47PM +0200, Takashi Iwai wrote:
> > > At Fri, 13 Apr 2012 15:07:07 +0200,
> > > Takashi Iwai wrote:
> > > (snip)
> > > > If the above seem work (again, make sure that you adjust the mixer
> > > > mutes and levels), I'll make kernel patches to add these fixups
> > > > statically in the driver so that it works without extra patching.
> > > 
> > > Looking through alsa-info.sh outputs from various ThinkPad models I've
> > > gathered, it seems that we can use the same pin setups for all.
> > 
> > We had a user try the alsa-tp-dock patch on an X201 and it didn't seem
> > to work for them.  See bug
> > https://bugzilla.redhat.com/show_bug.cgi?id=806217
> > 
> > Perhaps the [codec] section isn't set properly for their configuration?
> > The alsa-info for their machine is in comment #9 of the bug.
> > 
> > > Below is a test patch for 3.3 kernel.  (Note that it'd give a merge
> > > conflict for 3.4 kernel.)
> > 
> > OK, I'll do a scratch build with this and get people to test.
> 
> I built your patch in a scratch kernel and have at least one user with a
> t510 laptop report success.  Christoph reported the mixers showing up,
> but it wasn't clear to me if his sound actually worked on the x201.
> I've CC'd both users (Kevin t510, Christoph x201 in a dock).

Good.  Should I wait for a copule of days for the test results before
merging the patch, or go for now?


thanks,

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/