Troubleshooting a USB Bluetooth Dongle

Maksim Yevmenkin maksim.yevmenkin at gmail.com
Tue Nov 2 22:35:23 UTC 2010


On Tue, Nov 2, 2010 at 2:44 PM, Iain Hibbert <plunky at rya-online.net> wrote:
> On Tue, 2 Nov 2010, Maksim Yevmenkin wrote:
>
>> > Nov  2 16:08:02 tethys root: Unknown USB device: vendor 0x0cf3 product
>> > 0x3000 bus uhub8
>> > Nov  2 16:08:02 tethys kernel: ugen3.3: at usbus3
>> >
>> > Which doesn't give me much.  Doing a config dump:
>>
>> i disagree :) it gives you vendor/device id pair which is
>> 0x0cf3/0x3000. in other words, your adapter is based on atheros ar3011
>> chip and will require a special (new) driver that would download
>> firmware. ubtbcmfw(4) will not work, because its for broadcom chip. i
>> only mentioned this because it would be similar, but not the same :)
>>
>> [...]
>>
>> > So, any suggestions on where to go next?
>>
>> 1) need to write a special ubtathfw(4) driver;
>>
>> 2) obtain firmware (i assume it would be on a cd that came with the dongle);
>
> 3) as this device attaches at ugen(4) already, write a userland program
>   that opens the correct endpoint and writes the firmware directly

yes, i guess we could do that too :) linux driver does not seem to do
anything fancy. just sends control request (firmware download),
followed by a bunch of bulk requests (4k chunks of firmware).

> (http://homepages.rya-online.net/plunky/bcmfw-1.0.tar.gz does this for the
> old broadcom device on NetBSD, perhaps it would be easy to adapt..)

yep

thanks,
max


More information about the freebsd-bluetooth mailing list