[Bluez-devel] Re: Developing Broadcom driver support

linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* [Bluez-devel] Re: Developing Broadcom driver support
@ 2006-02-11 19:05 Keith Bannister
  2006-02-12  6:17 ` Brad Midgley
  2006-02-13 17:27 ` Brad Midgley
  0 siblings, 2 replies; 6+ messages in thread
From: Keith Bannister @ 2006-02-11 19:05 UTC (permalink / raw)
  To: bluez-devel

[-- Attachment #1: Type: text/plain, Size: 7743 bytes --]

Hi Brad,


>  but it seems that the broadcom was
> erroneously returning a 0 in an mtu field


Thanks for the heads up.

I tried the Broadcom patches didn't seem to work fo me

I applied the patch from here
http://sourceforge.net/mailarchive/message.php?msg_id=14450798 and here
http://sourceforge.net/mailarchive/message.php?msg_id=14772190

using both and either one at a time. I never got much joy.

(p.s. is there a better way of recompiling than make modules;make
modules_install?)

The patch seems to correctly set the sco field:

[root@mythtv keith]# grep hci_cc_info_param /var/log/messages | grep mtu
Feb 11 16:21:24 localhost kernel: hci_cc_info_param: hci0 mtu: acl 377, sco
16 max_pkt: acl 10, sco 8

But I still don't get any audio, similar to other complaints.

>From hcidump, it looks like for some reason the driver decides not to send
any data.

The headset/dongle where a budget pack from maplin.
Dongle: LM Technologies BTU01D
Headset: LM Technologies BHS02C

That'll teach me for not getting a known brand. Oh well.

Attached is the info I can pull from various sources

If anyone has any other ideas, I'm keen to hear them.

Cheers,

Keith

-------------------------
BTSCO session
btsco v0.41
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
[root@mythtv kernel]# btsco -v 00:0B:0D:66:08:07
btsco v0.41
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
speaker volume: 11 mic volume: 13
i/o needed: connecting sco...
connected SCO channel
Done setting sco fd
recieved AT+VGS=11
Sending up speaker change 11
speaker volume: 11 mic volume: 13
driver is not in use
disconnected SCO channel

-----------------------
hci dump (run after btsco but before aplay)
root@mythtv ~]# /usr/sbin/hcidump -X
HCI sniffer - Bluetooth packet analyzer ver 1.18
device: hci0 snap_len: 1028 filter: 0xffffffff
< ACL data: handle 6 flags 0x02 dlen 18
    L2CAP(d): cid 0x0049 len 14 [psm 0]
      0000: 0b ef 15 41 54 2b 56 47  53 3d 31 31 0d 9a        ...AT+VGS=11..
< ACL data: handle 6 flags 0x02 dlen 18
    L2CAP(d): cid 0x0049 len 14 [psm 0]
      0000: 0b ef 15 41 54 2b 56 47  4d 3d 31 33 0d 9a        ...AT+VGM=13..
< HCI Command: Add SCO Connection (0x01|0x0007) plen 4
    handle 6 ptype 0x00e0
    Packet type: HV1 HV2 HV3
  0000: 06 00 e0 00                                       ....
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 07 04                                       ....
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 06 00 02 00                                    .....
> HCI Event: Connect Complete (0x03) plen 11
  0000: 00 01 00 07 08 66 0d 0b  00 00 01                 .....f.....
> ACL data: handle 6 flags 0x02 dlen 19
    L2CAP(d): cid 0x0041 len 15 [psm 0]
      0000: 09 ff 15 02 41 54 2b 56  47 53 3d 31 31 0d 5c
....AT+VGS=11.\
< ACL data: handle 6 flags 0x02 dlen 14
    L2CAP(d): cid 0x0049 len 10 [psm 0]
      0000: 0b ef 0d 0d 0a 4f 4b 0d  0a 9a                    .....OK...
> HCI Event: Number of Completed Packets (0x13) plen 5
  0000: 01 06 00 01 00                                    .....
< HCI Command: Disconnect (0x01|0x0006) plen 3
    handle 1 reason 0x13
    Reason: Remote User Teminated Connection
