linux-kernel - Re: Non-working snd-pcsp

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:	Fri, 16 May 2008 17:18:36 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Takashi Iwai <tiwai@...e.de>
cc:	Stas Sergeev <stsp@...et.ru>,
	Roberto Oppedisano <roberto.oppedisano@...racom.it>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Non-working snd-pcsp


On Friday 2008-05-16 15:40, Takashi Iwai wrote:
>> 
>> If it does not even beep when issuing Ctrl-G on the shell,
>> you probably need to modprobe pcspkr, if it is not built-in.
>> (At least this is with kernels a little less
>> recent than 2.6.25. )
>
>If snd-pcsp module is built, input pcspkr module won't be built...

Previously, with Stas's standalone patch, one was able to switch
between (a) no speaker (b) beep/pcspkr (c) beep/pcspkr and
PCM/snd-pcsp, all by means of modprobe/rmmod.

Now, if pcspkr is deactivated when snd-pcsp is built... I would
not get any tone out of that piece of hardware.
Except if snd-pcsp itself contains beep code, and that would
be sort of redundant when it is already in pcspkr.
--
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/