From: Lars Grunewaldt <lgw@dark-reality.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] question: what does this patch from snd-bt-sco do?
Date: Tue, 18 May 2004 15:37:47 +0200 [thread overview]
Message-ID: <40AA11AB.6010307@dark-reality.de> (raw)
In-Reply-To: <1084881439.5833.108.camel@pegasus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Marcel Holtmann wrote:
| Hi Lars,
|
|
|>I already looked up the voice number stuff in the core docs, and was
|>able to find out that 0x0140 is ideal right now (MU_LAW encoded). Works
|>here, already.
|
|
| for this you must use alternate setting 1, because it is 8 bit.
|
um, sorry - what's an alternate setting? I mean, what exactly is "set" here?
I have a working setup with
hciconfig hci0 voice 0x0140
the above kernel patch and the default snd-bt-sco driver stuff (of
course alsa codec information has changed from PCM to MU_LAW)
so I don't exactly know that this alternate setting means :)
Or is it a setting that makes the 8bit-modes possible without using that
kernel patch?
sorry, but I'm a bit new to Bluez :)
~ Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAqhGqQWC6DTWkDAoRAruDAJ4+ovPkHM6M7YvCI2nh6T82RcXy+QCfV8xf
Cc+MRgtEf1rE96S3NHmcV/g=
=mc1o
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-05-18 13:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:34 [Bluez-devel] question: what does this patch from snd-bt-sco do? Lars Grunewaldt
2004-05-18 10:44 ` Marcel Holtmann
2004-05-18 10:53 ` Jonathan Paisley
2004-05-18 11:06 ` Lars Grunewaldt
2004-05-18 11:35 ` Lars Grunewaldt
2004-05-18 11:59 ` Marcel Holtmann
2004-05-18 11:57 ` Marcel Holtmann
2004-05-18 13:37 ` Lars Grunewaldt [this message]
2004-05-18 14:00 ` Marcel Holtmann
2004-06-16 22:49 ` Lars Grunewaldt
2004-06-16 23:06 ` Marcel Holtmann
2004-06-17 0:04 ` Lars Grunewaldt
2004-06-17 0:24 ` Marcel Holtmann
2004-06-17 11:24 ` Jonathan Paisley
2004-06-17 13:35 ` Lars Grunewaldt
2004-06-17 15:58 ` Marcel Holtmann
2004-06-17 20:08 ` Lars Grunewaldt
2004-06-17 20:28 ` Marcel Holtmann
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=40AA11AB.6010307@dark-reality.de \
--to=lgw@dark-reality.de \
--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 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.