From owner-freebsd-bluetooth@FreeBSD.ORG Wed Jan 12 21:04:03 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 23B1216A4CE for ; Wed, 12 Jan 2005 21:04:03 +0000 (GMT) Received: from mx1.wewitro.net (mx1.wewitro.net [82.96.83.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CD5943D3F for ; Wed, 12 Jan 2005 21:04:02 +0000 (GMT) (envelope-from rene@fantastici.de) Received: from localhost (localhost [127.0.0.1]) by mx1.wewitro.net (Postfix) with ESMTP id 5FF90900F; Wed, 12 Jan 2005 22:04:01 +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 14100-04; Wed, 12 Jan 2005 22:03:59 +0100 (CET) Received: from [192.168.17.48] (pD9E83997.dip.t-dialin.net [217.232.57.151]) by mx1.wewitro.net (Postfix) with ESMTP id 608CB82AF; Wed, 12 Jan 2005 22:03:59 +0100 (CET) In-Reply-To: <41E57004.8070201@savvis.net> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Ren=E9_Scholz?= Date: Wed, 12 Jan 2005 22:03:57 +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: Wed, 12 Jan 2005 21:04:03 -0000 Am 12.01.2005 um 19:44 Uhr schrieb Maksim Yevmenkin: [...] > what driver attaches to the device? ugen(4), uhid(4) or other? can you=20= > tell what endpoints are available? hint: look in /var/log/messages and=20= > /dev. > I had uhid, ums and ukbd compiled into my kernel, so ukbd und ums take=20= the device. Your hints were the right ones ;-) just compiled hid2hci.c with libusb,=20= changed the kernel to use uhid, ums and ukbd as modules so that ugen attached to=20 the device. Then I loaded ubt_ng and used hid2hci to switch the modes, hid2hci gave an=20 error "Switching device 0a12:1000 to HCI mode failed (Input/output error)" but the=20 switch was successfully done and voila ubt_ng found my bluetooh device. If I'd have a bt mouse and/or keyboard there might be some hassle to=20 load and unload the modules in the right order to use the hid or the hci part, but I have neither=20 of them so it's okay. So thank you and Marcel for giving me the right input and yes hid2hci.c=20= has no dependencies on the Linux USB stack. Ren=E9 -- =20