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

Hi,

> > 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? 

actually I don't see why you need more than one SCO link in a connection
between two devices. However take a look at the kernel source code of
Linux 2.6.x and especially at net/bluetooth/hci_conn.c
Regards

Marcel




-------------------------------------------------------
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

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

Thread overview: 21+ 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
2004-06-18 18:49         ` Marcel Holtmann [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-07-27 14:56 [Bluez-devel] SCO audio sync ubaldo
2004-07-27 15:06 ` Marcel Holtmann
2004-11-09 14:41   ` [Bluez-devel] Re: multi rfcomm/sco connection ubaldo
2004-11-10  0:52     ` Marcel Holtmann
     [not found] <E1CQIAu-0004AO-Dd@sc8-sf-list2.sourceforge.net>
2004-11-06 13:14 ` Suriyan
2004-11-06 13:50   ` Marcel Holtmann
2004-11-06 16:47     ` Lars Grunewaldt
     [not found] <20041110041405.3CC331D4758@sc8-sf-uberspam1.sourceforge.net>
2004-11-14  4:30 ` Suriyan
2004-11-14 15:35   ` Marcel Holtmann
2004-11-14 16:16     ` Lars Grunewaldt
2004-11-14 16:34       ` 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=1087584576.25061.6.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=ubaldo@eja.it \
    /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