Content-Type: text/plain;
  charset="iso-8859-1"
From: Ronny L Nilsson <bb@arbetsmyra.dyndns.org>
To: bluez-devel@lists.sourceforge.net
Cc: Albert Huang <ashuang@gmail.com>
MIME-Version: 1.0
Message-Id: <20050615113734.035D26EC@arbetsmyra.dyndns.org>
Subject: [Bluez-devel] varying time to connect
Sender: bluez-devel-admin@lists.sourceforge.net
Errors-To: bluez-devel-admin@lists.sourceforge.net
Reply-To: bluez-devel@lists.sourceforge.net
Date: Wed, 15 Jun 2005 13:35:30 +0200


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