Re: bluetooth working on 5.1-release

Hello Kim,

> Have bluetooth almost working on 5.1-release, thank you Max.

[...]
 
> The device is a Belkin F8T001, at plugin it logs:
> 
> Aug 17 16:43:01 radio kernel: ubt0: Broadcom Corp. BCM2033, rev 1.01/0.a0,
> addr 2
> Aug 17 16:43:01 radio kernel: ubt0: Interface 0 endpoints: interrupt=0x81,
> bulk-in=0x82, bulk-out=0x2
> Aug 17 16:43:01 radio kernel: ubt0: Interface 1 (alt.config 4) endpoints:
> isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320

yes, it is a Broadcom chip based device. you need to download firmware 
before you can use it.

> Procedure which works as follows:
> 
> > 1) make sure the USB device is detached
> > 2) load ubtbcmfw(4) module
> > 3) load ng_ubt(4) module
> > 4) attach the device
> 
> It logs:
> 
> Aug 17 16:10:31 radio kernel: ubtbcmfw0: Broadcom product 0x2033, rev
> 1.01/0.a0, addr 2             ^^^^^^^^^

yes, that is correct
 
> > 5) load Broadcom firmware with bcmfw(8) tools (in
> > /usr/src/usr.sbin/bluetooth)
> > (note: you need to get firmware off the internet - see man page)
> 
> Off the net:
> 
> http://bluez.sourceforge.net/download/bluez-bluefw-0.9.tar.gz
> 
> Then load the minidriver and firmware:
> 
> bcmfw -n ubtbcmfw0 -m /usr/local/bin/BCM2033-MD.hex -f [all one line..]
> /usr/local/bin/BCM2033-FW.bin

yes. that is also correct

> > 6) verify that ubtbcmfw0: device was detached and ubt0: device was
> > attached
> 
> It logs:
> 
> Aug 17 17:25:24 radio kernel: ubtbcmfw0: at uhub0 port 1 (addr 2)
> disconnected
> Aug 17 17:25:24 radio kernel: ubtbcmfw0: detached
> Aug 17 17:25:25 radio kernel: ubt0: Broadcom Corp. BCM2033, rev 1.01/0.a0,
> addr 2
> Aug 17 17:25:25 radio kernel: ubt0: Interface 0 endpoints: interrupt=0x81,
> bulk-in=0x82, bulk-out=0x2
> Aug 17 17:25:25 radio kernel: ubt0: Interface 1 (alt.config 4) endpoints:
> isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320

yes, that is what is should look like.
 
> > 7) run rc.bluetooth script on ubt0 device

[...]
 
> Yeah !! Great !!
> 
> Now it returns:
> 
> radio# /etc/rc.bluetooth start ubt0
> BD_ADDR: 00:03:c9:2d:c9:b5
> Features: 0xff 0xfd 0x5 00 00 00 00 00
> <3-Slot> <5-Slot> <Encryption> <Slot offset>
> <Timing accuracy> <Switch> <Hold mode> <Sniff mode>
> <Park mode> <Channel quality> <SCO link> <HV2 packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD>
> <Power control>
> Max. ACL packet size: 377 bytes
> Number of ACL packets: 10
> Max. SCO packet size: 16 bytes
> Number of SCO packets: 0

well, your Belkin adapter was initialized successfully. everything so far
looks
normal to me. BTW you do not have to have debug level so high :) 

> Now this problem:
> 
> radio# hccontrol -n ubt0hci inquiry
> Inquiry complete. Status: No error [00]
> 
> It logs:
> 
> Aug 17 17:28:41 radio kernel: ng_hci_process_event: ubt0hci - got HCI
> event=0xf, length=4
> Aug 17 17:28:47 radio kernel: ng_hci_process_event: ubt0hci - got HCI
> event=0x1, length=1
> Aug 17 17:29:59 radio kernel: ng_hci_process_event: ubt0hci - got HCI
> event=0xf, length=4
> Aug 17 17:30:05 radio kernel: ng_hci_process_event: ubt0hci - got HCI
> event=0x7, length=255
> 
> What do you think Max ?

i do not see any problem. you have asked local device to perform an "inquiry",
i.e. discover other Bluetooth devices in range. what local device tells you
is that there is no devices in range. Note: the device can be put into the
"hidden" mode where it will ignore "inquiry" requests. this "hidden" mode is
default on almost all devices. make sure you make your other device (i.e.
cell phone, PDA, etc.) is in "discoverable" (or sometimes called "visible")
mode. once you put other device in "discoverable" mode, run "inquiry" again
and you should see responses.

thanks,
max


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com