Date: Wed, 12 Jan 2005 16:25:41 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: =?ISO-8859-1?Q?Ren=E9_Scholz?= <rene@fantastici.de> Cc: freebsd-bluetooth@freebsd.org Subject: Re: HID Proxy switching Message-ID: <41E5C005.1040506@savvis.net> In-Reply-To: <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de> References: <1105515411.41e4d393d2c5b@webmail.wewitro.net> <1105531775.7961.46.camel@pegasus> <41E57004.8070201@savvis.net> <798814BF-64DD-11D9-BFF9-000A95688814@fantastici.de>
next in thread | previous in thread | raw e-mail | index | archive | help
René, >> 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 every time after you re-connect it? > 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 :) > 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 of hid2hci. max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E5C005.1040506>