Date: Wed, 12 Jan 2005 22:03:57 +0100 From: =?ISO-8859-1?Q?Ren=E9_Scholz?= <rene@fantastici.de> To: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching Message-ID: <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> In-Reply-To: <41E57004.8070201@savvis.net> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net>
index | next in thread | previous in thread | raw e-mail
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 > 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. 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. So thank you and Marcel for giving me the right input and yes hid2hci.c has no dependencies on the Linux USB stack. René --help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?798814BF-64DD-11D9-BFF9-000A95688814>