From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Mauro Tortonesi <mtortonesi@ing.unife.it>
Cc: "Marcel Holtmann" <marcel@holtmann.org>,
"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 14:30:10 +0000 [thread overview]
Message-ID: <403CB172.8070103@superbug.demon.co.uk> (raw)
In-Reply-To: <200402251504.47809.mtortonesi@ing.unife.it>
Mauro Tortonesi wrote:
>>
>>You can send PCM audio over a SCO socket, but you can't expect that the
>>PCM stream on the other side is byte by byte the same. It only sounds
>>the same.
>
>
> i haven't tried, but i don't suppose that infinite series of zeros i get on
> the receiver sounds just like art blakey's alamode. there is surely something
> wrong in the transfer process. could it be the fact that my hosts have an
> usb-uhci controller?
>
If you are receiving only zeros at the far end, the problem is with the
sco driver or the hci-usb driver or the uhci_hcd driver.
I currently think the hci-usb driver is at fault, but I am doing
research with the linux usb developers to discover how they think it
should be done, and then I will look at the hci-usb driver and see if it
is doing things correctly.
With my system, the urbs are failing the submit_urb in the hci-usb
driver on kernel 2.6.3, so the hci-usb driver must be doing something
wrong as the new kernel usb code does more checks in order to catch
badly behaved applications. I think they are taking the approach that if
an application is behaving badly, make it fail completely, thus forcing
the program writter to correct it. Seems like a good policy to me. It is
better to have an application working 100% of the time or 0% of the
time, rather than randomly working/not working.
Cheers
James
next prev parent reply other threads:[~2004-02-25 14:30 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
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 [this message]
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=403CB172.8070103@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=bluez-devel@schaettgen.de \
--cc=marcel@holtmann.org \
--cc=mtortonesi@ing.unife.it \
--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