From: Marcel Holtmann <marcel@holtmann.org>
To: "Todd E. Johnson" <tejohnson@yahoo.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: 2.6.2 errors with DBT-120 (B2)
Date: Sat, 14 Feb 2004 15:43:14 +0100 [thread overview]
Message-ID: <1076769794.14758.2.camel@pegasus> (raw)
In-Reply-To: <402E2E29.7040207@yahoo.com>
Hi Todd,
> Bummer on the SCO support. I am looking forward to using it in an
> embedded linux based telematics system for vehicle hands free
> functionality.
this depends on whats your design. Do you use SCO over PCM or SCO over
HCI? If your embedded device includes a PCM codec you can route the SCO
traffic of the Bluetooth chip over PCM and you don't need the SCO audio
support for the HCI USB driver.
Regards
Marcel
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-02-14 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 14:18 [Bluez-users] Re: 2.6.2 errors with DBT-120 (B2) Todd E. Johnson
2004-02-14 14:43 ` Marcel Holtmann [this message]
2004-02-14 15:01 ` [Bluez-users] bcm203x module causes kernel panic on boot Alex Holland
2004-02-14 15:15 ` Marcel Holtmann
[not found] ` <402E4E02.9020600@yahoo.com>
2004-02-15 13:27 ` [Bluez-users] Re: 2.6.2 errors with DBT-120 (B2) Marcel Holtmann
2004-02-15 16:09 ` Todd E. Johnson
2004-02-15 16:20 ` Marcel Holtmann
2004-02-16 21:36 ` [Bluez-users] " Todd E. Johnson
2004-02-16 22:31 ` [Linux-usb-users] " Todd E. Johnson
2004-02-16 22:34 ` Todd E. Johnson
2004-02-18 14:25 ` [Bluez-users] " Todd E. Johnson
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=1076769794.14758.2.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=tejohnson@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.