linux-kernel - Re: 2.6.23-rc4-mm1 - git-alsa.patch breaks audio 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hhcm8rhf5.wl%tiwai@suse.de>
Date:	Wed, 05 Sep 2007 22:22:38 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Valdis.Kletnieks@...edu
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc4-mm1 - git-alsa.patch breaks audio on Dell Latitude D820

At Wed, 05 Sep 2007 15:54:55 -0400,
Valdis.Kletnieks@...edu wrote:
> 
> On Wed, 05 Sep 2007 15:46:34 EDT, Valdis.Kletnieks@...edu said:
> >
> > % grep HDA_ .config
> > CONFIG_SND_HDA_INTEL=y
> > # CONFIG_SND_HDA_HWDEP is not set
> > CONFIG_SND_HDA_CODEC_REALTEK=y
> > CONFIG_SND_HDA_CODEC_ANALOG=y
> > CONFIG_SND_HDA_CODEC_SIGMATEL=y
> > # CONFIG_SND_HDA_CODEC_VIA is not set
> > # CONFIG_SND_HDA_CODEC_ATIHDMI is not set
> > # CONFIG_SND_HDA_CODEC_CONEXANT is not set
> > # CONFIG_SND_HDA_CODEC_CMEDIA is not set
> > # CONFIG_SND_HDA_CODEC_SI3054 is not set
> > CONFIG_SND_HDA_GENERIC=y
> > # CONFIG_SND_HDA_POWER_SAVE is not set
> 
> For the record, REALTEK and ANALOG got set to Y in my bisect build because of
> the infamous "defaults to Y" syndrome - after I saw Sigmatel go by I wised up
> and started saying N, but forgot to clean up the first two.  Those two are
> disabled in the live -rc4-mm1 .config, and it has the same issue.

The "default Y" is the correct behavior in this case.  These configs
are just splits from a single config, corresponding to all Y.


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/