From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO connection timed out issue
Date: Thu, 18 Oct 2007 12:31:40 +0200 [thread overview]
Message-ID: <4717360C.7090801@free.fr> (raw)
In-Reply-To: <BAY117-W36EE4B29F3D4550A7C9847C09E0@phx.gbl>
Hi,
Sorry i have to say you this, but you're basically trying to make sth
work that will never make it ;-)
* STLC2500C does not support sco over hci, so unless your development
has an audio codec hardwired to the BT chip, you're screwed :-(
* You need latest bluez-utils CVS to have any chance for your chip
to run at decent speed, which is required for a2dp streaming. You should
then use the follwing syntax to start the chip at max speed: hciattach
/dev/ttyUSB0 stlc2500 921600
Apart from that this is know to work.
Regards,
Fabien
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-18 10:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 1:36 [Bluez-devel] SCO connection timed out issue \x11
2007-10-18 1:49 ` Brad Midgley
2007-10-18 2:46 ` \x11
2007-10-18 3:14 ` \x11
2007-10-18 13:24 ` Brad Midgley
2007-10-18 13:46 ` \x11
2007-10-18 17:26 ` Brad Midgley
2007-10-19 2:24 ` dong yan
2007-10-18 10:31 ` Fabien Chevalier [this message]
2007-10-18 12:13 ` \x11
2007-10-18 12:33 ` \x11
2007-10-18 13:08 ` Fabien Chevalier
2007-10-19 3:16 ` \x11
2007-10-19 5:55 ` \x11
2007-10-20 8:05 ` \x11
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=4717360C.7090801@free.fr \
--to=fabchevalier@free.fr \
--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