* [Bluez-devel] Broadcom adapter
@ 2006-06-04 22:14 Eduardo Margallo
2006-06-05 4:41 ` Brad Midgley
0 siblings, 1 reply; 7+ messages in thread
From: Eduardo Margallo @ 2006-06-04 22:14 UTC (permalink / raw)
To: BlueZ development
Hi there,
I just bought a sweex USB BT adapter featuring a BCM2035. Everything
works fine (pand/dund), except for the SCO links to my Jabra BT205.
The symptoms are the same ones that have already been reported in this
list a couple of times: volume control works fine, but no audio comes
from/to the headset. Some white noise is audible while the channel is
open, but no bytes are transfered over SCO. I applied the patch for
the Broadcom MTU problem, but it made no difference.
I have been investigating a bit around the code. I am not familiar
with bluez and my knowledge of BT is limited. However, I found that
I'm getting -ERESTARTSYS (-512) errors in snd_card_bt_sco_thread
coming from bt_sock_recvmsg. It looks like quite an exotic error code
to me. Further I have difficulty tracking where it comes from. Is this
code normal?
I have attached a typical log with extended debug info for one of
these failed SCO connection attempts. Do you have any ideas what might
be wrong? Perhaps some pointers or suggestions to track the problem
down?
Regards,
Eduardo
sco_connect_cfm: hcon c1bb0120 bdaddr D3:73:7C:17:13:00 status 0
sco_conn_ready: conn c07985c0
sco_sock_clear_timer: sock c124ea00 state 5
sco_sock_getsockopt: sk c124ea00
sco_sock_getsockopt: sk c124ea00
sco_sock_getsockopt: mtu 64
bt_sock_poll: sock c1ce80c0, sk c1d6ca00
** Waiting for read
bt_sock_recvmsg: sock c1ce8540 sk c124ea00 len 256
** bt_sock_recvmsg: sk->sk_err = 0 before calling skb
** bt_sock_recvmsg: Error fffffe00 reading datagram from socket c124ea00
** read len -512 bytes from socket c1ce8540
** read negative length from socket c1ce8540!!!
hci_usb_rx_complete: hci0 urb c1a3a354 type 4 status 0 count 7 flags 0
__recv_frame: hci0 type 4 data c178bcc0 count 7
__recv_frame: new packet len 7
hci_usb_rx_complete: hci0 urb c1a3a354 type 4 resubmit status 0
** Waiting for read
bt_sock_recvmsg: sock c1ce8540 sk c124ea00 len 256
** bt_sock_recvmsg: sk->sk_err = 0 before calling skb
hci_usb_rx_complete: hci0 urb c1a3af54 type 2 status 0 count 21 flags 0
__recv_frame: hci0 type 2 data c1b9f800 count 21
__recv_frame: new packet len 21
hci_usb_rx_complete: hci0 urb c1a3af54 type 2 resubmit status 0
hci_usb_rx_complete: hci0 urb c1a3af54 type 2 status 0 count 6 flags 0
__recv_frame: hci0 type 2 data c1b9f800 count 6
__recv_frame: new packet len 6
hci_usb_rx_complete: hci0 urb c1a3af54 type 2 resubmit status 0
bt_sock_poll: sock c1ce80c0, sk c1d6ca00
hci_usb_send_frame: hci0 type 2 len 18
hci_usb_tx_process: hci0
hci_usb_send_bulk: hci0 skb c1d0a460 len 18
__tx_submit: hci0 urb c1a3a554 type 2
hci_usb_tx_complete: hci0 urb c1a3a554 status 0 flags 0
hci_usb_tx_process: hci0
bt_sock_poll: sock c1ce80c0, sk c1d6ca00
hci_usb_rx_complete: hci0 urb c1a3a354 type 4 status 0 count 7 flags 0
__recv_frame: hci0 type 4 data c178bcc0 count 7
__recv_frame: new packet len 7
hci_usb_rx_complete: hci0 urb c1a3a354 type 4 resubmit status 0
snd-bt-sco: playback_trigger 0
snd-bt-sco: setting playback to NULL
bt_sock_poll: sock c1ce80c0, sk c1d6ca00
snd-bt-sco: Disposing of previous socket count 3
** bt_sock_recvmsg: Error fffffe00 reading datagram from socket c124ea00
** read len -512 bytes from socket c1ce8540
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] Broadcom adapter
2006-06-04 22:14 [Bluez-devel] Broadcom adapter Eduardo Margallo
@ 2006-06-05 4:41 ` Brad Midgley
2006-06-05 10:54 ` [Bluez-devel] Belkin Eric Boon
2006-06-12 20:19 ` [Bluez-devel] Broadcom adapter Eduardo Margallo
0 siblings, 2 replies; 7+ messages in thread
From: Brad Midgley @ 2006-06-05 4:41 UTC (permalink / raw)
To: BlueZ development
Eduardo
> I have been investigating a bit around the code. I am not familiar
> with bluez and my knowledge of BT is limited. However, I found that
> I'm getting -ERESTARTSYS (-512) errors in snd_card_bt_sco_thread
> coming from bt_sock_recvmsg. It looks like quite an exotic error code
> to me. Further I have difficulty tracking where it comes from. Is this
> code normal?
I haven't dug into it like you have, but it's not unexpected to see the
error happen there. We have no sco data arriving on hci, so recvmsg must
be interrupted by a signal instead.
I suspect broadcom has an equivalent to csr's nonvolatile setting for
hci vs. pcm audio delivery. Apparently no one has good enough docs to
know for sure. It would help if we knew that dongle had been
successfully used for sco under windows.
Brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] Belkin
2006-06-05 4:41 ` Brad Midgley
@ 2006-06-05 10:54 ` Eric Boon
2006-06-05 11:53 ` Eric Boon
2006-06-12 20:19 ` [Bluez-devel] Broadcom adapter Eduardo Margallo
1 sibling, 1 reply; 7+ messages in thread
From: Eric Boon @ 2006-06-05 10:54 UTC (permalink / raw)
To: BlueZ development
Hello bluez-dev'ers
I recently bought a Belkin USB BT-stick and stumbled upon the infamous
Broadcom problem: everything seems to work fine, but no audio :-/ I'm
running Debian testing, on a P3@1GHz, followed the installation
instructions on http://bluetooth-alsa.sourceforge.net/ and
http://wiki.ubuntuusers.de/Bluetooth/Headset. The stick sits directly
in the PC, no USB hub used.
The Belkin stick is apparently a Broadcom device -- see hciconfig
output. I found a reference to 'F8T013' on the box, which gave me some
hope that fiddling with the SCO MTU value could solve my problem. Helas,
no joy...
I did not apply the kernel patch, as suggested on the bluetooth-alsa
website, but manually set the SCO MTU to 256:8 using 'hciconfig scomtu
256:8'. The original values were '64:0'.
Does that make any difference? Should I try different values? If
possible I'd rather avoid patching the kernel :-/
Any suggestions to getting this thing to work are welcome!
The headset is a Logitech 'Mobile Freedom' (HS02-V08)
Many thanx in advance,
Eric
(PS. Is there also a bluez IRC channel somewhere? :-))
eric@morpheus:~$ uname -a
Linux morpheus 2.6.15-1-686 #2 Mon Mar 6 15:27:08 UTC 2006 i686 GNU/Linux
eric@morpheus:~$ sudo hciconfig -a
hci0: Type: USB
BD Address: 00:00:3A:6A:80:1D ACL MTU: 1017:8 SCO MTU: 256:8
UP RUNNING PSCAN ISCAN
RX bytes:1115011 acl:25 sco:21838 events:54 errors:0
TX bytes:802 acl:21 sco:0 commands:25 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'morpheus-0'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x2073 LMP Ver: 2.0 (0x3) LMP
Subver: 0x4127
Manufacturer: Broadcom Corporation (15)
eric@morpheus:~$ sudo hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:00:3A:6A:80:1D ACL MTU: 1017:8 SCO MTU: 256:8
Firmware 8307.65 / 39
eric@morpheus:~$ sudo hcitool info 00:0D:44:3B:A9:35
Requesting information ...
BD Address: 00:0D:44:3B:A9:35
Device Name: Logitech HS02-V08
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>
Output of btsco when trying to play a sound file:
eric@morpheus:~$ btsco -v 00:0D:44:3B:A9:35
btsco v0.42
Device is 1:0
Voice setting: 0x0060
RFCOMM channel 1 connected
Using interface hci0
speaker volume: 13 mic volume: 14
i/o needed: connecting sco...
connected SCO channel
Done setting sco fd
recieved AT+VGS=13
Sending up speaker change 13
speaker volume: 14 mic volume: 14
speaker volume: 14 mic volume: 14
driver is not in use
disconnected SCO channel
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] Belkin
2006-06-05 10:54 ` [Bluez-devel] Belkin Eric Boon
@ 2006-06-05 11:53 ` Eric Boon
2006-06-05 13:26 ` Eric Boon
0 siblings, 1 reply; 7+ messages in thread
From: Eric Boon @ 2006-06-05 11:53 UTC (permalink / raw)
To: BlueZ development
Hello again,
I wrote:
> I recently bought a Belkin USB BT-stick and stumbled upon the infamous
> Broadcom problem: everything seems to work fine, but no audio :-/
> [...]
I just tested the combination (Belkin USB BT stick + Logitech Headset on
my WinXP laptop, and everything runs smoothly over there...
Eric
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] Belkin
2006-06-05 11:53 ` Eric Boon
@ 2006-06-05 13:26 ` Eric Boon
0 siblings, 0 replies; 7+ messages in thread
From: Eric Boon @ 2006-06-05 13:26 UTC (permalink / raw)
To: BlueZ development
And another hello :-)
I applied the patch as described in
http://www.ussg.iu.edu/hypermail/linux/kernel/0601.1/1679.html
and the device is now working, although I get numerous buffer
under-runs when the CPU has a noticeable load...
(E.g. upon opening an application.)
I'd still rather work with a non-patched kernel, so other options
are welcome!
Greetz,
Eric
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] Broadcom adapter
2006-06-05 4:41 ` Brad Midgley
2006-06-05 10:54 ` [Bluez-devel] Belkin Eric Boon
@ 2006-06-12 20:19 ` Eduardo Margallo
2006-06-17 22:00 ` Eduardo Margallo
1 sibling, 1 reply; 7+ messages in thread
From: Eduardo Margallo @ 2006-06-12 20:19 UTC (permalink / raw)
To: BlueZ development
Hi Brad,
well, in fact using the Broadcom Adapter under Windows with
BlueSoleil, I get a perfect audio connection. After pairing, I just
have to press the top button on my Jabra Headset and voil=E0. I have
attached the HCI communication (monitoring usb traffic and decoding
the packages in python) between both devices.
This sequence started when I pressed the connect button with both
devices paired. I stopped it after SCO traffic was going on. If you
need a different connection sequence, I can provide it. It is not a
lot of work now.
Cheers,
Eduardo
------------------------------------------------
UP EVT: Connection Request Event Data =3D D3 73 7C 17 13 00 0C 04 20 01
BD_ADDR 0x13177C73D3 Class_of_Device 0x20040C Link_Type 0x1
DOWN CMD: Accept Connection Request Command Data =3D 07 D3 73 7C 17 13 00 00
BD_ADDR 0x13177C73D3 Role 0x0 Remaining Data: [0]
UP EVT: Command Status Event Data =3D 00 01 09 04
Status 0x0 Num_HCI_Command_Packets 0x1 Command_Opcode 0x409
UP CMD: Accept Connection Request Command Data =3D 07 D3 73 7C 17 13 00
00 20 00 00 00 00 00 0A 00
BD_ADDR 0x13177C73D3 Role 0x0 Remaining Data: [0, 32, 0, 0,
0, 0, 0, 10, 0]
UP EVT: Role Change Event Data =3D 00 D3 73 7C 17 13 00 00
Status 0x0 BD_ADDR 0x13177C73D3 New_Role 0x0
UP EVT: Link Key Request Event Data =3D D3 73 7C 17 13 00
BD_ADDR 0x13177C73D3
DOWN CMD: Link Key Request Reply Command Data =3D 16 D3 73 7C 17 13 00
13 80 BA 19 E9 DC B3 A0 E5 8D A3 63 91 A1 BB E9
BD_ADDR 0x13177C73D3 Link_Key 0xE9BBA19163A38DE5A0B3DCE919BA8013
UP CMD: Link Key Request Reply Command Data =3D 16 D3 73 7C 17 13 00 13
80 BA 19 E9 DC B3 A0 E5 8D A3 63 91 A1 BB E9 20 00 00 00 00 00 19 00
BD_ADDR 0x13177C73D3 Link_Key
0xE9BBA19163A38DE5A0B3DCE919BA8013 Remaining Data: [32, 0, 0, 0, 0,
0, 25, 0]
UP EVT: Command Complete Event Data =3D 01 0B 04 00 D3 73 7C 17 13 00
Num_HCI_Command_Packets 0x1 Command_Opcode 0x0 Remaining Data:
[1, 11, 4, 0, 211, 115, 124, 23, 19, 0]
UP EVT: Connection Complete Event Data =3D 00 07 00 D3 73 7C 17 13 00 01 01
Status 0x0 Connection_Handle 0x7 BD_ADDR 0x13177C73D3
Link_Type 0x1 Encryption_Mode 0x1
DOWN CMD: Write Link Policy Settings Command Data =3D 04 07 00 07 00
Remaining Data: [7, 0, 7, 0]
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 02 01 04 00 01 00 61 00
L2CAP len=3D8 ch=3D1 Command=3DConnection request PSM 0x1 Src ID 0x=
61
UP CMD: Write Link Policy Settings Command Data =3D 04 07 00 07 00 20 00
00 00 00 00 07 00
Remaining Data: [7, 0, 7, 0, 32, 0, 0, 0, 0, 0, 7, 0]
UP EVT: Command Complete Event Data =3D 01 0D 08 00 07 00
Num_HCI_Command_Packets 0x1 Command_Opcode 0x0 Remaining Data:
[1, 13, 8, 0, 7, 0]
UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 03 01 08 00 42 00 61 00 0=
0 00 00 00
L2CAP len=3D12 ch=3D1 Command=3DConnection response Dest ID 0x42 Src
ID 0x61 Result 0x0 Status 0x0
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 04 04 04 00 61 00 00 00
L2CAP len=3D8 ch=3D1 Command=3DConfigure request Dest ID 0x61 Flags=
0x0
DOWN CMD: Write Link Supervision Timeout Command Data =3D 04 07 00 00 7D
Remaining Data: [7, 0, 0, 125]
UP EVT: Command Complete Event Data =3D 01 37 0C 00 07 00
Num_HCI_Command_Packets 0x1 Command_Opcode 0x0 Remaining Data:
[1, 55, 12, 0, 7, 0]
UP CMD: Write Link Supervision Timeout Command Data =3D 04 07 00 00 7D
20 00 00 00 00 00 07 00
Remaining Data: [7, 0, 0, 125, 32, 0, 0, 0, 0, 0, 7, 0]
DOWN CMD: Read Clock Offset Command Data =3D 02 07 00
Remaining Data: [7, 0]
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 02 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x2
UP EVT: Command Status Event Data =3D 00 01 1F 04
Status 0x0 Num_HCI_Command_Packets 0x1 Command_Opcode 0x41F
UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00
UP CMD: Read Clock Offset Command Data =3D 02 07 00 20 00 00 00 00 00 05 00
Remaining Data: [7, 0, 32, 0, 0, 0, 0, 0, 5, 0]
UP ACL: conn=3D7 flags=3D 1 Data =3D 04 02 08 00 42 00 00 00 01 02 30 00
UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 01 00 05 02 06 00 61 00 00 00 0=
0 00
L2CAP len=3D10 ch=3D1 Command=3DConfigure response Reason 0x61 Data
0x0 Remaining Data: [0, 0]
UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 01 00 05 04 06 00 42 00 00 00 0=
0 00
L2CAP len=3D10 ch=3D1 Command=3DConfigure response Reason 0x42 Data
0x0 Remaining Data: [0, 0]
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP EVT: Read Clock Offset Complete Event Data =3D 00 07 00 FE 0B
Status 0x0 Connection_Handle 0x7 Clock_Offset 0xBFE
UP ACL: conn=3D7 flags=3D 2 Data =3D 0f 00 42 00
UP ACL: conn=3D7 flags=3D 1 Data =3D 02 00 01 00 0a 35 05 1a 00 00 11 12 0=
0 28 00
UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 61 00 03 00 01 00 09 00 01 00 01
00 01 00 13 00
L2CAP len=3D2 ch=3D1 Command=3DInformation request Info Type 0x0
Remaining Data: [17, 18, 0, 40, 0, 14, 0, 97, 0, 3, 0, 1, 0, 9, 0, 1,
0, 1, 0, 1, 0, 19, 0]
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 11 00 42 00 04 00 02 00 0c 00 01 00 13
00 26 35 03 09 00 04 00
UP ACL: conn=3D7 flags=3D 2 Data =3D 1b 00 61 00 05 00 02 00 16 00 13 35 11
09 00 04 35 0c 35 03 19 01 00 35 05 19 00 03 08 07 00
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 02 03 04 00 03 00 62 00
L2CAP len=3D8 ch=3D1 Command=3DConnection request PSM 0x3 Src ID 0x=
62
UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 03 03 08 00 43 00 62 00 0=
0 00 00 00
L2CAP len=3D12 ch=3D1 Command=3DConnection response Dest ID 0x43 Src
ID 0x62 Result 0x0 Status 0x0
UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 04 05 08 00 62 00 00 00 0=
1 02 ae 06
L2CAP len=3D12 ch=3D1 Command=3DConfigure request Dest ID 0x62 Flags
0x0 Remaining Data: [1, 2, 174, 6]
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 02 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x2
UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 04 04 08 00 43 00 00 00 0=
1 02 84 00
L2CAP len=3D12 ch=3D1 Command=3DConfigure request Dest ID 0x43 Flags
0x0 Remaining Data: [1, 2, 132, 0]
UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 01 00 05 04 06 00 62 00 00 00 0=
0 00
L2CAP len=3D10 ch=3D1 Command=3DConfigure response Reason 0x62 Data
0x0 Remaining Data: [0, 0]
UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 01 00 05 05 0a 00 43 00 00 00 00
00 01 02 84 00
L2CAP len=3D14 ch=3D1 Command=3DConfigure response Reason 0x43 Data
0x0 Remaining Data: [0, 0, 1, 2, 132, 0]
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 43 00 03 3f 01 1c
UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 62 00 03 73 01 d7
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 43 00 03 ef 15 83 11 0e f0 00 00
7e 00 00 00 70
UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 62 00 01 ef 15 81 11 0e e0 00 00
7e 00 00 07 aa
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 43 00 3b 3f 01 06
UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 62 00 3b 73 01 cd
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 62 00 01 ef 09 e3 05 3b 8d aa
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 02 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x2
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 43 00 03 ef 09 e1 05 3b 8d 70
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 43 00 03 ef 09 e3 05 3b 0d 70
UP ACL: conn=3D7 flags=3D 2 Data =3D 05 00 43 00 3b ff 01 0f b9
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 62 00 01 ef 09 e1 05 3b 0d aa
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 06 05 04 00 42 00 61 00
L2CAP len=3D8 ch=3D1 Command=3DDisconnection request Src ID 0x42
Flags 0x61 Result 0x0 Config 0x0
UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 07 05 04 00 42 00 61 00
L2CAP len=3D8 ch=3D1 Command=3DDisconnection response Dest ID 0x42
Src ID 0x61 Result 0x0 Status 0x0
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP ACL: conn=3D7 flags=3D 2 Data =3D 10 00 43 00 3b ef 19 41 54 2b 43 4b 50
44 3d 32 30 30 0d a5
UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 62 00 39 ef 0d 0d 0a 4f 4b 0d 0=
a 7f
DOWN CMD: Add SCO Connection Command Data =3D 04 07 00 E0 00
Connection_Handle 0x7 Packet_Type 0xE0
UP CMD: Add SCO Connection Command Data =3D 04 07 00 E0 00 20 00 00 00 00 0=
0 07 00
Connection_Handle 0x7 Packet_Type 0xE0 Remaining Data: [32,
0, 0, 0, 0, 0, 7, 0]
UP EVT: Command Status Event Data =3D 00 01 07 04
Status 0x0 Num_HCI_Command_Packets 0x1 Command_Opcode 0x407
UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
Number_of_Handles 0x1 Connection_Handle[0] 0x7
HC_Num_Of_Completed_Packets[0] 0x1
UP EVT: Connection Complete Event Data =3D 00 01 00 D3 73 7C 17 13 00 00 01
Status 0x0 Connection_Handle 0x1 BD_ADDR 0x13177C73D3
Link_Type 0x0 Encryption_Mode 0x1
DOWN SCO: 00 00 00 00 00 00 00 00 40 9d 55 80 40 9d 55 80 ...
DOWN SCO: 00 00 00 00 00 00 00 00 40 94 55 80 00 e1 3f 84 ...
UP SCO: 08 00 08 00 20 00 20 00 18 00 20 00 18 00 30 00 ...
DOWN SCO: 08 00 08 00 20 00 20 00 18 00 20 00 18 00 30 00 ...
UP SCO: 00 00 00 30 00 50 00 38 00 38 00 38 00 38 00 30 ...
DOWN SCO: 00 00 00 30 00 50 00 38 00 38 00 38 00 38 00 30 ...
UP SCO: 00 18 00 30 00 48 00 40 00 20 00 40 00 40 00 20 ...
DOWN SCO: 00 18 00 30 00 48 00 40 00 20 00 40 00 40 00 20 ...
UP SCO: 00 10 00 30 00 40 00 38 00 18 00 30 00 30 00 28 ...
DOWN SCO: 00 10 00 30 00 40 00 38 00 18 00 30 00 30 00 28 ...
UP SCO: 00 18 00 38 00 48 00 48 00 38 00 38 00 30 00 20 ...
DOWN SCO: 00 18 00 38 00 48 00 48 00 38 00 38 00 30 00 20 ...
UP SCO: 00 18 00 40 00 60 00 30 00 10 00 48 00 38 00 20 ...
DOWN SCO: 00 18 00 40 00 60 00 30 00 10 00 48 00 38 00 20 ...
UP SCO: 00 10 00 30 00 38 00 40 00 38 00 30 00 30 00 20 ...
DOWN SCO: 00 10 00 30 00 38 00 40 00 38 00 30 00 30 00 20 ...
UP SCO: 00 10 00 28 00 30 00 40 00 38 00 30 00 30 00 28 ...
DOWN SCO: 00 10 00 28 00 30 00 40 00 38 00 30 00 30 00 28 ...
UP SCO: 00 10 00 38 00 48 00 38 00 28 00 38 00 30 00 20 ...
DOWN SCO: 00 10 00 38 00 48 00 38 00 28 00 38 00 30 00 20 ...
UP SCO: 00 18 00 40 00 50 00 48 00 38 00 38 00 38 00 28 ...
DOWN SCO: 00 18 00 40 00 50 00 48 00 38 00 38 00 38 00 28 ...
UP SCO: 00 10 00 40 00 50 00 48 00 28 00 30 00 30 00 28 ...
DOWN SCO: 00 10 00 40 00 50 00 48 00 28 00 30 00 30 00 28 ...
UP SCO: 00 10 00 40 00 58 00 38 00 20 00 38 00 30 00 30 ...
DOWN SCO: 00 10 00 40 00 58 00 38 00 20 00 38 00 30 00 30 ...
UP EVT: Connection Packet Type Changed Event Data =3D 00 01 00 80 00
Status 0x0 Connection_Handle 0x1 Packet_Type 0x80
UP SCO: 38 00 30 00 40 00 20 00 28 00 40 00 30 00 40 00 ...
DOWN SCO: 38 00 30 00 40 00 20 00 28 00 40 00 30 00 40 00 ...
UP SCO: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...
DOWN SCO: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...
UP SCO: 00 30 00 30 00 30 00 28 00 38 00 30 00 30 00 28 ...
DOWN SCO: 00 30 00 30 00 30 00 28 00 38 00 30 00 30 00 28 ...
UP SCO: 00 48 00 30 00 18 00 28 00 38 00 20 00 28 00 18 ...
DOWN SCO: 00 48 00 30 00 18 00 28 00 38 00 20 00 28 00 18 ...
UP SCO: 00 38 00 40 00 30 00 30 00 30 00 20 00 30 00 28 ...
DOWN SCO: 00 38 00 40 00 30 00 30 00 30 00 20 00 30 00 28 ...
UP ACL: conn=3D7 flags=3D 2 Data =3D 0f 00 43 00 3b ff 15 01 41 54 2b 56 47
53 3d 31 31
UP ACL: conn=3D7 flags=3D 1 Data =3D 0d b9
UP SCO: 00 30 00 40 00 28 00 20 00 40 00 30 00 20 00 18 ...
DOWN SCO: 00 30 00 40 00 28 00 20 00 40 00 30 00 20 00 18 ...
2006/6/5, Brad Midgley <bmidgley@xmission.com>:
> Eduardo
>
> > I have been investigating a bit around the code. I am not familiar
> > with bluez and my knowledge of BT is limited. However, I found that
> > I'm getting -ERESTARTSYS (-512) errors in snd_card_bt_sco_thread
> > coming from bt_sock_recvmsg. It looks like quite an exotic error code
> > to me. Further I have difficulty tracking where it comes from. Is this
> > code normal?
>
> I haven't dug into it like you have, but it's not unexpected to see the
> error happen there. We have no sco data arriving on hci, so recvmsg must
> be interrupted by a signal instead.
>
> I suspect broadcom has an equivalent to csr's nonvolatile setting for
> hci vs. pcm audio delivery. Apparently no one has good enough docs to
> know for sure. It would help if we knew that dongle had been
> successfully used for sco under windows.
>
> Brad
>
>
>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] Broadcom adapter
2006-06-12 20:19 ` [Bluez-devel] Broadcom adapter Eduardo Margallo
@ 2006-06-17 22:00 ` Eduardo Margallo
0 siblings, 0 replies; 7+ messages in thread
From: Eduardo Margallo @ 2006-06-17 22:00 UTC (permalink / raw)
To: BlueZ development
Hi everyone,
1. I've been studying the pairing and connection sequences both in
Windows and Linux and haven't been able to spot any glitch up to now.
Do you have any suggestions about what I should look at? Where is the
"csr's nonvolatile setting for
hci vs. pcm audio delivery" in the code? Are some pointers available?
2. On the other hand, I have seen that HCI_BROKEN_ISOC is defined for
Broadcom 0x0a5c 0x200a adapters, what leads to lack of ISOC transfers
in the module. If I understood it correctly, this immediately implies
no SCO. I have tried to enable isochronous transfers, but it obviously
does not work. The cpu seems to be trapped in interrupts most of the
time (>95%hi) and I get around 20 of these messages in my kern.log per
second:
Jun 17 22:52:49 babosa kernel: hci_usb_rx_complete: hci0 urb c1cfb414
type 3 resubmit status 0
Jun 17 22:52:49 babosa kernel: hci_usb_rx_complete: hci0 urb c1cfb814
type 3 status 0 count 0 flags 2
I would say that the lack of ISOC transfers is the real cause for
non-working SCO channels. Is this correct?
Kind regards,
Eduardo
2006/6/12, Eduardo Margallo < eduardo.margallo@gmail.com>:
> Hi Brad,
>
> well, in fact using the Broadcom Adapter under Windows with
> BlueSoleil, I get a perfect audio connection. After pairing, I just
> have to press the top button on my Jabra Headset and voil=E0. I have
> attached the HCI communication (monitoring usb traffic and decoding
> the packages in python) between both devices.
>
> This sequence started when I pressed the connect button with both
> devices paired. I stopped it after SCO traffic was going on. If you
> need a different connection sequence, I can provide it. It is not a
> lot of work now.
>
> Cheers,
>
> Eduardo
>
> ------------------------------------------------
> UP EVT: Connection Request Event Data =3D D3 73 7C 17 13 00 0C 04 20 01
> BD_ADDR 0x13177C73D3 Class_of_Device 0x20040C Link_Type 0x1
> DOWN CMD: Accept Connection Request Command Data =3D 07 D3 73 7C 17 13 00=
00
> BD_ADDR 0x13177C73D3 Role 0x0 Remaining Data: [0]
> UP EVT: Command Status Event Data =3D 00 01 09 04
> Status 0x0 Num_HCI_Command_Packets 0x1 Command_Opcode 0x409
> UP CMD: Accept Connection Request Command Data =3D 07 D3 73 7C 17 13 00
> 00 20 00 00 00 00 00 0A 00
> BD_ADDR 0x13177C73D3 Role 0x0 Remaining Data: [0, 32, 0, 0,
> 0, 0, 0, 10, 0]
> UP EVT: Role Change Event Data =3D 00 D3 73 7C 17 13 00 00
> Status 0x0 BD_ADDR 0x13177C73D3 New_Role 0x0
> UP EVT: Link Key Request Event Data =3D D3 73 7C 17 13 00
> BD_ADDR 0x13177C73D3
> DOWN CMD: Link Key Request Reply Command Data =3D 16 D3 73 7C 17 13 00
> 13 80 BA 19 E9 DC B3 A0 E5 8D A3 63 91 A1 BB E9
> BD_ADDR 0x13177C73D3 Link_Key 0xE9BBA19163A38DE5A0B3DCE919BA8013
> UP CMD: Link Key Request Reply Command Data =3D 16 D3 73 7C 17 13 00 13
> 80 BA 19 E9 DC B3 A0 E5 8D A3 63 91 A1 BB E9 20 00 00 00 00 00 19 00
> BD_ADDR 0x13177C73D3 Link_Key
> 0xE9BBA19163A38DE5A0B3DCE919BA8013 Remaining Data: [32, 0, 0, 0, 0,
> 0, 25, 0]
> UP EVT: Command Complete Event Data =3D 01 0B 04 00 D3 73 7C 17 13 00
> Num_HCI_Command_Packets 0x1 Command_Opcode 0x0 Remaining Data:
> [1, 11, 4, 0, 211, 115, 124, 23, 19, 0]
> UP EVT: Connection Complete Event Data =3D 00 07 00 D3 73 7C 17 13 00 01 =
01
> Status 0x0 Connection_Handle 0x7 BD_ADDR 0x13177C73D3
> Link_Type 0x1 Encryption_Mode 0x1
> DOWN CMD: Write Link Policy Settings Command Data =3D 04 07 00 07 00
> Remaining Data: [7, 0, 7, 0]
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 02 01 04 00 01 00 61 00
> L2CAP len=3D8 ch=3D1 Command=3DConnection request PSM 0x1 Src ID =
0x61
> UP CMD: Write Link Policy Settings Command Data =3D 04 07 00 07 00 20 00
> 00 00 00 00 07 00
> Remaining Data: [7, 0, 7, 0, 32, 0, 0, 0, 0, 0, 7, 0]
> UP EVT: Command Complete Event Data =3D 01 0D 08 00 07 00
> Num_HCI_Command_Packets 0x1 Command_Opcode 0x0 Remaining Data:
> [1, 13, 8, 0, 7, 0]
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 03 01 08 00 42 00 61 00=
00 00 00 00
> L2CAP len=3D12 ch=3D1 Command=3DConnection response Dest ID 0x42 =
Src
> ID 0x61 Result 0x0 Status 0x0
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 04 04 04 00 61 00 00 00
> L2CAP len=3D8 ch=3D1 Command=3DConfigure request Dest ID 0x61 Fla=
gs 0x0
> DOWN CMD: Write Link Supervision Timeout Command Data =3D 04 07 00 00 7D
> Remaining Data: [7, 0, 0, 125]
> UP EVT: Command Complete Event Data =3D 01 37 0C 00 07 00
> Num_HCI_Command_Packets 0x1 Command_Opcode 0x0 Remaining Data:
> [1, 55, 12, 0, 7, 0]
> UP CMD: Write Link Supervision Timeout Command Data =3D 04 07 00 00 7D
> 20 00 00 00 00 00 07 00
> Remaining Data: [7, 0, 0, 125, 32, 0, 0, 0, 0, 0, 7, 0]
> DOWN CMD: Read Clock Offset Command Data =3D 02 07 00
> Remaining Data: [7, 0]
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 02 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x2
> UP EVT: Command Status Event Data =3D 00 01 1F 04
> Status 0x0 Num_HCI_Command_Packets 0x1 Command_Opcode 0x41F
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00
> UP CMD: Read Clock Offset Command Data =3D 02 07 00 20 00 00 00 00 00 05 =
00
> Remaining Data: [7, 0, 32, 0, 0, 0, 0, 0, 5, 0]
> UP ACL: conn=3D7 flags=3D 1 Data =3D 04 02 08 00 42 00 00 00 01 02 30 00
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 01 00 05 02 06 00 61 00 00 00=
00 00
> L2CAP len=3D10 ch=3D1 Command=3DConfigure response Reason 0x61 Da=
ta
> 0x0 Remaining Data: [0, 0]
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 01 00 05 04 06 00 42 00 00 00=
00 00
> L2CAP len=3D10 ch=3D1 Command=3DConfigure response Reason 0x42 Da=
ta
> 0x0 Remaining Data: [0, 0]
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP EVT: Read Clock Offset Complete Event Data =3D 00 07 00 FE 0B
> Status 0x0 Connection_Handle 0x7 Clock_Offset 0xBFE
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0f 00 42 00
> UP ACL: conn=3D7 flags=3D 1 Data =3D 02 00 01 00 0a 35 05 1a 00 00 11 12=
00 28 00
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 61 00 03 00 01 00 09 00 01 00=
01
> 00 01 00 13 00
> L2CAP len=3D2 ch=3D1 Command=3DInformation request Info Type 0x0
> Remaining Data: [17, 18, 0, 40, 0, 14, 0, 97, 0, 3, 0, 1, 0, 9, 0, 1,
> 0, 1, 0, 1, 0, 19, 0]
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 11 00 42 00 04 00 02 00 0c 00 01 00=
13
> 00 26 35 03 09 00 04 00
> UP ACL: conn=3D7 flags=3D 2 Data =3D 1b 00 61 00 05 00 02 00 16 00 13 35=
11
> 09 00 04 35 0c 35 03 19 01 00 35 05 19 00 03 08 07 00
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 02 03 04 00 03 00 62 00
> L2CAP len=3D8 ch=3D1 Command=3DConnection request PSM 0x3 Src ID =
0x62
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 03 03 08 00 43 00 62 00=
00 00 00 00
> L2CAP len=3D12 ch=3D1 Command=3DConnection response Dest ID 0x43 =
Src
> ID 0x62 Result 0x0 Status 0x0
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 04 05 08 00 62 00 00 00=
01 02 ae 06
> L2CAP len=3D12 ch=3D1 Command=3DConfigure request Dest ID 0x62 Fl=
ags
> 0x0 Remaining Data: [1, 2, 174, 6]
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 02 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x2
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0c 00 01 00 04 04 08 00 43 00 00 00=
01 02 84 00
> L2CAP len=3D12 ch=3D1 Command=3DConfigure request Dest ID 0x43 Fl=
ags
> 0x0 Remaining Data: [1, 2, 132, 0]
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 01 00 05 04 06 00 62 00 00 00=
00 00
> L2CAP len=3D10 ch=3D1 Command=3DConfigure response Reason 0x62 Da=
ta
> 0x0 Remaining Data: [0, 0]
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 01 00 05 05 0a 00 43 00 00 00=
00
> 00 01 02 84 00
> L2CAP len=3D14 ch=3D1 Command=3DConfigure response Reason 0x43 Da=
ta
> 0x0 Remaining Data: [0, 0, 1, 2, 132, 0]
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 43 00 03 3f 01 1c
> UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 62 00 03 73 01 d7
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 43 00 03 ef 15 83 11 0e f0 00=
00
> 7e 00 00 00 70
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0e 00 62 00 01 ef 15 81 11 0e e0 00=
00
> 7e 00 00 07 aa
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 43 00 3b 3f 01 06
> UP ACL: conn=3D7 flags=3D 2 Data =3D 04 00 62 00 3b 73 01 cd
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 62 00 01 ef 09 e3 05 3b 8d aa
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 02 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x2
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 43 00 03 ef 09 e1 05 3b 8d 70
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 43 00 03 ef 09 e3 05 3b 0d 70
> UP ACL: conn=3D7 flags=3D 2 Data =3D 05 00 43 00 3b ff 01 0f b9
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 62 00 01 ef 09 e1 05 3b 0d aa
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 06 05 04 00 42 00 61 00
> L2CAP len=3D8 ch=3D1 Command=3DDisconnection request Src ID 0x42
> Flags 0x61 Result 0x0 Config 0x0
> UP ACL: conn=3D7 flags=3D 2 Data =3D 08 00 01 00 07 05 04 00 42 00 61 00
> L2CAP len=3D8 ch=3D1 Command=3DDisconnection response Dest ID 0x42
> Src ID 0x61 Result 0x0 Status 0x0
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP ACL: conn=3D7 flags=3D 2 Data =3D 10 00 43 00 3b ef 19 41 54 2b 43 4b=
50
> 44 3d 32 30 30 0d a5
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0a 00 62 00 39 ef 0d 0d 0a 4f 4b 0d=
0a 7f
> DOWN CMD: Add SCO Connection Command Data =3D 04 07 00 E0 00
> Connection_Handle 0x7 Packet_Type 0xE0
> UP CMD: Add SCO Connection Command Data =3D 04 07 00 E0 00 20 00 00 00 00=
00 07 00
> Connection_Handle 0x7 Packet_Type 0xE0 Remaining Data: [32,
> 0, 0, 0, 0, 0, 7, 0]
> UP EVT: Command Status Event Data =3D 00 01 07 04
> Status 0x0 Num_HCI_Command_Packets 0x1 Command_Opcode 0x407
> UP EVT: Number Of Completed Packets Event Data =3D 01 07 00 01 00
> Number_of_Handles 0x1 Connection_Handle[0] 0x7
> HC_Num_Of_Completed_Packets[0] 0x1
> UP EVT: Connection Complete Event Data =3D 00 01 00 D3 73 7C 17 13 00 00 =
01
> Status 0x0 Connection_Handle 0x1 BD_ADDR 0x13177C73D3
> Link_Type 0x0 Encryption_Mode 0x1
> DOWN SCO: 00 00 00 00 00 00 00 00 40 9d 55 80 40 9d 55 80 ...
> DOWN SCO: 00 00 00 00 00 00 00 00 40 94 55 80 00 e1 3f 84 ...
> UP SCO: 08 00 08 00 20 00 20 00 18 00 20 00 18 00 30 00 ...
> DOWN SCO: 08 00 08 00 20 00 20 00 18 00 20 00 18 00 30 00 ...
> UP SCO: 00 00 00 30 00 50 00 38 00 38 00 38 00 38 00 30 ...
> DOWN SCO: 00 00 00 30 00 50 00 38 00 38 00 38 00 38 00 30 ...
> UP SCO: 00 18 00 30 00 48 00 40 00 20 00 40 00 40 00 20 ...
> DOWN SCO: 00 18 00 30 00 48 00 40 00 20 00 40 00 40 00 20 ...
> UP SCO: 00 10 00 30 00 40 00 38 00 18 00 30 00 30 00 28 ...
> DOWN SCO: 00 10 00 30 00 40 00 38 00 18 00 30 00 30 00 28 ...
> UP SCO: 00 18 00 38 00 48 00 48 00 38 00 38 00 30 00 20 ...
> DOWN SCO: 00 18 00 38 00 48 00 48 00 38 00 38 00 30 00 20 ...
> UP SCO: 00 18 00 40 00 60 00 30 00 10 00 48 00 38 00 20 ...
> DOWN SCO: 00 18 00 40 00 60 00 30 00 10 00 48 00 38 00 20 ...
> UP SCO: 00 10 00 30 00 38 00 40 00 38 00 30 00 30 00 20 ...
> DOWN SCO: 00 10 00 30 00 38 00 40 00 38 00 30 00 30 00 20 ...
> UP SCO: 00 10 00 28 00 30 00 40 00 38 00 30 00 30 00 28 ...
> DOWN SCO: 00 10 00 28 00 30 00 40 00 38 00 30 00 30 00 28 ...
> UP SCO: 00 10 00 38 00 48 00 38 00 28 00 38 00 30 00 20 ...
> DOWN SCO: 00 10 00 38 00 48 00 38 00 28 00 38 00 30 00 20 ...
> UP SCO: 00 18 00 40 00 50 00 48 00 38 00 38 00 38 00 28 ...
> DOWN SCO: 00 18 00 40 00 50 00 48 00 38 00 38 00 38 00 28 ...
> UP SCO: 00 10 00 40 00 50 00 48 00 28 00 30 00 30 00 28 ...
> DOWN SCO: 00 10 00 40 00 50 00 48 00 28 00 30 00 30 00 28 ...
> UP SCO: 00 10 00 40 00 58 00 38 00 20 00 38 00 30 00 30 ...
> DOWN SCO: 00 10 00 40 00 58 00 38 00 20 00 38 00 30 00 30 ...
> UP EVT: Connection Packet Type Changed Event Data =3D 00 01 00 80 00
> Status 0x0 Connection_Handle 0x1 Packet_Type 0x80
> UP SCO: 38 00 30 00 40 00 20 00 28 00 40 00 30 00 40 00 ...
> DOWN SCO: 38 00 30 00 40 00 20 00 28 00 40 00 30 00 40 00 ...
> UP SCO: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...
> DOWN SCO: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...
> UP SCO: 00 30 00 30 00 30 00 28 00 38 00 30 00 30 00 28 ...
> DOWN SCO: 00 30 00 30 00 30 00 28 00 38 00 30 00 30 00 28 ...
> UP SCO: 00 48 00 30 00 18 00 28 00 38 00 20 00 28 00 18 ...
> DOWN SCO: 00 48 00 30 00 18 00 28 00 38 00 20 00 28 00 18 ...
> UP SCO: 00 38 00 40 00 30 00 30 00 30 00 20 00 30 00 28 ...
> DOWN SCO: 00 38 00 40 00 30 00 30 00 30 00 20 00 30 00 28 ...
> UP ACL: conn=3D7 flags=3D 2 Data =3D 0f 00 43 00 3b ff 15 01 41 54 2b 56=
47
> 53 3d 31 31
> UP ACL: conn=3D7 flags=3D 1 Data =3D 0d b9
> UP SCO: 00 30 00 40 00 28 00 20 00 40 00 30 00 20 00 18 ...
> DOWN SCO: 00 30 00 40 00 28 00 20 00 40 00 30 00 20 00 18 ...
>
>
>
>
> 2006/6/5, Brad Midgley < bmidgley@xmission.com>:
> > Eduardo
> >
> > > I have been investigating a bit around the code. I am not familiar
> > > with bluez and my knowledge of BT is limited. However, I found that
> > > I'm getting -ERESTARTSYS (-512) errors in snd_card_bt_sco_thread
> > > coming from bt_sock_recvmsg. It looks like quite an exotic error code
> > > to me. Further I have difficulty tracking where it comes from. Is this
> > > code normal?
> >
> > I haven't dug into it like you have, but it's not unexpected to see the
> > error happen there. We have no sco data arriving on hci, so recvmsg must
> > be interrupted by a signal instead.
> >
> > I suspect broadcom has an equivalent to csr's nonvolatile setting for
> > hci vs. pcm audio delivery. Apparently no one has good enough docs to
> > know for sure. It would help if we knew that dongle had been
> > successfully used for sco under windows.
> >
> > Brad
> >
> >
> >
> > _______________________________________________
> > Bluez-devel mailing list
> > Bluez-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-devel
> >
>
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2006-06-17 22:00 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-04 22:14 [Bluez-devel] Broadcom adapter Eduardo Margallo
2006-06-05 4:41 ` Brad Midgley
2006-06-05 10:54 ` [Bluez-devel] Belkin Eric Boon
2006-06-05 11:53 ` Eric Boon
2006-06-05 13:26 ` Eric Boon
2006-06-12 20:19 ` [Bluez-devel] Broadcom adapter Eduardo Margallo
2006-06-17 22:00 ` Eduardo Margallo
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.