linux-kernel - Re: [patch][rfc] depend pcspkr on CONFIG

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: <20091018075723.GI3935@core.coreip.homeip.net>
Date:	Sun, 18 Oct 2009 00:57:24 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Stas Sergeev <stsp@...et.ru>
Cc:	Linux kernel <linux-kernel@...r.kernel.org>,
	Dmitry Torokhov <dtor-oss@...cast.net>,
	Takashi Iwai <tiwai@...e.de>
Subject: Re: [patch][rfc] depend pcspkr on CONFIG_EMBEDDED

Hi Stas,

On Sun, Oct 18, 2009 at 01:22:27AM +0400, Stas Sergeev wrote:
> Hello.
>
> As most of the problems with snd-pcsp
> are now settled and the major distros
> are starting to unblacklist it and use
> instead of pcspkr:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539767
> I'd like to do that sneaky thing.
> The major argument for keeping pcspkr
> I've heard, was that it doesn't require
> the entire ALSA stack, and in this
> case I think it is usefull only with
> CONFIG_EMBEDDED. Right now it is a common
> situation when the both modules are
> built, and whichever gets loaded first,
> works.
> So can something like the attached
> patch be applied?

I think it is up to destribution to select the driver they want to use
and blacklist the one they don't want. No need to change the kernel.

-- 
Dmitry
--
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/