From: Ronny L Nilsson <bb@arbetsmyra.dyndns.org>
To: bluez-devel@lists.sourceforge.net
Cc: Albert Huang <ashuang@gmail.com>
Subject: [Bluez-devel] varying time to connect
Date: Wed, 15 Jun 2005 13:35:30 +0200 [thread overview]
Message-ID: <20050615113734.035D26EC@arbetsmyra.dyndns.org> (raw)
Hi
Following up my own question on the users-list at
http://sourceforge.net/mailarchive/forum.php?thread_id=7501858&forum_id=1883
I've made futher investigations regarding the optimise-connect issue.
Reading the BT 1.2 spec it seems like HCI support an optional clock
offset parameter when doing connects. However, it seems like BlueZ
doesn't utilise it. My guess is this might be the case to the very much
varying delays when establishing a connection with
hcitool cc 00:11:22:33:44:55
Anyone who can confirm this? Or is there a reason why the clock offset
parameter ain't used? I'm thinking of perhaps modifying hcid to cache
clocks from most resent inqury to reuse them later, at a subsequent
connect. Or is there a better way?
Regards
/Ronny Nilsson
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-06-15 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 11:35 Ronny L Nilsson [this message]
2005-06-15 11:04 ` [Bluez-devel] varying time to connect Peter Wippich
2005-06-15 13:14 ` Ronny L Nilsson
2005-06-15 13:09 ` 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=20050615113734.035D26EC@arbetsmyra.dyndns.org \
--to=bb@arbetsmyra.dyndns.org \
--cc=ashuang@gmail.com \
--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