From owner-cvs-src@FreeBSD.ORG Wed Nov 17 01:17:33 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87A8016A4CE; Wed, 17 Nov 2004 01:17:33 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A63C343D54; Wed, 17 Nov 2004 01:17:32 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from wotan.home.paeps.cx (wotan.home.paeps.cx [IPv6:2001:838:37f:10:a00:20ff:fe9b:138c]) by gateway.nixsys.be (Postfix) with ESMTP id 8819676; Wed, 17 Nov 2004 02:17:31 +0100 (CET) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [IPv6:2001:838:37f:10:20a:e6ff:fe7d:c08]) by wotan.home.paeps.cx (Postfix) with ESMTP id 23BBA6197; Wed, 17 Nov 2004 02:17:31 +0100 (CET) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) by fasolt.home.paeps.cx (8.13.1/8.13.1) with ESMTP id iAH1HUem025778; Wed, 17 Nov 2004 02:17:30 +0100 (CET) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.13.1/8.13.1/Submit) id iAH1HR6v025777; Wed, 17 Nov 2004 02:17:27 +0100 (CET) (envelope-from philip) Date: Wed, 17 Nov 2004 02:17:27 +0100 From: Philip Paeps To: Brooks Davis Message-ID: <20041117011727.GJ24418@fasolt.home.paeps.cx> Mail-Followup-To: Brooks Davis , Maksim Yevmenkin , Poul-Henning Kamp , src-committers@freebsd.org, cvs-src@freebsd.org, cvs-all@freebsd.org References: <7302.1100627038@critter.freebsd.dk> <20041116180905.GA11906@odin.ac.hmc.edu> <20041116183549.GB11906@odin.ac.hmc.edu> <20041117002959.GH24418@fasolt.home.paeps.cx> <20041117004508.GA13628@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117004508.GA13628@odin.ac.hmc.edu> X-Date-in-Rome: ante diem XV Kalendas Decembres MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Organization: Happily Disorganized User-Agent: Mutt/1.5.6i cc: cvs-src@freebsd.org cc: Poul-Henning Kamp cc: src-committers@freebsd.org cc: cvs-all@freebsd.org cc: Maksim Yevmenkin Subject: Re: cvs commit: src/sys/dev/vkbd vkbd.c vkbd_var.h src/sys/modules/vkbd Makefile X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 01:17:33 -0000 On 2004-11-16 16:45:08 (-0800), Brooks Davis wrote: > On Wed, Nov 17, 2004 at 01:29:59AM +0100, Philip Paeps wrote: > > My idea would be to feed all 'input events' from hardware drivers into a > > pseudo-driver, serialize it, and send it on to the higher layers of the > > system. I see no real reason why we should't allow a user to start typing > > a command on one keyboard, finish it on another, and hit on a third. > > Why anyone would want to do that is beyond me, but it should be possible. > > That's basicly what I would like to see. I don't think we need to support > people hitting the accent key on one keyboard and then finishing typing on > the other, but we do need to support multiple keyboards if only because the > users expect it. I'd like to assume that the fundamental 'event' from a keyboard to reach the console is going to be a 'character'. Your example becomes even crazier to consider when you add a compose key into the equation. Likewise, I don't think it's a good idea to try to support people holding down modifiers on one keyboard and pressing keys on another. Alt on kbd0 followed by 'a' on kbd1 should probably translate to just 'a'. One problem we're going to run into quickly are keymaps. Currently, the maps are being handled by syscons (and pcvt). If we're going to let people have multiple keyboards, there will be those who will want to have a US-qwerty and a Belgian azerty side-by-side. Mapping keys will probably need to be handled by the driver (or the input system) on a per-device basis rather than by the console driver. That little headache has been fermenting at the back of my head since I first started thinking about writing an input layer. I've been ignoring it by sticking to the mice bits, but... Can any syscons gurus shed light on how we could go about convincing syscons to go from a 'keypress'-oriented approach to a 'character'-oriented approach? - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. BOFH Excuse #58: high pressure system failure