> HCI Event: Command Status (0x0f) plen 4
  0000: 00 01 06 04                                       ....
> HCI Event: Disconn Complete (0x05) plen 4
  0000: 00 01 00 16

------------------------------
I ran aplay as below. I had to Ctrl-C out of it (it never finishe)

[root@mythtv kernel]# aplay -B 1000000 -D plughw:Headset
/usr/share/sounds/KDE_Startup_new.wav
Playing WAVE '/usr/share/sounds/KDE_Startup_new.wav' : Signed 16 bit Little
Endian, Rate 22050 Hz, Stereo
Aborted by signal Interrupt...


-----------------------------
kernel debug after during aplay
Feb 11 16:35:17 localhost kernel: snd-bt-sco: playback_open
Feb 11 16:35:17 localhost kernel: snd-bt-sco: prepare ok bps: 16000 size:
16002 count: 4000
Feb 11 16:35:17 localhost kernel: hci_event_packet: hci0 evt 0xf
Feb 11 16:35:17 localhost kernel: hci_cs_link_ctl: hci0 ocf 0x7
Feb 11 16:35:17 localhost kernel: hci_event_packet: hci0 evt 0x13
Feb 11 16:35:17 localhost kernel: hci_num_comp_pkts_evt: hci0 num_hndl 1
Feb 11 16:35:17 localhost kernel: snd-bt-sco: playback_trigger 1
Feb 11 16:35:17 localhost kernel: snd-bt-sco: setting playback to bspcm
Feb 11 16:35:17 localhost kernel: hci_event_packet: hci0 evt 0x3
Feb 11 16:35:17 localhost kernel: hci_conn_complete_evt: hci0
Feb 11 16:35:18 localhost kernel: hci_event_packet: hci0 evt 0x13
Feb 11 16:35:18 localhost kernel: hci_num_comp_pkts_evt: hci0 num_hndl 1
Feb 11 16:35:21 localhost kernel: snd-bt-sco: playback_trigger 0
Feb 11 16:35:21 localhost kernel: snd-bt-sco: setting playback to NULL
Feb 11 16:35:21 localhost kernel: snd-bt-sco: Disposing of previous socket
count 3
Feb 11 16:35:21 localhost kernel: snd-bt-sco: file_count is 2 (expected 3)
Feb 11 16:35:21 localhost kernel: hci_event_packet: hci0 evt 0xf
Feb 11 16:35:21 localhost kernel: hci_cs_link_ctl: hci0 ocf 0x6
Feb 11 16:35:21 localhost kernel: hci_cs_link_ctl: hci0 Command status: ogf
LINK_CTL ocf 6 status 0
Feb 11 16:35:21 localhost kernel: hci_event_packet: hci0 evt 0x5
Feb 11 16:35:21 localhost kernel: hci_disconn_complete_evt: hci0 status 0
Feb 11 16:35:25 localhost kernel: hci_event_packet: hci0 evt 0x13
Feb 11 16:35:25 localhost kernel: hci_num_comp_pkts_evt: hci0 num_hndl 1
Feb 11 16:35:25 localhost kernel: hci_event_packet: hci0 evt 0x13
Feb 11 16:35:25 localhost kernel: hci_num_comp_pkts_evt: hci0 num_hndl 1
Feb 11 16:35:27 localhost kernel: hci_event_packet: hci0 evt 0xf
Feb 11 16:35:27 localhost kernel: hci_cs_link_ctl: hci0 ocf 0x6
Feb 11 16:35:27 localhost kernel: hci_cs_link_ctl: hci0 Command status: ogf
LINK_CTL ocf 6 status 0
Feb 11 16:35:27 localhost kernel: hci_event_packet: hci0 evt 0x5
Feb 11 16:35:27 localhost kernel: hci_disconn_complete_evt: hci0 status 0


