From: kusy <kusy>
Date: Fri, 10 Apr 2009 21:38:09 +0000 (+0000)
Subject: Update an incorrect comment. Thanks to Thomas. (https://www.millennium.berkeley.edu... 
X-Git-Tag: rc_6_tinyos_2_1_1~421
X-Git-Url: https://oss.titaniummirror.com/gitweb/?a=commitdiff_plain;h=f372a3e0c55afe433d4fd5b6cdca7727cf42f76b;p=tinyos-2.x.git

Update an incorrect comment. Thanks to Thomas. (https://www.millennium.berkeley.edu/pipermail/tinyos-devel/2009-March/003733.html)
---

diff --git a/tos/lib/ftsp/TimeSyncMsg.h b/tos/lib/ftsp/TimeSyncMsg.h
index a9e6e393..f45c2b34 100644
--- a/tos/lib/ftsp/TimeSyncMsg.h
+++ b/tos/lib/ftsp/TimeSyncMsg.h
@@ -32,10 +32,16 @@ typedef nx_struct TimeSyncMsg
 	nx_uint16_t	nodeID;		// the node if of the sender
 	nx_uint8_t	seqNum;		// sequence number for the root
 
-	/* This field is initially set to the offset between global time and local
-	 * time. The TimeStamping component will add the current local time when the
-	 * message is actually transmitted. Thus the receiver will receive the
-	 * global time of the sender when the message is actually sent. */
+	/*
+	* After TEP 133, the message timestamp contains the difference between
+	* event time and the time the message was actually sent out. TimeSyncP
+	* sends the local time associated with this globalTime to the
+	* TimeStamping mechanism, which then calculates the difference.
+	*
+	* On the receiving side, the difference is applied to the local
+	* timestamp. The receiving timestamp thus represents the time on the
+	* receiving clock when the remote globalTime was taken.
+	*/
 	nx_uint32_t	globalTime;
 
 	//just for convenience