From: Marcel Holtmann <marcel@holtmann.org>
To: Steven Singer <steven.singer@csr.com>
Cc: ag@new-media-artists.de,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Device Busy during "hcitool info" or "sdptoolsearch"
Date: Wed, 17 Dec 2003 23:11:44 +0100 [thread overview]
Message-ID: <1071699104.21804.77.camel@pegasus> (raw)
In-Reply-To: <3FE0C1B9.5090504@csr.com>
Hi Steven,
> The create_connection-inquiry restriction is there because both
> procedures need to get as much radio bandwidth as possible to work. In
> particular, taking bandwidth away from paging can cause spurious failed
> connections. In this case, create_connection wins. If you issue a
> create_connection while an inquiry is in progress, we will terminate
> the inquiry with an inquiry_complete event and start paging
> immediately.
this is a nice thing/feature to know. Is it documented anywhere in the
firmware release notes?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-12-17 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 16:38 [Bluez-devel] Device Busy during "hcitool info" or "sdptool search" Andreas Gaufer
2003-12-17 17:54 ` Marcel Holtmann
2003-12-17 19:08 ` AW: [Bluez-devel] Device Busy during "hcitool info" or "sdptoolsearch" Andreas Gaufer
2003-12-17 19:34 ` Marcel Holtmann
2003-12-17 20:51 ` AW: " Steven Singer
2003-12-17 22:11 ` Marcel Holtmann [this message]
2003-12-18 14:39 ` Steven Singer
2003-12-18 0:50 ` AW: " Andreas Gaufer
2003-12-18 9: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=1071699104.21804.77.camel@pegasus \
--to=marcel@holtmann.org \
--cc=ag@new-media-artists.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=steven.singer@csr.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.