public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrea Galbusera" <gizero@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] concurrent calls to RFCOMM connect()
Date: Tue, 27 Nov 2007 09:03:05 +0100	[thread overview]
Message-ID: <f8e53fb0711270003r2e32f78ev18205a8381d750d3@mail.gmail.com> (raw)
In-Reply-To: <1196055392.4217.41.camel@aeonflux>

Hi Marcel,

On Nov 26, 2007 6:36 AM, Marcel Holtmann <marcel@holtmann.org> wrote:
> a small comment up-front. Top-posting is not a good way of getting my
> attention. Check http://www.bluez.org/lists.html

You are obviously right! I apologize to you and other users of the
list for the inconvenience. That was accidental and was not intended
as a way to catch more attention. I understand that some of my
questions may sound silly to you and other bluez developers, but I
don't have a wireless communication background and I'm trying to
approach bluetooth from the application level.

> It takes 20 seconds, because that is the page timeout of your local
> hardware. You can change it with "hciconfig hci0 pageto". You can also
> play with the link supervision timeout to faster detect a link loss.
> Please remember that a shorter value also has disadvantages.

I will search more on these timeouts and the pro/cons of changing
them. Maybe tuning them will suffice.

> It serializes connection attempts to different remote devices. If you
> try to connect to the same remote device (by opening the same TTY twice)
> then you are out of luck. The kernel is not doing anything here.

My question was not clear enough... In my test I try to connect to a
different remote address while in progress with the first one (both
powered off). I do it like this:

Terminal 1:
$> rfcomm connect 00:01:95:07:30:EA

Terminal 2 (while the first attempt is in progress):
$> rfcomm connect 00:01:95:07:30:40
Can't connect RFCOMM socket: Device or resource busy

Does it mean my kernel and/or my bluez-utils are too old to queue
connection attempts?

> You need to read the specification since clearly you are guessing here
> behavior. The various timeouts can be configured. Or maybe get a book
> that explains the basics behind the Bluetooth radio.

I'm going to follow your suggestions, even if I believe the
specification is too intricated for me. Maybe a book is a better
choice. Thanks for patience.

Regards,
Andrea

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-11-27  8:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-17  7:33 [Bluez-users] concurrent calls to RFCOMM connect() Andrea Galbusera
2007-10-17 14:20 ` Marcel Holtmann
2007-10-18  6:39   ` Andrea Galbusera
2007-11-25 15:54   ` Andrea Galbusera
2007-11-26  5:36     ` Marcel Holtmann
2007-11-27  8:03       ` Andrea Galbusera [this message]
2007-11-27  8:29         ` Marcel Holtmann
2007-11-27  8:37           ` Marco Pracucci
2007-11-27  8: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=f8e53fb0711270003r2e32f78ev18205a8381d750d3@mail.gmail.com \
    --to=gizero@gmail.com \
    --cc=bluez-users@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