Date: Wed, 22 Jun 2011 09:17:39 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: Broadcom BCM2046B1 in HCI mode? Message-ID: <BANLkTikbiJtr6E7-G86tEX-PpTZn2R8u7A@mail.gmail.com> In-Reply-To: <BANLkTikUpA-1NxFrrgXACzPoeocjjZXT=A@mail.gmail.com> References: <BANLkTikUpA-1NxFrrgXACzPoeocjjZXT=A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, June 21, 2011, Brandon Gooch <jamesbrandongooch@gmail.com> wrote: > I have one of these in my notebook: > > uhub4: <Broadcom BCM2046B1, class 9/0, rev 2.00/1.00, addr 5> on usbus0 > > This is a bluetooth device in HID mode, but I'd like to switch it to > HCI mode. I found the following in rc.conf(5): > > ubthidhci_enable > (bool) If set to ``YES'', change the USB Bluetooth controller > from HID mode to HCI mode. You also need to specify the > location of USB Bluetooth controller with the > ubthidhci_busnum and ubthidhci_addr variables. > > ubthidhci_busnum > Bus number where the USB Bluetooth controller is located. > Check the output of usbconfig(8) on your system to find this > information. > > ubthidhci_addr > Bus address of the USB Bluetooth controller. Check the out- > put of usbconfig(8) on your system to find this information. > > So I added the appropriate directives to /etc/rc.conf, to no avail: > > ubthidhci_enable="YES" > ubthidhci_busnum="0" > ubthidhci_addr="5" > > This basically calls usbconfig(8) at system start-up in the following way: > > /usr/sbin/usbconfig -u 0 -a 5 do_request 0x40 0 0 0 0 > /dev/null 2>&1 > > Running this command manually, I see this output: > > REQUEST = <ERROR> > > ...which I've read as potentially being OK, as the operation still may > have successfully completed -- it hasn't :( > > So, has anyone had any luck using this rc.conf(5) directive, or does > anyone on this list have a modified usbconfig(8) command that may help > me coax HCI from this device? Switching device between hid and hci modes is s something that is device / manufacturer specific. It could be that this particular device need different request or something like that. I would suggest to look at linux tool called hid2hci. It has support for different devices from different manufacturers. Thanks, Max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikbiJtr6E7-G86tEX-PpTZn2R8u7A>