From: Jonathan Paisley <jp-www@dcs.gla.ac.uk>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: Headset via usb dongle devel problems.
Date: Tue, 15 Jul 2003 22:46:13 +0100 [thread overview]
Message-ID: <pan.2003.07.15.21.46.10.918280@dcs.gla.ac.uk> (raw)
In-Reply-To: 3F0EF99B.6000400@superbug.demon.co.uk
On Fri, 11 Jul 2003 18:53:31 +0100, James Courtier-Dutton wrote:
> I have discovered that the performance of the bluez stack is a problem
> when using the hci_usb.c driver.
> I cannot get it to send SCO packets quicker than one urb per 40ms. As
> the headset needs one urb per 3ms, this is quite a problem. I would also
> assume that other applications like file transfer over bluetooth would
> be bad.
Have you identified what's actually causing this rate limit? It sounds
more like a scheduling issue to me than a number-of-memory-copies problem.
Would you consider sharing the code modifications you have made thus far?
I have been experimenting with two USB dongles with the aim of making the
PC act as a headset (I don't have one). I have been able to get reasonable
(although sometimes choppy audio) on the PC. That is, the sound is being
received by the PC. I haven't yet managed to test sending audio except for
/dev/zero. All this testing is with 2.4.20-mh10.
The two dongles I have are the Mitsumi WIF-0402c and the Sitecom CN-500,
which report as follows:
Sitecom CN-500:
$ sudo /sbin/hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:10:60:A2:E4:C2 ACL MTU: 192:8 SCO MTU: 64:8
HCI 16.4
Chip version: BlueCore02
Max key size: 56 bit
SCO mapping: HCI
Mitsumi WIF-0402c:
$ sudo /sbin/hciconfig hci0 revision
hci0: Type: USB
BD Address: 00:A0:96:1D:4A:AA ACL MTU: 128:8 SCO MTU: 64:8
HCI 11.2
Chip version: BlueCore01b
SCO mapping: HCI
The Mitsumi accepts the SCO connection and then gives up, whereas the
Sitecom is able to sustain the connection for as long as I have tested
(<2minutes). The Mitsumi is much older, so I'm not surprised there are
problems. However, both devices work okay in this manner under Windows.
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-07-15 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 17:53 [Bluez-devel] Headset via usb dongle devel problems James Courtier-Dutton
2003-07-15 21:46 ` Jonathan Paisley [this message]
2003-07-16 0:23 ` [Bluez-devel] Measuring throughput using l2test gives very high value Aarti Kumar
2003-07-21 23:13 ` [Bluez-devel] Headset via usb dongle devel problems Max Krasnyansky
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=pan.2003.07.15.21.46.10.918280@dcs.gla.ac.uk \
--to=jp-www@dcs.gla.ac.uk \
--cc=bluez-devel@lists.sourceforge.net \
/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