From owner-cvs-all@FreeBSD.ORG Tue Nov 16 19:47:21 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6049B16A4CE; Tue, 16 Nov 2004 19:47:21 +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 BEF0743D31; Tue, 16 Nov 2004 19:47:20 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iAGJlKRt090094; Tue, 16 Nov 2004 11:47:20 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iAGJlKq6090093; Tue, 16 Nov 2004 11:47:20 -0800 (PST) (envelope-from marcel) Date: Tue, 16 Nov 2004 11:47:20 -0800 From: Marcel Moolenaar To: Maksim Yevmenkin Message-ID: <20041116194720.GA90000@ns1.xcllnt.net> References: <7302.1100627038@critter.freebsd.dk> <20041116180905.GA11906@odin.ac.hmc.edu> <419A492A.7020602@freebsd.org> <419A4F8F.8000509@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: src-committers@FreeBSD.org cc: Brooks Davis cc: cvs-src@FreeBSD.org cc: Scott Long cc: cvs-all@FreeBSD.org cc: Poul-Henning Kamp Subject: Re: cvs commit: src/sys/dev/vkbd vkbd.c vkbd_var.h src/sys/modules/vkbd Makefile X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 19:47:21 -0000 On Tue, Nov 16, 2004 at 11:17:18AM -0800, Maksim Yevmenkin wrote: > > > there is no chance that the BT device could be needed for DDB or > > single-user mode then I guess that your driver is a good thing, though > > the 'vkbd' name is a bit misleading since it really only applies to BT. > > But if you're interested in working with Brooks on a more unified > > abstraction, please don't let me stop you =-) > > bluetooth keyboard definitely not needed in ddb and single mode (imo). I very strongly disagree with this. In fact, it's this sentiment that created the PS/2 vs USB keyboard problem for which we need a mux. We need to treat a keyboard as a keyboard because a keyboard is a keyboard. Some keyboards lend themselves more easily for low-level access due to the primitive nature of how one talks to the keyboard, but I think it's a mistake to treat a PS/2 keyboard different from any other keyboard simply because the interface is primitive. It's much more productive to try to get USB, Bluetooth and firefire to work as soon as possible during boot so that devices there can be used as early as PS/2 or legacy PC devices. The world is changing and we have syscons(4) to show what happens if you don't keep up and make a serious attempt at providing the right abstractions and interfaces to account for the new world order. Other than that. I think vkbd(4) can stay. Between no support and partial or imperfect support, we might as well keep the imperfect support until we're done perfecting things. With vkbd(4), one can actually use bluetooth in the common case. I think that's a big win on its own. Just my take on this, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net