From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 15 21:10:17 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 CBA4016A4CE for ; Mon, 15 Nov 2004 21:10:17 +0000 (GMT) Received: from vbook.fbsd.ru (user142.hovrino.net [82.179.232.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6377643D45 for ; Mon, 15 Nov 2004 21:10:16 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTo6p-0000Nz-4i for bluetooth@freebsd.org; Tue, 16 Nov 2004 00:09:59 +0300 From: Vladimir Grebenschikov To: bluetooth@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Tue, 16 Nov 2004 00:09:58 +0300 Message-Id: <1100552998.1098.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Subject: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 21:10:17 -0000 Hi Have anybody managed to get bluetooth mouse or/and keyboard work with FreeBSD ? If yes what models/manufacturers supported ? Thank you for answer. -- Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 15 22:25:07 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 DE22316A4D0 for ; Mon, 15 Nov 2004 22:25:07 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BD9343D1D for ; Mon, 15 Nov 2004 22:25:07 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id iAFMOuYs008100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 15 Nov 2004 14:25:03 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id iAFMOtdw008098 for freebsd-bluetooth@freebsd.org; Mon, 15 Nov 2004 14:24:55 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Mon, 15 Nov 2004 14:24:55 -0800 From: "Loren M. Lang" To: freebsd-bluetooth@freebsd.org Message-ID: <20041115222455.GA5468@alzatex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C Subject: Bluetooth Keyboard 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: Mon, 15 Nov 2004 22:25:08 -0000 So... how is the bluetooth hid driver coming along that I heard was being worked on back in January. He said he was making good progress, but I still don't see any program to enable hid support in FreeBSD 5.3. My bt keyboard shows up as a bt device, but that's about it. --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C =20 From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 16:58:55 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 F40C816A4CE for ; Wed, 17 Nov 2004 16:58:54 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B24E43D31 for ; Wed, 17 Nov 2004 16:58:54 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iAHGwHw1018988; Wed, 17 Nov 2004 10:58:17 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 10:58:12 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 10:58:00 -0600 Message-ID: <419B8314.3080306@savvis.net> Date: Wed, 17 Nov 2004 08:57:56 -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: "Loren M. Lang" References: <20041115222455.GA5468@alzatex.com> In-Reply-To: <20041115222455.GA5468@alzatex.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 16:58:00.0607 (UTC) FILETIME=[986CBAF0:01C4CCC6] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Keyboard 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: Wed, 17 Nov 2004 16:58:55 -0000 Loren M. Lang wrote: > So... how is the bluetooth hid driver coming along that I heard was > being worked on back in January. He said he was making good progress, > but I still don't see any program to enable hid support in FreeBSD 5.3. > My bt keyboard shows up as a bt device, but that's about it. it is coming along. i finally started to commit bits and pieces (i.e. vkbd(4)) max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 16:59:17 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 8D8C016A4CE for ; Wed, 17 Nov 2004 16:59:17 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2791943D2F for ; Wed, 17 Nov 2004 16:59:17 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iAHGx6w1019072; Wed, 17 Nov 2004 10:59:06 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 10:59:02 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 10:59:03 -0600 Message-ID: <419B8353.7040908@savvis.net> Date: Wed, 17 Nov 2004 08:58:59 -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> In-Reply-To: <1100552998.1098.5.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 16:59:03.0759 (UTC) FILETIME=[BE10F5F0:01C4CCC6] 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: Wed, 17 Nov 2004 16:59:17 -0000 Vladimir Grebenschikov wrote: > Hi > > Have anybody managed to get bluetooth mouse or/and keyboard work with not yet > FreeBSD ? If yes what models/manufacturers supported ? any model that conforms to bluetooth hid spec will be supported. max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 17:14:20 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 BDDA916A4CE for ; Wed, 17 Nov 2004 17:14:20 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61B3C43D46 for ; Wed, 17 Nov 2004 17:14:20 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CUTNr-000046-88; Wed, 17 Nov 2004 20:14:19 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: <419B8353.7040908@savvis.net> References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Wed, 17 Nov 2004 20:14:19 +0300 Message-Id: <1100711659.47346.11.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 17:14:20 -0000 =F7 =D3=D2, 17/11/2004 =D7 08:58 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4: Hi again > > Have anybody managed to get bluetooth mouse or/and keyboard work with >=20 > not yet Good news, is there any estimations or like ? =20 I am going to get such mouse but if it will not be supported for years it has no sense. > max --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 17:37:42 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 E8B6C16A4CE for ; Wed, 17 Nov 2004 17:37:42 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99BE643D46 for ; Wed, 17 Nov 2004 17:37:42 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iAHHbF7g022489; Wed, 17 Nov 2004 11:37:15 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 11:37:10 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 11:37:00 -0600 Message-ID: <419B8C3A.6030003@savvis.net> Date: Wed, 17 Nov 2004 09:36:58 -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> In-Reply-To: <1100711659.47346.11.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 17:37:00.0282 (UTC) FILETIME=[0AFACDA0:01C4CCCC] 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: Wed, 17 Nov 2004 17:37:43 -0000 >>> Have anybody managed to get bluetooth mouse or/and keyboard work >>> with >> >> not yet > > 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 am going to get such mouse but if it will not be supported for > years it has no sense. you can always write support yourself :) max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 18:47:45 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 50B5916A4CE for ; Wed, 17 Nov 2004 18:47:45 +0000 (GMT) Received: from smtp-vbr1.xs4all.nl (smtp-vbr1.xs4all.nl [194.109.24.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC10643D2F for ; Wed, 17 Nov 2004 18:47:44 +0000 (GMT) (envelope-from miketmp@xs4all.nl) Received: from mail.xs4all.nl (a80-126-82-35.adsl.xs4all.nl [80.126.82.35]) by smtp-vbr1.xs4all.nl (8.12.11/8.12.11) with ESMTP id iAHIlNLa028919 for ; Wed, 17 Nov 2004 19:47:38 +0100 (CET) (envelope-from miketmp@xs4all.nl) To: bluetooth@freebsd.org References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> Message-ID: Date: Wed, 17 Nov 2004 19:47:19 +0100 From: "Mike Crosland" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <419B8353.7040908@savvis.net> User-Agent: Opera M2/7.54 (Win32, build 3865) X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: miketmp@xs4all.nl List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 18:47:45 -0000 My current setup allows me to use my Logitech di Novo keyboard/mouse on my dual-boot machine. FreeBSD just sees it as being a usb hub. However I did have to do some patching and a kernel rebuild to do it. Also FreeBSD doesn't recognise the bt hub, which means if you want to link to other bt devices you need to have a seperate dongle. What would be decidedly cool was if the usb bt chip AND extra dongle(s) ie multiple devices could be recognised, in much the same way that the system can handle several network cards. Mike PS Max - congratulations to your enlarging user base - er I mean family :) On Wed, 17 Nov 2004 08:58:59 -0800, Maksim Yevmenkin wrote: > Vladimir Grebenschikov wrote: >> Hi >> Have anybody managed to get bluetooth mouse or/and keyboard work with > > not yet > >> FreeBSD ? If yes what models/manufacturers supported ? > > any model that conforms to bluetooth hid spec will be supported. > > max > > > > > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to > "freebsd-bluetooth-unsubscribe@freebsd.org" > From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 18:57:19 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 ED0EB16A4CE for ; Wed, 17 Nov 2004 18:57:19 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8143D43D55 for ; Wed, 17 Nov 2004 18:57:19 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iAHIvFJn029100; Wed, 17 Nov 2004 12:57:15 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 12:57:09 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 12:56:47 -0600 Message-ID: <419B9EF8.2090401@savvis.net> Date: Wed, 17 Nov 2004 10:56:56 -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: miketmp@xs4all.nl References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 18:56:47.0768 (UTC) FILETIME=[308B3180:01C4CCD7] 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: Wed, 17 Nov 2004 18:57:20 -0000 Mike Crosland wrote: > My current setup allows me to use my Logitech di Novo keyboard/mouse on > my dual-boot machine. FreeBSD just sees it as being a usb hub. However > I did have to do some patching and a kernel rebuild to do it. Also > FreeBSD doesn't recognise the bt hub, which means if you want to link > to other bt devices you need to have a seperate dongle. this is so called 'bluetooth hid proxy' feature of CSR BlueCore chipset. basically when you activate 'hid proxy' bluetooth dongle start acting as usb hub and pretends that is has usb keyboard and mouse plugged in. this is just a compatibility hack, so one can use bluetooth keyboard/mouse on a systems that do not support bluetooth. note that os must have support for usb. > What would be decidedly cool was if the usb bt chip AND extra > dongle(s) ie multiple devices could be recognised, in much the same way > that the system can handle several network cards. it is possible to turn 'hid proxy' feature off. in this case you have regular bluetooth dongle. if os supports bluetooth hid then use can use then same dongle to talk to your keyboard, mount, cell phone etc. there is only one limitation you can have up to 8 active bluetooth connection s at a time. keyboard and mouse will use one each, so you still can have up to 6 other bluetooth devices. > PS Max - congratulations to your enlarging user base - er I mean family > :) thanks! max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 19:23:26 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 B726816A4CE for ; Wed, 17 Nov 2004 19:23:26 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DF7D43D55 for ; Wed, 17 Nov 2004 19:23:25 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id iAHJNBYs030468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 11:23:14 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id iAHJNARn030466; Wed, 17 Nov 2004 11:23:10 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Wed, 17 Nov 2004 11:23:10 -0800 From: "Loren M. Lang" To: Maksim Yevmenkin Message-ID: <20041117192310.GA30137@alzatex.com> References: <20041115222455.GA5468@alzatex.com> <419B8314.3080306@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <419B8314.3080306@savvis.net> User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Keyboard 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: Wed, 17 Nov 2004 19:23:26 -0000 On Wed, Nov 17, 2004 at 08:57:56AM -0800, Maksim Yevmenkin wrote: > Loren M. Lang wrote: > >So... how is the bluetooth hid driver coming along that I heard was > >being worked on back in January. He said he was making good progress, > >but I still don't see any program to enable hid support in FreeBSD 5.3. > >My bt keyboard shows up as a bt device, but that's about it. >=20 > it is coming along. i finally started to commit bits and pieces (i.e.=20 > vkbd(4)) I actually ran across vkbd, it looks like a generic way to insert keyboard events into the kernel, but not specific to any technology like bluetooth. I'm assuming you also have a user-land daemon that uses sockets to talk on bluetooth then pass the event to vkbd. Is there a place to find the userland daemon source at the moment or do you just have a private copy? I would like to help with this project since I've had my bluetooth keyboard sitting on the shelf for months waiting for support in freebsd and I have been doing some other work in bluetooth recently. >=20 > max --=20 I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C =20 From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 19:24:45 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 182E516A4CE for ; Wed, 17 Nov 2004 19:24:45 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0080443D49 for ; Wed, 17 Nov 2004 19:24:44 +0000 (GMT) (envelope-from hvalentim@gmx.net) Received: (qmail 10018 invoked by uid 65534); 17 Nov 2004 19:24:40 -0000 Received: from unknown (EHLO robur.agsoft) (81.193.150.184) by mail.gmx.net (mp010) with SMTP; 17 Nov 2004 20:24:40 +0100 X-Authenticated: #13992909 From: "Hugo D. Valentim" Date: Wed, 17 Nov 2004 19:24:20 +0000 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Disposition: inline To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411171924.20835.hvalentim@gmx.net> Subject: dongle recognized as keyboard (?) 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: Wed, 17 Nov 2004 19:24:45 -0000 Hi all, My bluetooth dongle is automatically being recognized has a keyboard (a /dev/ukbd0 is created but NO /dev/ubt0), whereas I want to use it to connect to a mobile phone (see log bellow). This is a real nag since I am left without keyboard and have no way to type whenever I plug the dongle. I am using 5.3-release. In 5.2.1 this did not happen. Any ideas, please? Am I am missing something? Thanks, Hugo I have two USB plugs (Compaq laptop): one has a Tecom BT3033A dongle, the other has nothing: uhci0: port 0x1800-0x181f irq 5 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Broadcom product 0x3535, class 9/0, rev 2.00/1.00, addr 2 uhub1: 3 ports with 0 removable, bus powered ubt0: Broadcom Corp Bluetooth Transceiver, rev 1.10/1.00, addr 3 ubt0: Broadcom Corp Bluetooth Transceiver, rev 1.10/1.00, addr 3 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 ukbd0: Broadcom product 0x0099, rev 1.10/1.00, addr 4, iclass 3/1 kbd1 at ukbd0 ums0: Broadcom product 0x0097, rev 1.10/1.00, addr 5, iclass 3/1 ums0: 3 buttons From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 19:55:17 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 60EFD16A4CE for ; Wed, 17 Nov 2004 19:55:17 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F46643D41 for ; Wed, 17 Nov 2004 19:55:17 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iAHJt1Jn001227; Wed, 17 Nov 2004 13:55:01 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 13:54:58 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 13:54:47 -0600 Message-ID: <419BAC86.9040706@savvis.net> Date: Wed, 17 Nov 2004 11:54:46 -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: "Hugo D. Valentim" References: <200411171924.20835.hvalentim@gmx.net> In-Reply-To: <200411171924.20835.hvalentim@gmx.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 19:54:47.0893 (UTC) FILETIME=[4ADC2050:01C4CCDF] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: dongle recognized as keyboard (?) 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: Wed, 17 Nov 2004 19:55:17 -0000 Hi, > My bluetooth dongle is automatically being recognized has a keyboard > (a /dev/ukbd0 is created but NO /dev/ubt0), whereas I want to use > it to connect to a mobile phone (see log bellow). > > This is a real nag since I am left without keyboard and have no way > to type whenever I plug the dongle. > > I am using 5.3-release. In 5.2.1 this did not happen. > > Any ideas, please? Am I am missing something? well, for once adjust your /etc/devd.conf (or /etc/usbd.conf if you are running usbd(8)) to NOT activate usb keyboard by default. you should be looking for lines like # When a USB keyboard arrives, attach it as the console keyboard attach 100 { device-name "ukbd0"; action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 < /dev/console"; }; detach 100 { device-name "ukbd0"; action "kbdcontrol -k /dev/kbd0 < /dev/console"; }; same for the usb mouse # The entry below starts moused when a mouse is plugged in. Moused # stops automatically (actually it bombs :) when the device disappears. device "Mouse" devname "ums[0-9]+" attach "/etc/rc.d/moused start ${DEVNAME}" > I have two USB plugs (Compaq laptop): one has a Tecom BT3033A dongle, > the other has nothing: > > uhci0: port 0x1800-0x181f irq 5 at device > 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: > on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, > rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ok that is hub on motherboard > uhub1: Broadcom product 0x3535, class 9/0, rev 2.00/1.00, addr 2 > uhub1: 3 ports with 0 removable, bus powered ubt0: Broadcom Corp ok that is hub(!) on your dongle > Bluetooth Transceiver, rev 1.10/1.00, addr 3 > ubt0: Broadcom Corp Bluetooth Transceiver, rev 1.10/1.00, addr 3 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 > ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 ok that looks like normal bluetooth dongle > ukbd0: Broadcom product 0x0099, rev 1.10/1.00, addr 4, iclass 3/1 kbd1 at ukbd0 whoa! that looks like usb keyboard! > ums0: Broadcom product 0x0097, rev 1.10/1.00, addr 5, iclass 3/1 ums0: 3 buttons whoa! that looks like usb mouse! well, i got to have this specimen in my lab. from what i can see the dongle gives 3 (!) interfaces. 1) bluetooth usb dongle (ubt0) 2) bluetooth keyboard (ukbd0) 3) bluetooth mouse (ums0) all 3 appears active at the same time. this dongle has 'bluetooh hid proxy' feature active by default *and* at the same time is still accessible via hci. i've never seen anything like this before. from what i can see all 3 interfaces are recognized, so everything should work. and, btw there is no /dev/ubt0, so dont worry about it. try to run # ngctl li and you should see ubt0 netgraph node. if you do then just run # rc.bluetooth start ubt0 everything should be working. your keyboard is switched to ukbd0 (by default) and that is why you have to change /etc/devd.conf and/or /etc/usbd.conf. if you had bluetooth keyboard then it would work just like usb keyboard. hope that helps, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 20:01:25 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 6CDDA16A4CE for ; Wed, 17 Nov 2004 20:01:25 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29DED43D49 for ; Wed, 17 Nov 2004 20:01:25 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iAHK10Jn001690; Wed, 17 Nov 2004 14:01:00 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 14:00:57 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 14:00:53 -0600 Message-ID: <419BADF3.5060704@savvis.net> Date: Wed, 17 Nov 2004 12:00:51 -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: "Loren M. Lang" References: <20041115222455.GA5468@alzatex.com> <419B8314.3080306@savvis.net> <20041117192310.GA30137@alzatex.com> In-Reply-To: <20041117192310.GA30137@alzatex.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 20:00:53.0460 (UTC) FILETIME=[24C13940:01C4CCE0] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Keyboard 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: Wed, 17 Nov 2004 20:01:25 -0000 Loren M. Lang wrote: > On Wed, Nov 17, 2004 at 08:57:56AM -0800, Maksim Yevmenkin wrote: > >>Loren M. Lang wrote: >> >>>So... how is the bluetooth hid driver coming along that I heard was >>>being worked on back in January. He said he was making good progress, >>>but I still don't see any program to enable hid support in FreeBSD 5.3. >>>My bt keyboard shows up as a bt device, but that's about it. >> >>it is coming along. i finally started to commit bits and pieces (i.e. >>vkbd(4)) > > I actually ran across vkbd, it looks like a generic way to insert > keyboard events into the kernel, but not specific to any technology like > bluetooth. I'm assuming you also have a user-land daemon that uses > sockets to talk on bluetooth then pass the event to vkbd. Is there a correct > place to find the userland daemon source at the moment or do you just > have a private copy? there is somewhat old version is in cvs, but it is not connected to the build /usr/src/usr.sbin/bluetooth/bthidcontrol /usr/src/usr.sbin/bluetooth/bthidd you can read the code and try to get the idea. bthidcontrol(8) should just work. bthidd(8) has very simple support for bluetooth mouse and no support for the keyboard. > I would like to help with this project since I've had my bluetooth > keyboard sitting on the shelf for months waiting for support in freebsd > and I have been doing some other work in bluetooth recently. sure. i'll be glad to review and commit your patches. max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 21:38:02 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 E0AD116A4CE for ; Wed, 17 Nov 2004 21:38:02 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3D9343D2F for ; Wed, 17 Nov 2004 21:38:01 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id iAHLboYs002349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 13:37:53 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id iAHLbnuD002346; Wed, 17 Nov 2004 13:37:49 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Wed, 17 Nov 2004 13:37:49 -0800 From: "Loren M. Lang" To: Maksim Yevmenkin Message-ID: <20041117213749.GB30137@alzatex.com> References: <20041115222455.GA5468@alzatex.com> <419B8314.3080306@savvis.net> <20041117192310.GA30137@alzatex.com> <419BADF3.5060704@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419BADF3.5060704@savvis.net> User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Keyboard 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: Wed, 17 Nov 2004 21:38:03 -0000 On Wed, Nov 17, 2004 at 12:00:51PM -0800, Maksim Yevmenkin wrote: > Loren M. Lang wrote: > >On Wed, Nov 17, 2004 at 08:57:56AM -0800, Maksim Yevmenkin wrote: > > > >>Loren M. Lang wrote: > >> > >>>So... how is the bluetooth hid driver coming along that I heard was > >>>being worked on back in January. He said he was making good progress, > >>>but I still don't see any program to enable hid support in FreeBSD 5.3. > >>>My bt keyboard shows up as a bt device, but that's about it. > >> > >>it is coming along. i finally started to commit bits and pieces (i.e. > >>vkbd(4)) > > > >I actually ran across vkbd, it looks like a generic way to insert > >keyboard events into the kernel, but not specific to any technology like > >bluetooth. I'm assuming you also have a user-land daemon that uses > >sockets to talk on bluetooth then pass the event to vkbd. Is there a > > correct > > >place to find the userland daemon source at the moment or do you just > >have a private copy? > > there is somewhat old version is in cvs, but it is not connected to the > build > > /usr/src/usr.sbin/bluetooth/bthidcontrol > /usr/src/usr.sbin/bluetooth/bthidd > > you can read the code and try to get the idea. bthidcontrol(8) should > just work. bthidd(8) has very simple support for bluetooth mouse and no > support for the keyboard. I tried compiling both bthidd and bthidcontrol, but they are complaining about a missing header and a missing type, report_desc_t. I'm assuming report_desc_t is supposed to be defined in libusbhid.h, but that does not seem to be on my system anywhere according to locate. Is that in some port or just an old file since I'd think nothing under /usr/src should depend on a port. > > >I would like to help with this project since I've had my bluetooth > >keyboard sitting on the shelf for months waiting for support in freebsd > >and I have been doing some other work in bluetooth recently. > > sure. i'll be glad to review and commit your patches. How old is the cvs version, I'd hate to be fixing old bugs or writing code that is no longer useful. > > max -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C From owner-freebsd-bluetooth@FreeBSD.ORG Wed Nov 17 21:51:33 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 AEF3316A4CE for ; Wed, 17 Nov 2004 21:51:33 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F97D43D2D for ; Wed, 17 Nov 2004 21:51:33 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iAHLpRJn010033; Wed, 17 Nov 2004 15:51:27 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 15:51:20 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew03.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 17 Nov 2004 15:51:16 -0600 Message-ID: <419BC7D6.1060700@savvis.net> Date: Wed, 17 Nov 2004 13:51:18 -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: "Loren M. Lang" References: <20041115222455.GA5468@alzatex.com> <419B8314.3080306@savvis.net> <20041117192310.GA30137@alzatex.com> <419BADF3.5060704@savvis.net> <20041117213749.GB30137@alzatex.com> In-Reply-To: <20041117213749.GB30137@alzatex.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 17 Nov 2004 21:51:16.0348 (UTC) FILETIME=[904DBBC0:01C4CCEF] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: Bluetooth Keyboard 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: Wed, 17 Nov 2004 21:51:33 -0000 >>>>>So... how is the bluetooth hid driver coming along that I heard was >>>>>being worked on back in January. He said he was making good progress, >>>>>but I still don't see any program to enable hid support in FreeBSD 5.3. >>>>>My bt keyboard shows up as a bt device, but that's about it. >>>> >>>>it is coming along. i finally started to commit bits and pieces (i.e. >>>>vkbd(4)) >>> >>>I actually ran across vkbd, it looks like a generic way to insert >>>keyboard events into the kernel, but not specific to any technology like >>>bluetooth. I'm assuming you also have a user-land daemon that uses >>>sockets to talk on bluetooth then pass the event to vkbd. Is there a >> >>correct >> >>>place to find the userland daemon source at the moment or do you just >>>have a private copy? >> >>there is somewhat old version is in cvs, but it is not connected to the >>build >> >>/usr/src/usr.sbin/bluetooth/bthidcontrol >>/usr/src/usr.sbin/bluetooth/bthidd >> >>you can read the code and try to get the idea. bthidcontrol(8) should >>just work. bthidd(8) has very simple support for bluetooth mouse and no >>support for the keyboard. > > I tried compiling both bthidd and bthidcontrol, but they are complaining > about a missing header and a missing type, report_desc_t. I'm assuming > report_desc_t is supposed to be defined in libusbhid.h, but that does > not seem to be on my system anywhere according to locate. Is that in > some port or just an old file since I'd think nothing under /usr/src > should depend on a port. hmmm, it appears that libusbhid.h was renamed to usbhid.h. no bthidd does not depend on any port. just on libusbhid (see usbhid(3) for details). just apply this patch in /usr/src/usr.sbin/bluetooth/bthidd --- parser.y Fri Apr 9 17:18:00 2004 +++ /tmp/parser.y Wed Nov 17 13:49:04 2004 @@ -33,10 +33,10 @@ #include #include #include -#include #include #include #include +#include #include >>>I would like to help with this project since I've had my bluetooth >>>keyboard sitting on the shelf for months waiting for support in freebsd >>>and I have been doing some other work in bluetooth recently. >> >>sure. i'll be glad to review and commit your patches. > > How old is the cvs version, I'd hate to be fixing old bugs or writing > code that is no longer useful. well, its old. give me a couple of days and i will update the bluetooth hid stuff in cvs. in the mean time the current code is a good starting reference. max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 04:30:52 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 314ED16A4D5 for ; Thu, 18 Nov 2004 04:30:52 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D6C1243D41 for ; Thu, 18 Nov 2004 04:30:50 +0000 (GMT) (envelope-from hvalentim@gmx.net) Received: (qmail 10726 invoked by uid 65534); 18 Nov 2004 04:30:48 -0000 Received: from unknown (EHLO robur.agsoft) (81.193.150.184) by mail.gmx.net (mp009) with SMTP; 18 Nov 2004 05:30:48 +0100 X-Authenticated: #13992909 From: "Hugo D. Valentim" To: freebsd-bluetooth@freebsd.org Date: Thu, 18 Nov 2004 04:30:27 +0000 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200411180430.27711.hvalentim@gmx.net> Subject: TECOM BT3033A. Problem Solved! 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 04:30:52 -0000 Recapitulating the problem and the solution, for future reference. THE PROBLEM: I first complained because when I plugged my bluetooth dongle (wishing to=20 connect to a mobile phone) the OS assumed it to be a usb/bluetooth keyboard= ;=20 created a /dev/uskbo and assigned it to be the console keyboard, thus leavi= ng=20 me with no way to type. THE HARDWARE: I am using a TECOM BT3033A dongle with a Compaq Presario 1215EA (it has two= =20 USB plugs, the first has the dongle, the second a USB a4Tech mouse - but th= e=20 mouse part is relevant for the issue). The mobile phone is a SonyEricsson=20 K700i. I am running FBSD 5.3-release. THE SOLUTION: A - Following Maksim's suggestion, I commented out the following lines=20 from /etc/dev.conf # When a USB keyboard arrives, attach it as the console keyboard # attach 100 { # device-name "ukbd0"; # action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 < /dev/console"; # }; # detach 100 { # device-name "ukbd0"; # action "kbdcontrol -k /dev/kbd0 < /dev/console"; # }; B - Now, with ng_ubt_load=3D"YES" in /boot/load.conf I get at startup the i= nfo=20 bellow (the following devs are created: ukbd0, kb1, ums0, ums1. ukbd0, kb1= =20 and ums1 dissapear as soon as I type =AB/etc/rc.bluetooth start ubt0=BB. As= far=20 as I can understand this means a bluetooth mouse and or bluetooth keyboard= =20 could work if I had them); since the ukbd0 is no longer automatically=20 assigned as console keyboard (step A) my problem dissapeared: Nov 18 01:55:35 kernel: uhci0: port 0x1800-0x1= 81f=20 irq 5 at device 7.2 on pci0 Nov 18 01:55:35 kernel: uhci0: [GIANT-LOCKED] Nov 18 01:55:35 kernel: usb0: on uhci0 Nov 18 01:55:35 kernel: usb0: USB revision 1.0 Nov 18 01:55:35 kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00= ,=20 addr 1 Nov 18 01:55:35 kernel: uhub0: 2 ports with 2 removable, self powered Nov 18 01:55:35 kernel: ums0: A4Tech USB Optical Mouse, rev 1.10/0.01, add= r=20 2, iclass 3/1 Nov 18 01:55:35 kernel: ums0: 7 buttons and Z dir. Nov 18 01:55:35 kernel: uhub1: Broadcom product 0x3535, class 9/0, rev=20 2.00/1.00, addr 3 Nov 18 01:55:35 kernel: uhub1: 3 ports with 0 removable, bus powered Nov 18 01:55:35 kernel: ubt0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 4 Nov 18 01:55:35 kernel: ubt0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 4 Nov 18 01:55:35 kernel: ubt0: Interface 0 endpoints: interrupt=3D0x81,=20 bulk-in=3D0x82, bulk-out=3D0x2 Nov 18 01:55:35 kernel: ubt0: Interface 1 (alt.config 4) endpoints:=20 isoc-in=3D0x83, isoc-out=3D0x3; wMaxPacketSize=3D64; nframes=3D5, buffer si= ze=3D320 Nov 18 01:55:35 kernel: ukbd0: Broadcom product 0x0099, rev 1.10/1.00, add= r=20 5, iclass 3/1 Nov 18 01:55:35 kernel: kbd1 at ukbd0 Nov 18 01:55:35 kernel: ums1: Broadcom product 0x0097, rev 1.10/1.00, addr= 6,=20 iclass 3/1 Nov 18 01:55:35 kernel: ums1: 3 buttons C - usbdevs -v -d shows: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),=20 VIA(0x0000),rev 1.00 uhub0 port 1 addr 2: low speed, power 100 mA, config 1, USB Optical Mouse(0x0006= ),=20 A4Tech(0x09da), rev 0.01 ums0 port 2 addr 3: full speed, power 100 mA, config 1, product 0x3535(0x3535),= =20 Broadcom(0x0a5c), rev 1.00 uhub1 port 1 addr 4: full speed, self powered, config 1, Bluetooth=20 Transceiver(0x200a), Broadcom Corp(0x0a5c), rev 1.00 ubt0 port 2 addr 5: full speed, self powered, config 1, product 0x0099(0x0099)= ,=20 Broadcom(0x0a5c), rev 1.00 ukbd0 port 3 addr 6: full speed, self powered, config 1, product 0x0097(0x0097)= ,=20 Broadcom(0x0a5c), rev 1.00 ums1 AFTER =AB/etc/rc.bluetooth start ubt0=BB that TURNS INTO: Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000),=20 VIA(0x0000),rev 1.00 uhub0 port 1 addr 2: low speed, power 100 mA, config 1, USB Optical Mouse(0x0006= ),=20 A4Tech(0x09da), rev 0.01 ums0 port 2 addr 3: full speed, power 100 mA, config 1, product 0x3535(0x3535),= =20 Broadcom(0x0a5c), rev 1.00 uhub1 port 1 addr 4: full speed, self powered, config 1, Bluetooth=20 Transceiver(0x200a), Broadcom Corp(0x0a5c), rev 1.00 ubt0 port 2 powered port 3 powered =20 ********************************* Just for the sake of argument and because eventually it might be helpful to= =20 someone, this is what I did next following the instructions found here: and here: ********************************* D - Started the stack and found my dongle address to be 00:03:c9:34:d1:f5: # /etc/rc.bluetooth start ubt0 BD_ADDR: 00:03:c9:34:d1:f5 =46eatures: 0xff 0xff 0xd 0x38 0x8 0x8 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 377 bytes Number of ACL packets: 10 Max. SCO packet size: 16 bytes Number of SCO packets: 0 E - With bluetooth on on the mobile, set to be in =ABreceptive mode=BB, I found the mobile phone address to be 00:0e:07:e4:55:f7: # hccontrol -n ubt0hci inquiry Inquiry result, num_responses=3D1 Inquiry result #0 BD_ADDR: 00:0e:07:e4:55:f7 Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x4756 Inquiry complete. Status: No error [00] =46 - Checked that the PC was able to get the name the phone was reporting # hccontrol -n ubt0hci remote_name_request 00:0e:07:e4:55:f7 BD_ADDR: 00:0e:07:e4:55:f7 Name: K700i G - Checked that the PC was able to connect to the mobile # hccontrol -n ubt0hci create_connection 00:0e:07:e4:55:f7 BD_ADDR: 00:0e:07:e4:55:f7 Connection handle: 6 Encryption mode: Disabled [0] H - Checked that the connection was properly listed # hccontrol -n ubt0hci read_connection_list Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State 00:0e:07:e4:55:f7 6 ACL 0 MAST NONE 0 0 OPEN I - Tested the quality of the connection # hccontrol -n ubt0hci get_link_quality 6 Connection handle: 6 Link quality: 255 =46 - Checked the PC was able to terminate the connection # hccontrol -n ubt0hci disconnect 6 Connection handle: 6 Reason: Connection terminated by local host [0x16] G - Pinged the phone just for the sake of it. # l2ping -a 00:0e:07:e4:55:f7 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D0 time=3D30164.356 ms result=3D0x22 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D1 time=3D5142.148 ms result=3D0x4 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D2 time=3D2678.448 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D3 time=3D23.042 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D4 time=3D21.016 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D5 time=3D19.766 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D6 time=3D27.627 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D7 time=3D27.354 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D8 time=3D21.189 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D9 time=3D20.949 ms result=3D0 0 bytes from 00:0e:07:e4:55:f7 seq_no=3D10 time=3D19.870 ms result=3D0 H - I then made sure the addresses were translated to easier to use names b= y=20 editing: /etc/bluetooth/hosts 00:03:c9:34:d1:f5 PCNAME # Localhost 00:0e:07:e4:55:f7 K700i # K700i I - And made sure hcsecd would know about the phone /etc/bluetooth/hcsecd.conf device { bdaddr 00:0e:07:e4:55:f7; name "K700i"; key nokey; pin "1234"; } J - Started hcsecd with =ABverbose=BB mode in console # hcsecd -d K - I then paired the devices (from phone). The following info showed up: hcsecd[1406]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr=20 00:0e:07:e4:55:f7 hcsecd[1406]: Found matching entry, remote bdaddr 00:0e:07:e4:55:f7, name=20 'K700i', PIN code exists hcsecd[1406]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr=20 00:0e:07:e4:55:f7 hcsecd[1406]: Got Link_Key_Notification event from 'ubt0hci', remote bdaddr= =20 00:0e:07:e4:55:f7 hcsecd[1406]: Updating link key for the entry, remote bdaddr=20 00:0e:07:e4:55:f7,name 'K700i', link key exists I - The phone shows the PC reporting Push Object support. J - Finaly I checked the services available in the phone from the PC: # sdpcontrol -a K700i browse Record Handle: 0x00010000 Service Class ID List: Dial-Up Networking (0x1103) Generic Networking (0x1201) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Dial-Up Networking (0x1103) ver. 1.0 Record Handle: 0x00010002 Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 4 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.0 Record Handle: 0x00010003 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 2 Record Handle: 0x00010004 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 Record Handle: 0x00010005 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 6 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x00010006 Service Class ID List: IrMC Sync (0x1104) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 8 OBEX (0x0008) Bluetooth Profile Descriptor List: IrMC Sync (0x1104) ver. 1.0 Record Handle: 0x0001000a Service Class ID List: Imaging Responder (0x111b) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 9 OBEX (0x0008) Bluetooth Profile Descriptor List: Imaging (0x111a) ver. 1.0 Record Handle: 0x0001000d Service Class ID List: OBEX File Transfer (0x1106) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 7 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX File Transfer (0x1106) ver. 1.0 Record Handle: 0x0001000e Service Class ID List: Handsfree Audio Gateway (0x111f) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 5 Bluetooth Profile Descriptor List: Handsfree (0x111e) ver. 1.1 Record Handle: 0x00010018 Service Class ID List: 0xee000058-0002-8000-1000-000000000002 Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 15 OBEX (0x0008) Record Handle: 0x0001001b Service Class ID List: PNP Information (0x1200) Record Handle: 0x0001001c Service Class ID List: Human Interface Device (0x1124) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 17 HIDP (0x0011) Bluetooth Profile Descriptor List: Human Interface Device (0x1124) ver. 1.0 I have yet to try the rest of the stuff. ***************************************************************** EXTRA INFO (shown at boot time with different scenarios): *****************************************************************=20 I - With NO ng_ubt_load=3D"YES" in /boot/load.conf and with USB mouse plugg= ed=20 in: Nov 18 00:52:56 kernel: uhci0: port 0x1800-0x1= 81f=20 irq 5 at device 7.2 on pci0 Nov 18 00:52:56 kernel: uhci0: [GIANT-LOCKED] Nov 18 00:52:56 kernel: usb0: on uhci0 Nov 18 00:52:56 kernel: usb0: USB revision 1.0 Nov 18 00:52:56 kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00= ,=20 addr 1 Nov 18 00:52:56 kernel: uhub0: 2 ports with 2 removable, self powered Nov 18 00:52:56 kernel: ums0: A4Tech USB Optical Mouse, rev 1.10/0.01, add= r=20 2, iclass 3/1 Nov 18 00:52:56 kernel: ums0: 7 buttons and Z dir. Nov 18 00:52:56 kernel: uhub1: Broadcom product 0x3535, class 9/0, rev=20 2.00/1.00, addr 3 Nov 18 00:52:56 kernel: uhub1: 3 ports with 0 removable, bus powered Nov 18 00:52:56 kernel: ugen0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 4 Nov 18 00:52:56 kernel: ukbd0: Broadcom product 0x0099, rev 1.10/1.00, add= r=20 5, iclass 3/1 Nov 18 00:52:56 kernel: kbd1 at ukbd0 Nov 18 00:52:56 kernel: ums1: Broadcom product 0x0097, rev 1.10/1.00, addr= 6,=20 iclass 3/1 Nov 18 00:52:56 kernel: ums1: 3 buttons II - With NO ng_ubt_load=3D"YES" in /boot/load.conf and no USB mouse plugge= d in =20 Nov 18 01:09:31 kernel: uhci0: port 0x1800-0x1= 81f=20 irq 5 at device 7.2 on pci0 Nov 18 01:09:31 kernel: uhci0: [GIANT-LOCKED] Nov 18 01:09:31 kernel: usb0: on uhci0 Nov 18 01:09:31 kernel: usb0: USB revision 1.0 Nov 18 01:09:31 kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00= ,=20 addr 1 Nov 18 01:09:31 kernel: uhub0: 2 ports with 2 removable, self powered Nov 18 01:09:31 kernel: uhub1: Broadcom product 0x3535, class 9/0, rev=20 2.00/1.00, addr 2 Nov 18 01:09:31 kernel: uhub1: 3 ports with 0 removable, bus powered Nov 18 01:09:31 kernel: ugen0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 3 Nov 18 01:09:31 kernel: ukbd0: Broadcom product 0x0099, rev 1.10/1.00, add= r=20 4, iclass 3/1 Nov 18 01:09:31 kernel: kbd1 at ukbd0 Nov 18 01:09:31 kernel: ums0: Broadcom product 0x0097, rev 1.10/1.00, addr= 5,=20 iclass 3/1 com product 0x3535, class 9/0, rev 2.00/1.00, addr 2 Nov 18 01:09:31 kernel: uhub1: 3 ports with 0 removable, bus powered Nov 18 01:09:31 kernel: ugen0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 3 Nov 18 01:09:31 kernel: ukbd0: Broadcom product 0x0099, rev 1.10/1.00, add= r=20 4, iclass 3/1 Nov 18 01:09:31 kernel: kbd1 at ukbd0 Nov 18 01:09:31 kernel: ums0: Broadcom product 0x0097, rev 1.10/1.00, addr= 5,=20 iclass 3/1 Nov 18 01:09:31 kernel: ums0: 3 buttons III - WITH ng_ubt_load=3D"YES" in /boot/load.conf and NO USB mouse Nov 18 01:16:19 kernel: uhci0: port 0x1800-0x1= 81f=20 irq 5 at device 7.2 on pci0 Nov 18 01:16:19 kernel: uhci0: [GIANT-LOCKED] Nov 18 01:16:19 kernel: usb0: on uhci0 Nov 18 01:16:19 kernel: usb0: USB revision 1.0 Nov 18 01:16:19 kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00= ,=20 addr 1 Nov 18 01:16:19 kernel: uhub0: 2 ports with 2 removable, self powered Nov 18 01:16:19 kernel: uhub1: Broadcom product 0x3535, class 9/0, rev=20 2.00/1.00, addr 2 Nov 18 01:16:19 kernel: uhub1: 3 ports with 0 removable, bus powered Nov 18 01:16:19 kernel: ubt0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 3 Nov 18 01:16:19 kernel: ubt0: Broadcom Corp Bluetooth Transceiver, rev=20 1.10/1.00, addr 3 Nov 18 01:16:19 kernel: ubt0: Interface 0 endpoints: interrupt=3D0x81,=20 bulk-in=3D0x82, bulk-out=3D0x2 Nov 18 01:16:19 kernel: ubt0: Interface 1 (alt.config 4) endpoints:=20 isoc-in=3D0x83, isoc-out=3D0x3; wMaxPacketSize=3D64; nframes=3D5, buffer si= ze=3D320 Nov 18 01:16:19 kernel: ukbd0: Broadcom product 0x0099, rev 1.10/1.00, add= r=20 4, iclass 3/1 Nov 18 01:16:19 kernel: kbd1 at ukbd0 Nov 18 01:16:19 kernel: ums0: Broadcom product 0x0097, rev 1.10/1.00, addr= 5,=20 iclass 3/1 Nov 18 01:16:19 kernel: ums0: 3 buttons From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 07:26:41 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 8EB2416A4CE for ; Thu, 18 Nov 2004 07:26:41 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C853E43D41 for ; Thu, 18 Nov 2004 07:26:40 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CUggh-0000T6-5C; Thu, 18 Nov 2004 10:26:39 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: <419B8C3A.6030003@savvis.net> References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> <1100711659.47346.11.camel@localhost> <419B8C3A.6030003@savvis.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 18 Nov 2004 10:26:38 +0300 Message-Id: <1100762798.1069.13.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru 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 07:26:41 -0000 =F7 =D3=D2, 17/11/2004 =D7 09:36 -0800, Maksim Yevmenkin =D0=C9=DB=C5=D4: > > Good news, is there any estimations or like ? >=20 > no. life with 8 months old son can not be predicted easily :) (come to=20 > 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 am going to get such mouse but if it will not be supported for > > years it has no sense. >=20 > you can always write support yourself :) Yes, this option is always available with BSD :) 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) Frankly speaking I afraid case when with syscons pointing to vkbd DDB will be called, and what happens ?=20 Another option is to use special binding for DDB keyboard, but I did not like it. > max --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 07:37: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 185B816A4CE for ; Thu, 18 Nov 2004 07:37:27 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B5A43D41 for ; Thu, 18 Nov 2004 07:37:26 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CUgr7-0000Ua-Jz; Thu, 18 Nov 2004 10:37:25 +0300 From: Vladimir Grebenschikov To: bluetooth@freebsd.org In-Reply-To: References: <1100552998.1098.5.camel@localhost> <419B8353.7040908@savvis.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 18 Nov 2004 10:37:25 +0300 Message-Id: <1100763445.1069.20.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: miketmp@xs4all.nl Subject: Re: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru 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 07:37:27 -0000 =F7 =D3=D2, 17/11/2004 =D7 19:47 +0100, Mike Crosland =D0=C9=DB=C5=D4: > My current setup allows me to use my Logitech di Novo keyboard/mouse on m= y =20 > dual-boot machine. FreeBSD just sees it as being a usb hub. However I did= =20 > have to do some patching and a kernel rebuild to do it. Also FreeBSD =20 > doesn't recognise the bt hub, which means if you want to link to other bt= =20 > devices you need to have a seperate dongle. >=20 > What would be decidedly cool was if the usb bt chip AND extra dongle(s)= =20 > ie multiple devices could be recognised, in much the same way that the =20 > system can handle several network cards. Ok, please advise,=20 As I understand BT mouses often shipped with BT USB dongle, But is it safe to buy mouse with that type ? Is protocol between this dongle and BT mouse is BTHID - complaint ? I simple do not want to get mouse that will not work without that dongle. > Mike >=20 > PS Max - congratulations to your enlarging user base - er I mean family > :) Max thank you for excellent BT support ! --=20 Vladimir B. Grebenchikov vova@fbsd.ru 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 From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 17:42: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 AAF8216A4CE for ; Thu, 18 Nov 2004 17:42:27 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6368943D4C for ; Thu, 18 Nov 2004 17:42:27 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iAIHgNIr010309; Thu, 18 Nov 2004 11:42:23 -0600 Received: from s228130hz1ew03.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 18 Nov 2004 11:42:19 -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:42:14 -0600 Message-ID: <419CDEF5.4090005@savvis.net> Date: Thu, 18 Nov 2004 09:42:13 -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> <1100763445.1069.20.camel@localhost> In-Reply-To: <1100763445.1069.20.camel@localhost> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 18 Nov 2004 17:42:14.0160 (UTC) FILETIME=[F07A8900:01C4CD95] X-ECS-MailScanner: No virus is found cc: bluetooth@freebsd.org cc: miketmp@xs4all.nl 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:42:27 -0000 Vladimir Grebenschikov wrote: > В ср, 17/11/2004 в 19:47 +0100, Mike Crosland пишет: > >>My current setup allows me to use my Logitech di Novo keyboard/mouse on my >>dual-boot machine. FreeBSD just sees it as being a usb hub. However I did >>have to do some patching and a kernel rebuild to do it. Also FreeBSD >>doesn't recognise the bt hub, which means if you want to link to other bt >>devices you need to have a seperate dongle. >> >> What would be decidedly cool was if the usb bt chip AND extra dongle(s) >>ie multiple devices could be recognised, in much the same way that the >>system can handle several network cards. > > Ok, please advise, > > As I understand BT mouses often shipped with BT USB dongle, > But is it safe to buy mouse with that type ? Is protocol between this > dongle and BT mouse is BTHID - complaint ? what Mike has is a bluetooth receiver that implements 'hid proxy' feature. basically the bluetooth receiver implements bluetooth hid protocol and pretends to be hub with usb keyboard and mouse attached. in this case *no* bluetooth support is required from os. again, from os point of view it looks like regular usb keyboard and mouse. that also mean that it is *not possible* to use bluetooth receiver to talk to other devices. that is unless you turn 'hid proxy' feature off, but in this case os *must* implement bluetooth hid protocol. > I simple do not want to get mouse that will not work without that > dongle. if it is a bluetooth mouse and it has been certified (which is usually the case) then in *must* work with any certified bluetooth dongle. max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 18:37:59 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 40B8B16A4CE for ; Thu, 18 Nov 2004 18:37:59 +0000 (GMT) Received: from vbook.fbsd.ru (user142.hovrino.net [82.179.232.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40BF143D1F for ; Thu, 18 Nov 2004 18:37:57 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CUrAJ-0000YW-46; Thu, 18 Nov 2004 21:37:55 +0300 From: Vladimir Grebenschikov To: Maksim Yevmenkin 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> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 18 Nov 2004 21:37:54 +0300 Message-Id: <1100803074.1347.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: bluetooth@freebsd.org Subject: Re: Bluetooth mouse X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru 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 18:37:59 -0000 =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 From owner-freebsd-bluetooth@FreeBSD.ORG Thu Nov 18 19:48:33 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 B353016A4CE for ; Thu, 18 Nov 2004 19:48:33 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E30F43D46 for ; Thu, 18 Nov 2004 19:48:33 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iAIJj3Ir020970; Thu, 18 Nov 2004 13:45:03 -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 13:44:55 -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 13:44:47 -0600 Message-ID: <419CFBAE.7040500@savvis.net> Date: Thu, 18 Nov 2004 11:44:46 -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> <419CDD47.7000108@savvis.net> <1100803074.1347.12.camel@localhost> In-Reply-To: <1100803074.1347.12.camel@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Nov 2004 19:44:47.0719 (UTC) FILETIME=[0F8A9770:01C4CDA7] 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 19:48:33 -0000 [...] >>>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. > > 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. the problem is that you can only have one keyboard active at a time. vkbd(4) is *NOT* trying to solve this problem. at least not in its current form. it is *NOT* a keyboard mux. it is a *kludge* to work around bigger problem. > As I understand valid (and only) usage of vkbd is > 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. will you please stop with atkbd, ukbd, ddb etc. wireless keyboards *CAN* and *WILL* come and go. it is their nature. so it is up to the userspace daemon to detect when wireless keyboard comes online/offline and switch from/to wired keyboard accordingly. that is what i tried to do in bthidd(8). if your system has panic'ed or you hit ctrl-alt-esc thats too bad for you. you just have lost your keyboard. >>>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. > > No, as I said before I just want be able to enter DDB with at keyboard > when I have use bt keyboard. you *CANNOT* have two or more keyboards active at the same time. period. at least not now. it has been a problem for a while. you have to live with this. vkbd(4) is *NOT* going to help you. at least not in its current form. now it *CAN* be changed to implement many-to-one mux. hell, you can even make it many-to-many mux if you want. the only problem is that syscons will accept input from one keyboard at a time. if you fix syscons, then you do not need vkbd at all. > I do not try to flame at all, just supply ideas. i understand, i just think that vkbd is the wrong place to fix it, thats it. max