From: "Cooper Xu" <cooper.xu@mapleworks.com>
To: "'Nick Pelly'" <npelly@google.com>
Cc: <linux-bluetooth@vger.kernel.org>
Subject: RE: A strange compatible problem for eSCO audio with CSR USB Bluetooth dongle
Date: Mon, 15 Mar 2010 18:24:06 -0400 [thread overview]
Message-ID: <AF001CBC42E74321BAACA4E800DC68E7@mapleworks.com> (raw)
In-Reply-To: <35c90d961003151435i6dc2a096j300198decb4844e6@mail.gmail.com>
Thanks, I will try it.
The strange thing is the eSCO audio worked ok with Blackberry curve 8310,
which seems to use the same CSR BlueCore4 chipset and firmware version
0xc5c. I assume the library of Blackberry is not Bluez.
But when I use a PC with CSR BlueCore4 dongle with USB interface and Bluez
library as the remote for testing, from the captured eSCO stream, I can not
see any real data I sent, I got all zero.
However If I changed the USB dongle to Broadcom chipset, I can see a few
real data from captured eSCO stream (not all of data I sent, some seemed
lost or being replaced by zero).
-----Original Message-----
From: Nick Pelly [mailto:npelly@google.com]
Sent: Monday, March 15, 2010 5:35 PM
To: Cooper Xu
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: A strange compatible problem for eSCO audio with CSR USB
Bluetooth dongle
I wonder if this is some eSCO packet type incompatibility between
chipsets. Try setting /sys/module/sco/parameters/disable_esco to 1 to
see if this resolves the issue.
Nick
prev parent reply other threads:[~2010-03-15 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 23:01 A strange compatible problem for eSCO audio with CSR USB Bluetooth dongle Cooper Xu
2010-03-14 23:28 ` Marcel Holtmann
2010-03-16 1:54 ` Cooper Xu
2010-03-16 2:38 ` Marcel Holtmann
2010-03-16 2:53 ` Cooper Xu
2010-03-16 3:06 ` Cooper Xu
2010-03-24 21:08 ` Cooper Xu
2010-04-19 22:03 ` Cooper Xu
2010-03-15 21:35 ` Nick Pelly
2010-03-15 22:24 ` Cooper Xu [this message]
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=AF001CBC42E74321BAACA4E800DC68E7@mapleworks.com \
--to=cooper.xu@mapleworks.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=npelly@google.com \
/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).