Date: Thu, 8 Nov 2007 13:05:00 -0800 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: jimmiejaz@gmail.com Cc: freebsd-bluetooth@freebsd.org, freebsd-questions@freebsd.org Subject: Re: usb dongle Message-ID: <bb4a86c70711081305k7c188234sc36944007aec8498@mail.gmail.com> In-Reply-To: <47336CE0.4040909@gmail.com> References: <47336CE0.4040909@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/8/07, Jimmie James <jimmiejaz@gmail.com> wrote: > I have a Broadcom BCM92035DGROM dongle, and this is what I'm seeing. > I'm assuming it's not supported, (from the handbook: The Broadcom > BCM2033 chip based Bluetooth devices are supported via the ubtbcmfw(4) > and ng_ubt(4) drivers) > > Is there anyone that's gotten this model to work, or is it an exercise > in futility? first of all, i doubt that BCM92035 is using 2033 chip. i think it is uses different (2035?) chip. it also appears that this particular dongle may need to use special non-standard initialization sequence. can you please check vendor id/product id pair for your dongle (use usbdevs(8)). 1) if it is (0x0a5c, 0x200a) then you could try to comment out "reset" command in /etc/rc.d/bluetooth 2) if it is (x0a5c, 0x2009) then you out of luck - this device needs special non-standard initialization sequence. ng_ubt(4) currently does not support that. if i can get this dongle into my hands i can fix ng_ubt(4) thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70711081305k7c188234sc36944007aec8498>