Date: Tue, 16 Nov 2004 10:28:37 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/vkbd vkbd.c vkbd_var.h src/sys/modules/vkbd Makefile Message-ID: <bb4a86c70411161028698cbae2@mail.gmail.com> In-Reply-To: <20041116180905.GA11906@odin.ac.hmc.edu> References: <bb4a86c7041116093262758595@mail.gmail.com> <7302.1100627038@critter.freebsd.dk> <bb4a86c704111610006d8283ed@mail.gmail.com> <20041116180905.GA11906@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Nov 2004 10:09:05 -0800, Brooks Davis <brooks@one-eyed-alien.net> wrote: > On Tue, Nov 16, 2004 at 10:00:24AM -0800, Maksim Yevmenkin wrote: > > > > On Tue, 16 Nov 2004 18:43:58 +0100, Poul-Henning Kamp > > <phk@phk.freebsd.dk> wrote: > > > In message <bb4a86c7041116093262758595@mail.gmail.com>, Maksim Yevmenkin writes > > > : > > > > > > > > > >On Tue, 16 Nov 2004 18:04:56 +0100, Poul-Henning Kamp > > > ><phk@phk.freebsd.dk> wrote: > > > >> In message <200411161659.iAGGxNiX087329@repoman.freebsd.org>, Maksim 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? > > 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. 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 :) 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? max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70411161028698cbae2>