public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 07 Nov 2006 16:58:30 -0700	[thread overview]
Message-ID: <45511DA6.2000906@xmission.com> (raw)
In-Reply-To: <20060917202558.GG21347@compendium.com.ar>

Horacio

> Attached you'll find the code for a test program that makes a call using
> the hands-free profile connected to a cell phone and when the call is
> answered it generates echo (so the person who answers the phone will
> hear himself)

I talked with Marcel about this. Here's the current situation:

uart-connected bluetooth adapters can do multiple sco connections
without any trouble.

usb-connected bluetooth adapters suffer from a limitation in the usb
kernel layer... the number of sco connections has to be hardcoded at
boot time in the isoc parameter. If it's set for two 16-bit sco
connections, when more or fewer connections are in use, no audio gets
through. The usb layer needs a rewrite to fix this.

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

      parent reply	other threads:[~2006-11-07 23:58 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
2006-09-18  6:16 ` Marcel Holtmann
2006-11-07 23:58 ` Brad Midgley [this message]

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=45511DA6.2000906@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox