From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Audio & Bluetooth
Date: Fri, 12 Nov 2004 02:26:55 +0100 [thread overview]
Message-ID: <1100222815.12168.54.camel@pegasus> (raw)
In-Reply-To: <1100221786.28744.36.camel@loke>
Hi Martin,
if you sign your emails, then make sure that your public key is
available for download somewhere or don't sign at all.
> > 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.
>
> How can the mapping be changed, if I may ask. I've been looking around
> and the only material that i found of it, is actually that you stated at
> some point, that they have to match, but not how it can be changed.
It must be set to SCO over HCI to get it working. Most dongles sold now
uses this setting by default. Some older don't. So this is a CSR chip
and all settings are in the persistant storage (PS). So you only have to
set the PS key for this one to HCI instead of PCM.
Said this there is a Windows program called pstool that can do this for
you, but it is not freely available. This is CSR specific and if you dig
deep enough into the source code of BlueZ and also the OpenBT project,
you can get the knowledge on how to change it. I don't provide a tool
for it and I also won't answer any further questions about this.
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
next prev parent reply other threads:[~2004-11-12 1:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 18:59 [Bluez-users] Audio & Bluetooth administrator tootai
2004-11-08 19:31 ` Brad Midgley
2004-11-08 19:57 ` Marcel Holtmann
2004-11-08 22:56 ` Martin List-Petersen
2004-11-08 23:28 ` Marcel Holtmann
2004-11-09 2:05 ` Martin List-Petersen
2004-11-09 9:54 ` Peter Stephenson
2004-11-09 14:11 ` Timothy Murphy
2004-11-09 14:28 ` Marcel Holtmann
2004-11-09 14:47 ` Peter Stephenson
2004-11-10 0:56 ` Marcel Holtmann
2004-11-11 20:57 ` Martin List-Petersen
2004-11-11 21:27 ` Marcel Holtmann
2004-11-12 1:09 ` Martin List-Petersen
2004-11-12 1:26 ` Marcel Holtmann [this message]
2004-11-12 1:40 ` Martin List-Petersen
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=1100222815.12168.54.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@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