linux-kernel - Re: 2.6.28-rc2-mm1 - sound semi-busted on Dell Latitude D820

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: <s5h7i78ruzh.wl%tiwai@suse.de>
Date:	Thu, 13 Nov 2008 07:38:26 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Valdis.Kletnieks@...edu
Cc:	Andrew Morton <akpm@...ux-foundation.org>, perex@...ex.cz,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: 2.6.28-rc2-mm1 - sound semi-busted on Dell Latitude D820

At Wed, 12 Nov 2008 16:09:37 -0500,
Valdis.Kletnieks@...edu wrote:
> 
> On Tue, 11 Nov 2008 18:04:56 +0100, Takashi Iwai said:
> 
> Following up...
> 
> > > > To confirm a regression, could you copy sound/pci/hda/patch_sigmatel.c
> > > > from 2.6.27 kernel and check the driver works?  Does the same problem
> > > > exist in 2.6.28-rc kernel?
> 
> Yes, it was a regression - using the older patch_sigmatel.c in the -rc4-mm
> kernel worked fine.
> 
> > > Could you try the patch below?
> 
> > > There is another patch for a missing capture mux control, but in your
> > > case, it doesn't matter because you didn't change the value.
> > > I'll post that patch later, too.
> > 
> > Here is another fix.
> 
> > Subject: [PATCH] ALSA: hda - Add missing analog-mux mixer creation for STAC9200
> 
> Running with a current patch_sigmatel.c plus the two patches also works fine,
> so feel free to stick a Tested-By: on it if you wish...

Thanks for checking.

FYI, the patches have been already merged to Linus tree yesterday,
as I could confirm with other test cases.


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/