From owner-cvs-all@FreeBSD.ORG Tue Nov 16 22:00:14 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 4036316A4CE; Tue, 16 Nov 2004 22:00:14 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9A0C43D46; Tue, 16 Nov 2004 22:00:13 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAGLwPHN041132; Tue, 16 Nov 2004 14:58:25 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 16 Nov 2004 14:58:45 -0700 (MST) Message-Id: <20041116.145845.69991278.imp@bsdimp.com> To: marcel@xcllnt.net From: "M. Warner Losh" In-Reply-To: <20041116194720.GA90000@ns1.xcllnt.net> References: <419A4F8F.8000509@freebsd.org> <20041116194720.GA90000@ns1.xcllnt.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: src-committers@FreeBSD.org cc: brooks@one-eyed-alien.net cc: cvs-src@FreeBSD.org cc: scottl@FreeBSD.org cc: cvs-all@FreeBSD.org cc: phk@phk.freebsd.dk cc: maksim.yevmenkin@gmail.com 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 22:00:14 -0000 In message: <20041116194720.GA90000@ns1.xcllnt.net> Marcel Moolenaar writes: : 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. If we make it so that vkbd is also useful from whthin the kernel, then we can use it to implement many different things. The code doesn't look that far from this ideal, although I'm not sure what the right API is for doing it. If bluetooth keyboards do become common place, we'll have to move bluetooth into the kernel to support them in single user mode or in ddb. Warner