From: Mauro Tortonesi <mtortonesi@ing.unife.it>
To: Marcel Holtmann <marcel@holtmann.org>,
James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: "Fred Schättgen" <bluez-devel@schaettgen.de>,
"BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>,
"Simon Vogl" <vogl@soft.uni-linz.ac.at>
Subject: Re: [Bluez-devel] sco link help needed
Date: Wed, 25 Feb 2004 13:59:00 +0100 [thread overview]
Message-ID: <200402251359.00791.mtortonesi@ing.unife.it> (raw)
In-Reply-To: <1077522938.2832.84.camel@pegasus>
On Monday 23 February 2004 08:55, Marcel Holtmann wrote:
> > The bluetooth chip should not have to worry about dropping packets, the
> > application should just send the chip packets when the chip wants them.
>
> Yes it have to. You should read the mailing list archive and search for
> comments from the CSR guys about SCO. And you can of course take the
> Bluetooth specification itself.
hi marcel,
could you please provide a url?
i have been trying to transfer pcm data over a sco socket both using scotest
and other similar apps of mine, but the actual data tranferred were only a
bunch of random bytes, completely unrelated to the data sent. moreover, the
behaviour of sco links is very unreliable. in my tests i have used several
usb dongles with CSR chips (firmware versions ranging from HCI 15.3 to HCI
16.4) and kernel versions from 2.4.22 to 2.4.25-pre7.
you have told us many times that there are strong limitations in what you can
do with sco sockets, but i still can't understand what are these limitations.
i have tried searching trough the archives but i couldn't find anything
interesting about this.
> > I am only asking for changes to the SCO side of things due to it's real
> > time nature. Using network sockets for RFCOMM and bulk data transfers
> > that are not real time in nature is fine.
> >
> > Once we have proper real time SCO support, we can overlay the current
> > SCO file descriptor read/write model on top if you still need it.
>
> Again, I can't follow what you are trying to achieve. The current socket
> interface for SCO fits not perfect, because it is audio only data.
does this mean that you simply can't perform pcm audio transfers between two
bluez hosts by using sco sockets just like scotest does? if so, what is the
purpose of scotest, then?
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi mtortonesi@ing.unife.it
mauro@deepspace6.net
mauro@ferrara.linux.it
Deep Space 6 - IPv6 with Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
next prev parent reply other threads:[~2004-02-25 12:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 14:36 [Bluez-devel] sco link help needed Simon Vogl
2004-02-19 15:29 ` Fred Schättgen
2004-02-21 14:37 ` James Courtier-Dutton
2004-02-22 12:27 ` Marcel Holtmann
2004-02-22 20:53 ` James Courtier-Dutton
2004-02-22 21:30 ` Marcel Holtmann
2004-02-22 22:04 ` James Courtier-Dutton
2004-02-22 22:09 ` Marcel Holtmann
2004-02-22 23:37 ` James Courtier-Dutton
2004-02-23 7:55 ` Marcel Holtmann
2004-02-25 12:59 ` Mauro Tortonesi [this message]
2004-02-25 13:25 ` Marcel Holtmann
2004-02-25 14:04 ` Mauro Tortonesi
2004-02-25 14:23 ` Marcel Holtmann
2004-02-25 15:35 ` Mauro Tortonesi
2004-02-25 15:37 ` Marcel Holtmann
2004-02-25 15:46 ` Mauro Tortonesi
[not found] ` <1077728432.6021.522.camel@localhost>
2004-02-25 17:16 ` Marcel Holtmann
2004-02-25 17:27 ` Nils Faerber
2004-02-25 14:30 ` James Courtier-Dutton
2004-02-25 14:59 ` Dr. Simon Vogl
2004-02-25 15:09 ` Marcel Holtmann
2004-02-25 14:22 ` James Courtier-Dutton
2004-02-23 16:35 ` libs2 and utils2 Aaron Klish
2004-02-23 17:19 ` [Bluez-devel] " Marcel Holtmann
2004-02-22 21:54 ` [Bluez-devel] sco link help needed Fred Schättgen
2004-02-22 22:00 ` Marcel Holtmann
2004-02-22 22:35 ` Fred Schättgen
2004-02-22 12:44 ` Dr. Simon Vogl
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=200402251359.00791.mtortonesi@ing.unife.it \
--to=mtortonesi@ing.unife.it \
--cc=James@superbug.demon.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-devel@schaettgen.de \
--cc=marcel@holtmann.org \
--cc=vogl@soft.uni-linz.ac.at \
/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