From owner-cvs-src@FreeBSD.ORG Wed Nov 17 02:02:27 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 559C416A4CE; Wed, 17 Nov 2004 02:02:27 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9D4F43D53; Wed, 17 Nov 2004 02:02:26 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iAH22PEd091991; Tue, 16 Nov 2004 18:02:25 -0800 (PST) (envelope-from marcel@xcllnt.net) In-Reply-To: <20041117011727.GJ24418@fasolt.home.paeps.cx> 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> <20041117011727.GJ24418@fasolt.home.paeps.cx> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Tue, 16 Nov 2004 18:02:24 -0800 To: Philip Paeps X-Mailer: Apple Mail (2.619) cc: src-committers@FreeBSD.org cc: Brooks Davis cc: cvs-src@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Poul-Henning Kamp 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 02:02:27 -0000 On Nov 16, 2004, at 5:17 PM, Philip Paeps wrote: > 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? I'm no guru in this regard, but it's probably best to take it one step at a time. Add a mux and let syscons think there's just 1 keyboard. After that it's a good idea to come up with the abstractions and the layering and move the keymap code there. The same can and should probably done in the opposite direction. So that you can have the output go to multiple displays with a choice of TE. As for the abstractions and layering, think GEOM without the OO obfuscation. A procedural (KOBJ based) interface for the most elementary functions would probably do it. It's probably also a good idea to have the keymap layer send off special keys to devd(8)... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net