--------------------------------
root@mythtv kernel]# /usr/sbin/hciconfig -a
hci0:   Type: USB
        BD Address: 00:0B:0D:63:41:46 ACL MTU: 377:10 SCO MTU: 16:8
        UP RUNNING PSCAN ISCAN AUTH ENCRYPT
        RX bytes:2507 acl:79 sco:0 events:123 errors:0
        TX bytes:2014 acl:63 sco:0 commands:42 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'mythtv-0'
        Class: 0x120104
        Service Classes: Networking
        Device Class: Computer, Desktop workstation
        HCI Ver: 1.2 (0x2) HCI Rev: 0x4 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
        Manufacturer: Broadcom Corporation (15)

---------------------------
root@mythtv kernel]# /usr/sbin/hciconfig hci0 revision
hci0:   Type: USB
        BD Address: 00:0B:0D:63:41:46 ACL MTU: 377:10 SCO MTU: 16:8
        Firmware 4.3.009

----------------------------
[root@mythtv kernel]# hcitool info 00:0B:0D:66:08:07
Requesting information ...
        BD Address:  00:0B:0D:66:08:07
        Device Name: HSII-E
        LMP Version: 1.2 (0x2) LMP Subversion: 0x611
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
                <encryption> <slot offset> <timing accuracy> <role switch>
                <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
                <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
                <paging scheme> <power control> <transparent SCO>
                <AFH cap. slave> <AFH cap. master>

[-- Attachment #2: Type: text/html, Size: 11914 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-devel] Re: Developing Broadcom driver support
  2006-02-11 19:05 [Bluez-devel] Re: Developing Broadcom driver support Keith Bannister
@ 2006-02-12  6:17 ` Brad Midgley
  2006-02-12 23:00   ` Mario
  2006-02-13 17:27 ` Brad Midgley
  1 sibling, 1 reply; 6+ messages in thread
From: Brad Midgley @ 2006-02-12  6:17 UTC (permalink / raw)
  To: bluez-devel

Keith

> http://sourceforge.net/mailarchive/message.php?msg_id=14772190

We should find out exactly what that second poster "whoopie" was doing
to set the mtu. Apparently he was only asking if the modified patch
would work but he had gotten it working by using the original patch and
tweaking the mtu at runtime.

Brad


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-devel] Re: Developing Broadcom driver support
  2006-02-12  6:17 ` Brad Midgley
@ 2006-02-12 23:00   ` Mario
  2006-02-13  0:12     ` Chase Douglas
  0 siblings, 1 reply; 6+ messages in thread
From: Mario @ 2006-02-12 23:00 UTC (permalink / raw)
  To: bluez-devel

2006/2/12, Brad Midgley <bmidgley@xmission.com>:
> We should find out exactly what that second poster "whoopie" was doing
> to set the mtu. Apparently he was only asking if the modified patch
> would work but he had gotten it working by using the original patch and
> tweaking the mtu at runtime.

It's incredible! Without any patch to the kernel.

hciconfig hci0 scomtu 64:8

IT WORKS!! A nasty Broadcom BT Chipset works! :\

root@legolas:~# hciconfig hci0 revision
hci0:   Type: USB
        BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 16:0
        Firmware 2.105 / 97

root@legolas:~# hciconfig hci0 scomtu 64:8

root@legolas:~# hciconfig hci0 revision
hci0:   Type: USB
        BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 64:8
        Firmware 2.105 / 97

Now my Plantronics Voyager 510 BT headset works (I have to test it
better with applications now...).

Mario :D


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-devel] Re: Developing Broadcom driver support
  2006-02-12 23:00   ` Mario
@ 2006-02-13  0:12     ` Chase Douglas
  0 siblings, 0 replies; 6+ messages in thread
From: Chase Douglas @ 2006-02-13  0:12 UTC (permalink / raw)
  To: bluez-devel

I have an iogear gb211, which has a broadcom chipset.

localhost chase # hciconfig -a
hci0:   Type: USB
        BD Address: 00:02:72:C3:C5:2E ACL MTU: 377:10 SCO MTU: 16:8
        UP RUNNING PSCAN ISCAN
        RX bytes:14392 acl:25 sco:0 events:799 errors:0
        TX bytes:4813 acl:18 sco:0 commands:752 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'BlueZ (0)'
        Class: 0xff0408
        Service Classes: Positioning, Networking, Rendering, Capturing
        Device Class: Audio/Video, Hands-free
        HCI Ver: 1.2 (0x2) HCI Rev: 0x14 LMP Ver: 1.2 (0x2) LMP Subver: 
