From owner-cvs-all@FreeBSD.ORG Tue Nov 16 18:34:50 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 F136716A4CE; Tue, 16 Nov 2004 18:34:50 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA92143D5C; Tue, 16 Nov 2004 18:34:50 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAGIZnsw024424; Tue, 16 Nov 2004 10:35:49 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAGIZnmI024423; Tue, 16 Nov 2004 10:35:49 -0800 Date: Tue, 16 Nov 2004 10:35:49 -0800 From: Brooks Davis To: Maksim Yevmenkin Message-ID: <20041116183549.GB11906@odin.ac.hmc.edu> References: <7302.1100627038@critter.freebsd.dk> <20041116180905.GA11906@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hHWLQfXTYDoKhP50" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: Brooks Davis cc: cvs-src@freebsd.org cc: Poul-Henning Kamp cc: src-committers@freebsd.org cc: cvs-all@freebsd.org 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 18:34:51 -0000 --hHWLQfXTYDoKhP50 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2004 at 10:28:37AM -0800, Maksim Yevmenkin wrote: > On Tue, 16 Nov 2004 10:09:05 -0800, Brooks Davis > wrote: > > On Tue, Nov 16, 2004 at 10:00:24AM -0800, Maksim Yevmenkin wrote: > >=20 > >=20 > > > On Tue, 16 Nov 2004 18:43:58 +0100, Poul-Henning Kamp > > > wrote: > > > > In message , Maksim Yevm= enkin writes > > > > : > > > > > > > > > > > > >On Tue, 16 Nov 2004 18:04:56 +0100, Poul-Henning Kamp > > > > > wrote: > > > > >> In message <200411161659.iAGGxNiX087329@repoman.freebsd.org>, Ma= ksim Yevmenkin > > > > >> writes: > > > > >> > > > > >> > > > > >> >emax 2004-11-16 16:59:23 UTC > > > > >> > > > > > >> > FreeBSD src repository > > > > >> > > > > > >> > Added files: > > > > >> > sys/dev/vkbd vkbd.c vkbd_var.h > > > > >> > sys/modules/vkbd Makefile > > > > >> > Log: > > > > >> > Add virtual AT keyboard driver vkbd(4). > > > > >> > Not yet connected to the build. > > > > >> > > > > >> I thought we had one of those already ? > > > > > > > > > >when? where? did i miss it? > > > > > > > > sys/dev/kbd (and various MD stuff all over the place) ? > > > > > > perhaps i'm missing something here. the idea behind vkdb(4) is to > > > create a keyboard without a keyboard. that is to create a keyboard > > > that accepts scan codes from userspace and not from real hardware. > > > that is what vkbd(4) does. it creates a new keyboard (just like > > > ukbd(4) etc) and register it with kbd(4). basically what i want to do > > > is to obtain scan codes from bluetooth keyboard and then feed them > > > into the kernel. the idea is that bluetooth hid daemon looks for the > > > bluetooth keyboard, connects to it, switches active keyboard to > > > vkbd(4) , reads scan codes and feeds them into vkbd(4). when bluetooth > > > keyboard is gone the bluetooth hid daemon switches back to wired > > > keyboard. i do not think i can do it with kdb(4), can i? > >=20 > > Have you considered making the virtual keyboard an in kernel client of > > it's child keyboard(s)? If you don't do this, you can't use the virtual > > keyboard in single user mode or in the debugger. >=20 > vkbd(4) man page says that it will not work with ddb(4) :) and (at > this point) i'm not sure whether this is required. in case of > bluetooth hid all scan codes have to passed through bluetooth stack. i > definitely do not want to use bluetooth keyboard in ddb(4) or in > single user mode :) It's not require for bluetooth, but its is a requirement for USB. There are actually two parts to this. You need to be able to function without a daemon as in single user mode or sysinstall. You also need to be able to work in the polling mode the debugger uses. > i think i see where you are going. you are probably thinking about > some sort of lights-out management where you use only network > connection to control box remotely, a-la pc-weasel and eric cards. am > i close? I'm primairly intrested in solving the problem of machines with a AT keyboard controller (which currently attached non-existant keyboards to allow hot-pluging) and a USB keyboard. The second case I'm intrested in is a LOM card. In one case I've seen one present the keyboard as a USB keyboard which means you need to support two USB keyboards. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --hHWLQfXTYDoKhP50 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBmkiFXY6L6fI4GtQRAhI4AJwPG2cjXamJnzhrW5ruAxLuXRctwACgvQDh q11HRAjWWVsmWWpsEv84CZI= =9QIU -----END PGP SIGNATURE----- --hHWLQfXTYDoKhP50--