From: Marcel Holtmann <marcel@holtmann.org>
To: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>
Cc: bluez-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
maxk@qualcomm.com
Subject: Re: patch: problem with sco
Date: Thu, 12 Jan 2006 10:14:04 +0100 [thread overview]
Message-ID: <1137057244.3955.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200601120138.31791.wolfgang.walter@studentenwerk.mhn.de>
Hi Wolfgang,
> 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.
>
> hciconfig hci0 shows sco_mtu to be 64:0. Changing that to 64:8 did not help.
>
> This was because in hci_cc_info_param hdev->sco_pkts is set to zero. When we
> changed this line so that hdev->sco_pkts is set to 8 if bs->sco_max_pkt is 0
> sco transfer to the headset started to work just fine.
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.
I personally prefer to implement this as a quirk which can be activated
by the driver. Once I have seen the device information, I will think
about how we might deal with it.
Regards
Marcel
next prev parent reply other threads:[~2006-01-12 9:14 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 [this message]
2006-01-12 11:47 ` Wolfgang Walter
2006-01-12 12:26 ` Patrick McHardy
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=1137057244.3955.3.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).