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: Thu, 17 Jun 2004 15:35:15 +0200 [thread overview]
Message-ID: <40D19E13.9070005@dark-reality.de> (raw)
In-Reply-To: <E1B5DFDA-C050-11D8-9772-000A95A4D990@dcs.gla.ac.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jonathan Paisley wrote:
| On 17 Jun 2004, at 1:24, Marcel Holtmann wrote:
|
|>> To make my headset work for now (need my "phone") I used that bad kernel
|>> patch again, but I'll try to do everything to avoid that in the release.
|>> I just have to understand what's going on...
|>
|>
|> I don't see your problem. Simply use 16bit PCM in the ALSA code.
|
|
| This should work fine. Reconfigure the sound format descriptors in the
| ALSA driver to describe 16 bit audio instead of 8 bit.
won't be a problem. I know what to do because I changed them before,
from S8 to MULAW_8 :)
My only problem/wish is that I'd like to support all three audio
encodings, but I understand this is impossible right now.
What exactly are the influences of the "alternate setting"? Does this
only change SCO/Audio behaviour, or is the whole bluez stack affected by
this (if hci_usb is used, of course). I just want to understand the
pros/cons of 8bit/16bit setting.
[listOT]
There's one more (alsa-related) issue I have with the alsa driver. The
problem is that, if there's no open sco channel, the audio application
accessing the interface is stalled because the buffer is never read. It
would be better if the data could be "dumped" or something.
Is this possible in an easy way, or do I have to look for audio
sync/timing and stuff instead of just writing the data to /dev/null and
tell the app "go for the next buffer".
[/listOT]
thanks,
~ Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA0Z4TQWC6DTWkDAoRAusPAKCaEozsMCgE38q4Ki+wHBcVoYu/RwCgjbPn
6NmfwP1Qxbvgrg3tMkPQdtg=
=AMrl
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-17 13:35 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
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 [this message]
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=40D19E13.9070005@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox