From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,4cf2bf48a13f1d9
X-Google-Attributes: gid103376,public
From: Ehud Lamm <mslamm@mscc.huji.ac.il>
Subject: Re: Clock Synchronization
Date: 2000/07/14
Message-ID: 
 <Pine.A41.3.96-heb-2.07.1000714133246.123762A-100000@pluto.mscc.huji.ac.il>#1/1
X-Deja-AN: 646270874
References: <396ED195.8DED1C1A@ib-paus.com>
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Complaints-To: usenet@news.huji.ac.il
X-Trace: news.huji.ac.il 963570858 10143 132.64.178.45 (14 Jul 2000 10:34:18
 GMT)
Organization: The Hebrew University of Jerusalem
Mime-Version: 1.0
NNTP-Posting-Date: 14 Jul 2000 10:34:18 GMT
Newsgroups: comp.lang.ada
Date: 2000-07-14T10:34:18+00:00
List-Id: <comp.lang.ada>

I am not an embedded man, and don't know much about the hardware you use.
But I thought I'd mention the clock synchonization is a classic
distributed algorithms problem, with several published and analyzied
algorithms.

Ehud Lamm mslamm@mscc.huji.ac.il
http://purl.oclc.org/NET/ehudlamm <== My home on the web 
Check it out and subscribe to the E-List- for interesting essays and more!