jimmiejaz at gmail.com
Thu Nov 8 13:29:53 PST 2007
Maksim Yevmenkin wrote:
> On 11/8/07, Jimmie James <jimmiejaz at 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
I was searching google and came across these two threads,
So it looked like it was possible...
usbdevs -dv shows:
port 1 addr 2: full speed, power 100 mA, config 1,
BCM92035DGROM(0x0850), Broadcom(0x22b8), rev 1.09
If you need anything else, I'll do what I can.
If you can't beat your computer at chess, try kickboxing.
--- --- ---
Solving Today's Problems Tomorrow
More information about the freebsd-questions