From owner-freebsd-bluetooth@FreeBSD.ORG Fri Dec 17 18:26:27 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 7A29C16A4CE for ; Fri, 17 Dec 2004 18:26:27 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05C8243D54 for ; Fri, 17 Dec 2004 18:26:27 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iBHIPJBT007278; Fri, 17 Dec 2004 12:25:19 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 17 Dec 2004 12:24:57 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 17 Dec 2004 12:24:50 -0600 Message-ID: <41C32471.2050805@savvis.net> Date: Fri, 17 Dec 2004 10:24:49 -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> <419B9EF8.2090401@savvis.net> <1103269957.974.7.camel@localhost> In-Reply-To: <1103269957.974.7.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Dec 2004 18:24:50.0876 (UTC) FILETIME=[B2612FC0:01C4E465] 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: Fri, 17 Dec 2004 18:26:27 -0000 Vladimir, > I have found your message: > ====================================== > you need to have Bluetooth HID (Human Interface Device) support. someone > wrote me an e-mail a while ago asking the same question. i tried to > explain Bluetooth HID and how it works. its not a rocket science - you > just need write a daemon that opens a couple of L2CAP connection to the > mouse and read bytes from it. then you feed these bytes > into /dev/console via ioctl(2) to move actual mouse pointer. i'm not > sure if this person working on this. > ====================================== > > So I am ready to try it, Can you resend me your explanations ? good :) > Also, I think, it is better to provide usual /dev/*msX interface for > moused ? why? > It looks like I need to write ng node which will connect to l2cap node > one side and create /dev/btmsX on another side ? well, actually its much simpler :) most of the work already was done. take a look at /usr/src/usr.sbin/bluetooth/{bthidcontrol,bthidd}. these are not yet connected to the build, but you should be able to compile and run them. bthidcontrol(8) is a utility that can query bluetooth hid devices and create configuration for bthidd(8). % nroff -man bthidcontrol.8 | less -- for more information bthidd(8) is a bluetooth hid daemon (incomplete but mouse should work). it will read configuration created by bthidcontrol(8) and talk to bluetooth hid devices. whats needs to be done: 1) finish and test bthidd(8) and vkbd(4) integration (bluetooth keyboard support). i've done most of it, but was never able to finish and test it :( 2) better handling of bluetooth mouse events, i.e. detect double clicks etc. and send appropriate ioctl(2) to /dev/console. double clicks etc. will work in X, but not in the text mode. thanks, max