From: Marcel Holtmann <marcel@holtmann.org>
To: Lars Grunewaldt <lgw@dark-reality.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
linux-usb-users@lists.sourceforge.net
Subject: Re: [Bluez-devel] question: what does this patch from snd-bt-sco do?
Date: Tue, 18 May 2004 12:44:41 +0200 [thread overview]
Message-ID: <1084877081.5833.102.camel@pegasus> (raw)
In-Reply-To: <40A9E6CB.4010505@dark-reality.de>
Hi Lars,
> there's a kernel patch in snd-bt-sco, and it would be great if someone
> could explain what it does:
>
> *****
> - --- linux-2.6.4-orig/drivers/bluetooth/hci_usb.c 2004-03-11
> 02:55:44.000000000 +0000
> +++ linux-2.6.4/drivers/bluetooth/hci_usb.c 2004-03-13
> 23:52:27.000000000 +0000
> @@ -851,7 +851,12 @@
>
> ~ #ifdef CONFIG_BT_HCIUSB_SCO
> ~ case USB_ENDPOINT_XFER_ISOC:
> - - if (ep->desc.wMaxPacketSize < size || a > 2)
> + /* Use only the 9 byte
> + "One voice channel with 8 bit encoding"
> + endpoint until there is support for changing
> + the endpoint dynamically. See
> + Bluetooth 1.1 Part H:2, section 2.1 */
> + if (ep->desc.wMaxPacketSize != 9)
> ~ break;
> ~ size = ep->desc.wMaxPacketSize;
> ****
according to the current voice setting (0x0060 by default) and the
number of SCO link the Bluetooth USB driver has to adjust the alternate
setting for the ISOC interface. Currently we don't support this dynamic
adjustment in hci_usb and so I have choosen to use alternate setting 2
as default value in the latest versions of 2.4 and 2.6 kernels. This
means that the voice setting must be 0x0060 and there can be only one
SCO link at the same time. For more information look at the Bluetooth
core specification.
> Also, it would be interesting to know if this patch for kernel 2.6.4 is
> still nessesary for newer kernels (2.6.6 to be specific), because I want
> to "port" snd-bt-sco to alsa 1.0.4 and kernel 2.6.6.
Don't use this patch and accept the default voice setting of 0x0060.
Regards
Marcel
-------------------------------------------------------
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 10:44 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 [this message]
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
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=1084877081.5833.102.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=lgw@dark-reality.de \
--cc=linux-usb-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