Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!hao!hplabs!oliveb!intelca!kds
From: kds@intelca.UUCP (Ken Shoemaker)
Newsgroups: net.arch
Subject: insuring command recovery delays, etc.
Message-ID: <218@intelca.UUCP>
Date: Mon, 24-Feb-86 18:38:31 EST
Article-I.D.: intelca.218
Posted: Mon Feb 24 18:38:31 1986
Date-Received: Wed, 26-Feb-86 21:16:37 EST
References: <1475@seismo.CSS.GOV>
Organization: Intel, Santa Clara, Ca.
Lines: 18

I say this once (I won't say where) and I thought it was really cute.  The
way it works, is that you have a standard timing loop "value", and whenever
you need a timing loop, you load this value into your loop variable.  On
reset, you calculate this value using some known time standard, whose
resolution need not be anything like what you need for your timing loops,
e.g., a 1 second timer interrupt, a character transmition time, or 
something like that.

I realize this can have some problems, what with caching, but it does
relate somewhat the speed of the processor to real time.
-- 
If you don't like the answer, then ask another question!  Everything is the
answer to something...

Ken Shoemaker, Microprocessor Design, Intel Corp., Santa Clara, Ca.
{pur-ee,hplabs,amd,scgvaxd,dual,qantel}!intelca!kds
	
---the above views are personal.