From owner-freebsd-bluetooth@FreeBSD.ORG Thu Jan 13 06:08:00 2005 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 6144816A4CE for ; Thu, 13 Jan 2005 06:08:00 +0000 (GMT) Received: from mx1.wewitro.net (mx1.wewitro.net [82.96.83.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6188843D39 for ; Thu, 13 Jan 2005 06:07:59 +0000 (GMT) (envelope-from rene@fantastici.de) Received: from localhost (localhost [127.0.0.1]) by mx1.wewitro.net (Postfix) with ESMTP id 4460690F8; Thu, 13 Jan 2005 07:07:58 +0100 (CET) Received: from mx1.wewitro.net ([82.96.83.62]) by localhost (mx1.wewitro.net [82.96.83.62]) (amavisd-new, port 10024) with LMTP id 22931-02-2; Thu, 13 Jan 2005 07:07:56 +0100 (CET) Received: from [192.168.17.48] (pD9E83E75.dip.t-dialin.net [217.232.62.117]) by mx1.wewitro.net (Postfix) with ESMTP id 12FF98C25; Thu, 13 Jan 2005 07:07:55 +0100 (CET) In-Reply-To: <41E5C005.1040506@savvis.net> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net> <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> <41E5C005.1040506@savvis.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <7746422F-6529-11D9-BFF9-000A95688814@fantastici.de> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Ren=E9_Scholz?= Date: Thu, 13 Jan 2005 07:07:55 +0100 To: Maksim Yevmenkin X-Mailer: Apple Mail (2.619) X-Virus-Scanned: by amavisd-maia-1.0.0-rc5 (Debian) at wewitro.net cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching 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, 13 Jan 2005 06:08:00 -0000 Am 13.01.2005 um 1:25 Uhr schrieb Maksim Yevmenkin: > Ren=E9, > >>> what driver attaches to the device? ugen(4), uhid(4) or other? can >>> you tell what endpoints are available? hint: look in >>> /var/log/messages and /dev. >> I had uhid, ums and ukbd compiled into my kernel, so ukbd und ums >> take the device. Your hints were the right ones ;-) just compiled >> hid2hci.c with libusb, changed the kernel to use uhid, ums and ukbd >> as modules so that ugen attached to the device. Then I loaded ubt_ng >> and used hid2hci to switch the modes, hid2hci gave an error >> "Switching device 0a12:1000 to HCI mode failed (Input/output error)" >> but the switch was successfully done and voila ubt_ng found my >> bluetooh device. > > hmm... ok. does device stay in hci mode? or do you have to switch it=20= > every time after you re-connect it? No it doesn't stay in this mode, on every re-connect it is in hid mode=20= again. I'll try to write a usbd rule that execute hid2hci to do this automaticly each time the=20 device connects. > >> If I'd have a bt mouse and/or keyboard there might be some hassle to >> load and unload the modules in the right order to use the hid or the >> hci part, but I have neither of them so it's okay. > > it would be real hassle if you had wired usb keyboard :) ;-) That's true. > >> So thank you and Marcel for giving me the right input and yes >> hid2hci.c has no dependencies on the Linux USB stack. > > i've got to get me one of these dongles :) so i can write bsd version=20= > of hid2hci. > If I woudn't need it every day for my GPS communication I would send it=20= to you to play. Btw. these devices are becoming very cheap today. I've seen my model=20 for 22 Euros here in Germany. Ren=E9 -- =20