public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "ubaldo" <ubaldo@eja.it>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: multi rfcomm/sco connection
Date: Fri, 18 Jun 2004 20:42:32 +0200	[thread overview]
Message-ID: <20040618184232.25439.qmail@webmail.aruba.it> (raw)
In-Reply-To: <1087583875.25061.2.camel@pegasus>

Thanx Marcel for your unlimited patience! :) 


>> > it is possible to establish up to 30 RFCOMM connections into each
>> > direction. The number of SCO connections is limited to one per ACL link. 
>> 
>> Does it mean that for each SCO connection I need another bt-dongle, or there 
>> is a way to allow multi SCO connection with the same bt-dongle?
> 
> I said per ACL link. The Bluetooth specification defines that between
> two devices one ACL and up to three SCO links can exists. The max number
> of SCO links per piconet is also three. In BlueZ we currently allow one
> ACL and one SCO link between two devices. This limitation is some kind
> of historic. Feel free to fix it.

Any tip for where to put the eyes on for fixing? 

  reply	other threads:[~2004-06-18 18:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 17:54 [Bluez-devel] multi rfcomm/sco connection ubaldo
2004-06-18 18:15 ` Marcel Holtmann
2004-06-18 18:33   ` ubaldo
2004-06-18 18:37     ` [Bluez-devel] " Marcel Holtmann
2004-06-18 18:42       ` ubaldo [this message]
2004-06-18 18:49         ` Marcel Holtmann
2004-07-16 14:02           ` ubaldo
2004-07-16 15:29             ` [Bluez-devel] " Marcel Holtmann
2004-08-04 22:45               ` Radha Thiagarajan
2004-08-04 23:35                 ` Marcel Holtmann
2004-08-05 15:33                   ` Radha Thiagarajan
2004-08-05 17:25                     ` 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=20040618184232.25439.qmail@webmail.aruba.it \
    --to=ubaldo@eja.it \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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