Date: Thu, 18 Nov 2004 21:37:54 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse Message-ID: <1100803074.1347.12.camel@localhost> In-Reply-To: <419CDD47.7000108@savvis.net> References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> <1100711659.47346.11.camel@localhost> <419B8C3A.6030003@savvis.net> <1100762798.1069.13.camel@localhost> <419CDD47.7000108@savvis.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =DE=D4, 18/11/2004 =D7 09:35 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4: > > I have another question about vkbd. > >=20 > > Is it really requires userland connector ? > > Probably it is not a bad idea to have kernel hook for vkbd also ? > >=20 > > I mean to make syscons ability to use in-kernel mixer of keyboard > > events. > >=20 > > So after that one can connect to that mixer some keyboards (usb, at, bt= ) >=20 > this was beaten to death on cvs-src, src-committers and cvs-all. please=20 > look for the huge discussion followed by my vkbd commit >=20 > Re: cvs commit: src/sys/dev/vkbd vkbd.c vkbd_var.h src/sys/modules/vkbd=20 > Makefile Looks like I should subscribe again to cvs-all, ok, will read. > > Frankly speaking I afraid case when with syscons pointing to vkbd DDB > > will be called, and what happens ?=20 >=20 > when people learn to read man pages? :) that is what they are for! :)=20 > vkbd(4) is just a way to feed key events into the kernel. key events=20 > have to be obtained somehow. in case of bluetooth all key codes passed=20 > through the rest of the stack. obviously bluetooth stack does not work=20 > when you are at ddb prompt. I do read man-page before. Actually, I don't want bt kbd work under dbb, But I don't want to loose at keyboard for DDB when I use bt keyboard for other (not DDB) input. This was my point. As I understand valid (and only) usage of vkbd is=20 1. start user-land software feeding vkbd with events (probably from different sources atkbd, ukbd, btkbd) 2. change syscons input to vkbd in this case any enter to DDB will stop keyboard processing at all. my idea was just have hook (probably ng) to be able shortcut vkbd and atkbd without user-land software.=20 > > Another option is to use special binding for DDB keyboard, but I did no= t > > like it. >=20 > i do not understand why this keeps poping up :( if it is required to=20 > support wireless keyboards under ddb then support must be impemented on=20 > lower lever, i.e. in bios. No, as I said before I just want be able to enter DDB with at keyboard when I have use bt keyboard. > max PS: I do not try to flame at all, just supply ideas. --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1100803074.1347.12.camel>