Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 22 Aug 2002 16:36:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 22 Aug 2002 16:36:55 -0400 Received: from kweetal.tue.nl ([131.155.2.7]:28863 "EHLO kweetal.tue.nl") by vger.kernel.org with ESMTP id ; Thu, 22 Aug 2002 16:36:55 -0400 Date: Thu, 22 Aug 2002 22:39:42 +0200 From: Andries Brouwer To: Alan Cox Cc: Alan Stern , Dave Jones , James Simmons , linux-kernel@vger.kernel.org Subject: Re: Patch for PC keyboard driver's autorepeat-rate handling Message-ID: <20020822203942.GA5471@win.tue.nl> References: <1030037462.3090.1.camel@irongate.swansea.linux.org.uk> <20020822193743.GA5448@win.tue.nl> <1030047374.3161.60.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1030047374.3161.60.camel@irongate.swansea.linux.org.uk> User-Agent: Mutt/1.3.25i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1035 Lines: 25 On Thu, Aug 22, 2002 at 09:16:14PM +0100, Alan Cox wrote: > On Thu, 2002-08-22 at 20:37, Andries Brouwer wrote: > > What it does for KDKBDREP is conform the text of kd.h, and I think > > conform what m68k has done for years (but I've never seen the m68k patch). > > Alan Stern is entirely right that the current 2.4 kernels and the > > current kbdrate program have different ideas about what KDKBDREP does. > > XFree86 assumes the existing m68k behaviour from the base m68k tree A good pointer. And indeed, xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_io.c has code virtually identical to the kbdrate code (indeed, most likely taken from kbdrate). So, it seems the kernel has to change, and (although I have not checked it) Alan Stern's patch may be the right thing. Andries - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/