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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8c564a80b820db35
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.68.227.166 with SMTP id sb6mr612047pbc.4.1331031105480;
        Tue, 06 Mar 2012 02:51:45 -0800 (PST)
Path: 
 h9ni45543pbe.0!nntp.google.com!news1.google.com!goblin1!goblin3!goblin.stu.neva.ru!news.tu-darmstadt.de!news.belwue.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail
Date: Tue, 06 Mar 2012 11:51:31 +0100
From: Georg Bauhaus <rm.dash-bauhaus@futureapps.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6;
 rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Any leap year issues caused by Ada yesterday?
References: <4f4f746a$0$6565$9b4e6d93@newsspool3.arcor-online.net>
 <abdf6306-50b4-43ed-9e18-3c57c1e97160@9g2000vbq.googlegroups.com>
 <20608866.730.1330963171058.JavaMail.geo-discussion-forums@ynbq18>
 <1t8v4akrmapkl.1xwfi9yxtw2ji$.dlg@40tude.net> <m2eht6j3xl.fsf@pushface.org>
 <msh09luylmxz$.qdnnl7pz5j14.dlg@40tude.net> <m2aa3uix7a.fsf@pushface.org>
 <18ghv3yeh1a1k$.1bjwdaps59rt3$.dlg@40tude.net> <m262eihyq0.fsf@pushface.org>
 <d37aucb0avr1$.ihxbw6kqhx1e$.dlg@40tude.net>
In-Reply-To: <d37aucb0avr1$.ihxbw6kqhx1e$.dlg@40tude.net>
Message-ID: <4f55ec33$0$7613$9b4e6d93@newsspool1.arcor-online.net>
Organization: Arcor
NNTP-Posting-Date: 06 Mar 2012 11:51:31 CET
NNTP-Posting-Host: 1a6fd257.newsspool1.arcor-online.net
X-Trace: 
 DXC=AK@o26Z1NAmfF8a^:6>b7eic==]BZ:afn4Fo<]lROoRa<`=YMgDjhgbVlijeZK>]Hanc\616M64>jLh>_cHTX3jm_G`S2J0lOIj
X-Complaints-To: usenet-abuse@arcor.de
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Date: 2012-03-06T11:51:31+01:00
List-Id: <comp.lang.ada>

On 06.03.12 11:07, Dmitry A. Kazakov wrote:
> The actual problem is to get the multiplier, the BIOS time, and keeping the
> TSC synchronized with the system clock.

Why isn't there a chip that does just one thing:
signal regularly, at sufficiently high frequency,
and totally independent of its electrical surroundings,
autonomous,
unaffected by software,
and having its own power supply?
Ping - ping - ping - ping - ...
Into some memory location, maybe?

Or is there?