From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] It's rfcomm connect problem
Date: Mon, 24 Jul 2006 18:35:12 +0200 [thread overview]
Message-ID: <1153758912.25058.3.camel@localhost> (raw)
In-Reply-To: <20060724155621.02cd5e11@localhost.localdomain>
Hi Andreas,
> thank your for that information. I guess your problem is just the same
> you had with sdp some while ago. A single BT Device can not *start*
> connecting to two different remote devices at the same time.
>
> To solve this you have to find a way to:
>
> 1. Create Connection to device A
> 2. Wait until Connect Complete for A's bdaddr happens (no matter if failed or succ.)
> 3. Then continue with other Create Connection Commands
we have a plan to make the L2CAP layer handle multiple ACL connects and
try again if one attempt fails. However the last patch I wrote for it
got lost somehow and it was broken anyway. The mailing list should
contain a thread where I proposed how this must be handled. I don't have
time to look at it at the moment. So if anybody wants to work on it,
please do so and send in a patch.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-07-24 16:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 16:28 [Bluez-devel] Error: sdptool browse --> Connection reset by peer JP Freeley
2006-07-20 0:48 ` Marcel Holtmann
2006-07-20 21:27 ` JP Freeley
2006-07-25 4:26 ` JP Freeley
2006-07-22 14:08 ` [Bluez-devel] It's rfcomm connect problem Fabrizio Guglielmino
2006-07-24 8:38 ` Andreas Gaufer
2006-07-24 13:33 ` Fabrizio Guglielmino
2006-07-24 13:56 ` Andreas Gaufer
2006-07-24 16:35 ` Marcel Holtmann [this message]
2006-07-24 18:34 ` Andreas Gaufer
2006-07-24 20:30 ` Fabrizio Guglielmino
2006-07-24 21:12 ` Marcel Holtmann
2006-07-27 9:04 ` Fabrizio Guglielmino
2006-07-27 9:25 ` [Bluez-devel] It's rfcomm connect problem [ERRATA] Fabrizio Guglielmino
2006-07-28 11:14 ` [Bluez-devel] It's rfcomm connect problem Marcel Holtmann
2006-07-31 10:02 ` [Bluez-devel] About l2cap patch to handle multiple connections Fabrizio Guglielmino
2006-07-31 14:14 ` Marcel Holtmann
2006-08-02 11:24 ` Fabrizio Guglielmino
2006-08-02 13:43 ` 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=1153758912.25058.3.camel@localhost \
--to=marcel@holtmann.org \
--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