Subject: Re: [Bluez-users] Audio & Bluetooth
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
In-Reply-To: <1100206677.4193d255a3140@support.tuxbox.dk>
References: <418FC205.7070102@tootai.net>
	 <1099943857.29330.27.camel@pegasus>
	 <1100206677.4193d255a3140@support.tuxbox.dk>
Content-Type: text/plain
Message-Id: <1100208476.12168.31.camel@pegasus>
Mime-Version: 1.0
Sender: bluez-users-admin@lists.sourceforge.net
Errors-To: bluez-users-admin@lists.sourceforge.net
Reply-To: bluez-users@lists.sourceforge.net
Date: Thu, 11 Nov 2004 22:27:56 +0100

Hi Martin,

> > actually this is not an easy to answer question. First thing is that you
> > should get a Bluetooth device with a CSR chip and at least HCI 16.x
> > firmware on it. The second is that it must route the SCO traffic through
> > the HCI and via a PCM. Then it should be possible.
> 
> Getting back to this (and just to clarify this exactly).
> 
> on hciconfig hci0 revision: "SCO mapping:  PCM" is good ? And "SCO mapping: 
> HCI" is bad ? 

the SCO mapping HCI is the right one, because for the PCM you need
access to the PCM interface on your Bluetooth chip and normally you
can't access this on an USB dongle.

> Is there anyway that can be done to this in regards to audio ?

For a CSR chip the SCO mapping can be changed.

Regards

Marcel


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users/listinfo/bluez-users