From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761543AbYEPPXy (ORCPT ); Fri, 16 May 2008 11:23:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759178AbYEPPX1 (ORCPT ); Fri, 16 May 2008 11:23:27 -0400 Received: from mx2.suse.de ([195.135.220.15]:49669 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758514AbYEPPX0 (ORCPT ); Fri, 16 May 2008 11:23:26 -0400 Date: Fri, 16 May 2008 17:23:24 +0200 Message-ID: From: Takashi Iwai To: Jan Engelhardt Cc: Stas Sergeev , Roberto Oppedisano , LKML Subject: Re: Non-working snd-pcsp In-Reply-To: References: <482737BE.20502@infracom.it> <4827415A.7060101@aknet.ru> <482756F0.8020609@infracom.it> <48275D8D.10500@aknet.ru> <4827F0A1.9090600@infracom.it> <48288ACC.1020909@aknet.ru> <48299F08.2060702@infracom.it> <4829B6A1.90707@infracom.it> <482A7A17.8070706@infracom.it> <482C9A3E.3000009@infracom.it> <482C9F3E.4050104@aknet.ru> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta28) (fuki) (+CVS-20070806) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Fri, 16 May 2008 17:18:36 +0200 (CEST), Jan Engelhardt wrote: > > > 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. Indeed snd-pcsp contains the input pcspkr code. Yes, it's redundant, but separating them isn't trivial. Takashi