0x309
        Manufacturer: Broadcom Corporation (15)

localhost chase # hciconfig hci0 scomtu 64:8
localhost chase # hciconfig -a
hci0:   Type: USB
        BD Address: 00:02:72:C3:C5:2E ACL MTU: 377:10 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:14392 acl:25 sco:0 events:799 errors:0
        TX bytes:4813 acl:18 sco:0 commands:752 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'BlueZ (0)'
        Class: 0xff0408
        Service Classes: Positioning, Networking, Rendering, Capturing
        Device Class: Audio/Video, Hands-free
        HCI Ver: 1.2 (0x2) HCI Rev: 0x14 LMP Ver: 1.2 (0x2) LMP Subver: 
0x309
        Manufacturer: Broadcom Corporation (15)

I can't get anything from or to my headset, although I can transmit and 
receive when using a D-Link DBT-120 rev. B4. I had also applied the 
first patch about the mtu stuff, but not the one to set the mtu by default.

Let me know if you know of anything to try.

Thanks

Mario wrote:

>2006/2/12, Brad Midgley <bmidgley@xmission.com>:
>  
>
>>We should find out exactly what that second poster "whoopie" was doing
>>to set the mtu. Apparently he was only asking if the modified patch
>>would work but he had gotten it working by using the original patch and
>>tweaking the mtu at runtime.
>>    
>>
>
>It's incredible! Without any patch to the kernel.
>
>hciconfig hci0 scomtu 64:8
>
>IT WORKS!! A nasty Broadcom BT Chipset works! :\
>
>root@legolas:~# hciconfig hci0 revision
>hci0:   Type: USB
>        BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 16:0
>        Firmware 2.105 / 97
>
>root@legolas:~# hciconfig hci0 scomtu 64:8
>
>root@legolas:~# hciconfig hci0 revision
>hci0:   Type: USB
>        BD Address: 00:10:C6:59:7A:FC ACL MTU: 377:10 SCO MTU: 64:8
>        Firmware 2.105 / 97
>
>Now my Plantronics Voyager 510 BT headset works (I have to test it
>better with applications now...).
>
>Mario :D
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://sel.as-us.falkag.net/sel?cmd_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-devel] Re: Developing Broadcom driver support
  2006-02-11 19:05 [Bluez-devel] Re: Developing Broadcom driver support Keith Bannister
  2006-02-12  6:17 ` Brad Midgley
@ 2006-02-13 17:27 ` Brad Midgley
  2006-02-15 10:02   ` Mario
  1 sibling, 1 reply; 6+ messages in thread
From: Brad Midgley @ 2006-02-13 17:27 UTC (permalink / raw)
  To: bluez-devel

Keith

Did you try something similar to Whoopie's patch that changes both mtu
and sco_cnt?

 http://bluetooth-alsa.sourceforge.net/sco-mtu.patch

Brad


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [Bluez-devel] Re: Developing Broadcom driver support
  2006-02-13 17:27 ` Brad Midgley
@ 2006-02-15 10:02   ` Mario
  0 siblings, 0 replies; 6+ messages in thread
From: Mario @ 2006-02-15 10:02 UTC (permalink / raw)
  To: bluez-devel

I have to say that usually fix "hciconfig hci0 scomtu 64:8" usually
works but sometime it stops to work. It is not so stable and I have to
use the command every time.


2006/2/13, Brad Midgley <bmidgley@xmission.com>:
>  http://bluetooth-alsa.sourceforge.net/sco-mtu.patch

This kind of patch (I've tried to use the constants 64 & 8) seems to
work not good as the command-line fix.

Mario


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-02-15 10:02 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-11 19:05 [Bluez-devel] Re: Developing Broadcom driver support Keith Bannister
2006-02-12  6:17 ` Brad Midgley
2006-02-12 23:00   ` Mario
2006-02-13  0:12     ` Chase Douglas
2006-02-13 17:27 ` Brad Midgley
2006-02-15 10:02   ` Mario

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).