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 00:49:21 +0200 [thread overview]
Message-ID: <40D0CE71.2010208@dark-reality.de> (raw)
In-Reply-To: <1084888843.4327.1.camel@pegasus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi again,
I hope you can remember the issue we had a few weeks ago about
snd-bt-sco/bt-headset stuff.
I'm right now moving it from alsa 1.0.3 to 1.0.5a and kernel 2.6.7, and
I want to get rid of this patch (as it seems you all don't like it).
But I still don't understand, and can't find out, what I have to do to
set the dubious "alternate" setting of the hci_usb you spoke of. I'm
totally lost here, and I hope you can help me out easily :)
I understand what it does, but I don't have *any* clue right now what I
have to do to set the usb alternate setting.
- - parameter to hci_usb on module load or some other CL stuff?
- - changing something in the btsco userspace daemon that handles the
rfcomm/sco-stuff?
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.
As soon as this works again, I'll put a new patch together and make it
available.
thanks for helping out,
~ Lars
Marcel Holtmann wrote:
| Hi Lars,
|
|
|>um, sorry - what's an alternate setting? I mean, what exactly is "set"
here?
|
|
| this has nothing to do with ALSA or BlueZ. It is a USB specific
| definition of having alternate settings for an interface. Look at
| /proc/bus/usb/devices for your USB Bluetooth dongle.
|
| Regards
|
| Marcel
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA0M5wQWC6DTWkDAoRAlK5AJ94SZEYK4UTgem1AwCFWBpaCCQ9OwCfZjUu
wM24Y3tNEwcKkL6UO24qQgY=
=MKIj
-----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-16 22:49 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 [this message]
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=40D0CE71.2010208@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