From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 28 Aug 2002 10:45:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 28 Aug 2002 10:45:17 -0400 Received: from twilight.ucw.cz ([195.39.74.230]:38821 "EHLO twilight.ucw.cz") by vger.kernel.org with ESMTP id ; Wed, 28 Aug 2002 10:45:17 -0400 Date: Wed, 28 Aug 2002 16:49:08 +0200 From: Vojtech Pavlik To: Gerhard Mack Cc: Vojtech Pavlik , Mikael Pettersson , Linus Torvalds , Kernel Mailing List Subject: Re: 2.5.32 doesn't beep? Message-ID: <20020828164908.B17287@ucw.cz> References: <20020828150522.A13090@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gmack@innerfire.net on Wed, Aug 28, 2002 at 09:58:42AM -0400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 28, 2002 at 09:58:42AM -0400, Gerhard Mack wrote: > On Wed, 28 Aug 2002, Vojtech Pavlik wrote: > > > 2.5.32 still has quite complex input core config options - sorry, my > > fault, and I'll fix it soon. You have to enable CONFIG_INPUT_MISC and > > CONFIG_INPUT_PCSPKR. > > That begs the question: > How do I input using the PC speaker ? Reverse the time? Anyway, it makes sense, since for example Sun keyboards (and others) have a beeper built into them, and those are input devices. So the easiest way is to define PC speaker to be an input device as well and then the common code can be the same. -- Vojtech Pavlik SuSE Labs