From: Patrick McHardy <kaber@trash.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>,
bluez-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
maxk@qualcomm.com
Subject: Re: patch: problem with sco
Date: Thu, 12 Jan 2006 13:26:52 +0100 [thread overview]
Message-ID: <43C64B0C.2080903@trash.net> (raw)
In-Reply-To: <1137057244.3955.3.camel@localhost.localdomain>
Marcel Holtmann wrote:
>>A friend and I encountered a problem with sco transfers to a headset using
>>linux (vanilla 2.6.15). While all sco packets sent by the headset were
>>received there was no outgoing traffic.
>>
>>After switching debugging output on we found that actually sco_cnt was always
>>zero in hci_sched_sco.
I'm seeing the exact same problem with a Logitech "mobile Freedom"
headset. I'm using this patch to work around the problem:
--- a/net/bluetooth/hci_core.c
+++ b/net/bluetooth/hci_core.c
@@ -1239,7 +1239,7 @@ static inline void hci_sched_sco(struct
BT_DBG("%s", hdev->name);
- while (hdev->sco_cnt && (conn = hci_low_sent(hdev, SCO_LINK,
"e))) {
+ while (/* hdev->sco_cnt && */ (conn = hci_low_sent(hdev,
SCO_LINK, "e))) {
while (quote-- && (skb = skb_dequeue(&conn->data_q))) {
BT_DBG("skb %p len %d", skb, skb->len);
hci_send_frame(skb);
> send in the information from "hciconfig -a" for this device, because
> this is a hardware bug and you can't be sure that you can have eight
> outstanding SCO packets.
In my case:
hci0: Type: USB
BD Address: 00:10:C6:86:64:27 ACL MTU: 377:10 SCO MTU: 48:64
UP RUNNING PSCAN ISCAN
RX bytes:622370 acl:27 sco:12167 events:69 errors:0
TX bytes:588454 acl:25 sco:11520 commands:35 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: 'krusty-0'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.2 (0x2) HCI Rev: 0x11 LMP Ver: 1.2 (0x2) LMP Subver:
0x6963
Manufacturer: Broadcom Corporation (15)
next prev parent reply other threads:[~2006-01-12 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 0:38 patch: problem with sco Wolfgang Walter
2006-01-12 9:14 ` Marcel Holtmann
2006-01-12 11:47 ` Wolfgang Walter
2006-01-12 12:26 ` Patrick McHardy [this message]
2006-01-12 13:31 ` Marcel Holtmann
2006-01-12 13:56 ` Patrick McHardy
2006-01-12 14:59 ` Wolfgang Walter
2006-01-12 23:31 ` Wolfgang Walter
2006-01-12 23:33 ` Wolfgang Walter
2006-01-13 8:27 ` [Bluez-devel] " Marcel Holtmann
2006-01-15 14:40 ` Wolfgang Walter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C64B0C.2080903@trash.net \
--to=kaber@trash.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
--cc=wolfgang.walter@studentenwerk.mhn.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).