From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluetooth dies when trying to use 2 sco links
Date: Sun, 17 Sep 2006 20:44:12 -0600 [thread overview]
Message-ID: <450E07FC.30700@xmission.com> (raw)
In-Reply-To: <20060917202558.GG21347@compendium.com.ar>
Horacio
fyi... over a year ago, Marcel wrote this cryptic note on multiple sco
connections:
===========
starting with 2.6.10 the hci_usb got a module parameter "isoc". This
controls the alternate setting when plugging in a dongle. The default
value is 2 (or 0 if it is blacklisted device). Check the Bluetooth
specification what value you have to choose for 2 x 16-bit SCO channels.
===========
If you're not able to find that value, you could try experimenting with
different values.
I was not able to find out what happens if the value is set higher than
you really need it. Would it hurt to load hci_usb with isoc set to the
value for two headsets even if you usually only use one? I don't know.
> Running just one instance of it with just one phone, it works great.
> When I try to run two instances, each connected to a different phone, it
> works for a few seconds and then all the SCO data stops flowing
Brad
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-09-18 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-17 20:25 [Bluez-devel] bluetooth dies when trying to use 2 sco links Horacio J. Peña
2006-09-18 2:44 ` Brad Midgley [this message]
2006-09-18 6:16 ` Marcel Holtmann
2006-11-07 23:58 ` Brad Midgley
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=450E07FC.30700@xmission.com \
--to=bmidgley@xmission.com \
--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.