From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 17:37:15 2004 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAEC916A4CE for ; Thu, 18 Nov 2004 17:37:15 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CBBE43D1F for ; Thu, 18 Nov 2004 17:37:15 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iAIHZcIr009837; Thu, 18 Nov 2004 11:35:39 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 18 Nov 2004 11:35:31 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 18 Nov 2004 11:35:12 -0600 Message-ID: <419CDD47.7000108@savvis.net> Date: Thu, 18 Nov 2004 09:35:03 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vova@fbsd.ru References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> <1100711659.47346.11.camel@localhost> <419B8C3A.6030003@savvis.net> <1100762798.1069.13.camel@localhost> In-Reply-To: <1100762798.1069.13.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Nov 2004 17:35:12.0224 (UTC) FILETIME=[F4FC3600:01C4CD94] X-ECS-MailScanner: No virus is found cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:37:15 -0000 Vladimir, >>>Good news, is there any estimations or like ? >> >>no. life with 8 months old son can not be predicted easily :) (come to >>think about it life in general can not be predicted easily :) > > I know, frankly speaking I just want to be sure that there is some > activity in this direction, I, probably, will get any comments trying to > get it works myself. It is a bit challenging to buy unsupported hardware > but interesting anyway. i'm working on this, but very very slowly :) [...] > I have another question about vkbd. > > Is it really requires userland connector ? > Probably it is not a bad idea to have kernel hook for vkbd also ? > > I mean to make syscons ability to use in-kernel mixer of keyboard > events. > > So after that one can connect to that mixer some keyboards (usb, at, bt) this was beaten to death on cvs-src, src-committers and cvs-all. please look for the huge discussion followed by my vkbd commit Re: cvs commit: src/sys/dev/vkbd vkbd.c vkbd_var.h src/sys/modules/vkbd Makefile > Frankly speaking I afraid case when with syscons pointing to vkbd DDB > will be called, and what happens ? when people learn to read man pages? :) that is what they are for! :) vkbd(4) is just a way to feed key events into the kernel. key events have to be obtained somehow. in case of bluetooth all key codes passed through the rest of the stack. obviously bluetooth stack does not work when you are at ddb prompt. > Another option is to use special binding for DDB keyboard, but I did not > like it. i do not understand why this keeps poping up :( if it is required to support wireless keyboards under ddb then support must be impemented on lower lever, i.e. in bios. max