public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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 02:04:14 +0200	[thread overview]
Message-ID: <40D0DFFE.7020701@dark-reality.de> (raw)
In-Reply-To: <1087427168.4309.30.camel@pegasus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marcel Holtmann wrote:
|>If you could just supply a short code snippet that shows how to handle
|>this stuff. Right now it does not look very wise to reduce support to
|>audio 0x0060, because it seems that not many headsets support that audio
|>encoding.
|
|
| This has nothing to do with the headset, because we are talking about
| the input coding and not the air coding.

Now I'm lost again. Is there an audio transcoding somewhere in the SCO
layer, so that I could simply send PCM_S16 and the SCO layer transcodes
the audio if the headset does not support this? I mean there must be a
reason why the original snd-bt-sco developer hardcoded the 8bit format
instead of using 16 bit.

What about audio quality during transcoding? MULAW sounds much better
than PCM_S8.

I have just a hard time with "accept 0x0060 because - ."

Sorry that I don't fully understand this bluetooth stuff, I'm trying my
best here. :(

I hope I dont make anyone angry or something...

|
|
|>As soon as this works again, I'll put a new patch together and make it
|>available.
|
|
| What kind of patch? We need dynamic alternate setting adjustment for the
| hci_usb driver. Nothing else.

sorry, misunderstanding. I'll make a new version of snd-bt-sco that
builds with alsa-1.0.5a. Nothing for bluez.

I'd like to help you out with this dynamic alternate setting adjustment,
but I think I don't know enough usb and/or bluetooth mojo to do anything
usefull.

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...

cu,
~  Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA0N/+QWC6DTWkDAoRArSUAJ4p4tJgUHZNgynBUdmQVyyGLR53lwCdGAe/
KLuMLz+uvuTKLaIO1yB8s9E=
=ZqlF
-----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

  reply	other threads:[~2004-06-17  0:04 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 [this message]
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=40D0DFFE.7020701@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