Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 11 Dec 2002 19:53:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 11 Dec 2002 19:53:37 -0500 Received: from kweetal.tue.nl ([131.155.2.7]:45194 "EHLO kweetal.tue.nl") by vger.kernel.org with ESMTP id ; Wed, 11 Dec 2002 19:53:36 -0500 Date: Thu, 12 Dec 2002 02:01:16 +0100 From: Andries Brouwer To: Pavel Machek Cc: "H. Peter Anvin" , linux-kernel@vger.kernel.org Subject: Re: PATCH: Four function buttons on DELL Latitude X200 Message-ID: <20021212010116.GA10297@win.tue.nl> References:

<20021210213444.GA451@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021210213444.GA451@elf.ucw.cz> User-Agent: Mutt/1.3.25i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1088 Lines: 32 On Tue, Dec 10, 2002 at 10:34:44PM +0100, Pavel Machek wrote: > > The PC only has so many possible keycodes (with E0 and E1 it's still > > in the sub-300 range.) It won't fit within 128, but I would really > > like an algorithmic mapping from scancodes to keycodes so we don't > > continue to have this problem. > > > > For example, using a 16-bit keycode model: > > > > > > Scancode Keycode (binary) > > mxxxxxxx m0000000 0xxxxxxx > > E0 mxxxxxxx m0000000 1xxxxxxx > > E1 mxxxxxxx yyyyyyyy mxxxxxxx yyyyyyyy > > > > m = make/break bit > > Well, nothing prevents keyboard manufacturers from using 0xe2 as a > prefix, too. I think there are really *weird* keyboards out there. > > Pavel Indeed. See, for example, http://www.win.tue.nl/~aeb/linux/kbd/scancodes-2.html#ss2.18 for a keyboard that uses 0x80 as a prefix. - 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/