www.delorie.com/archives/browse.cgi | search |
Date: | Mon, 31 Aug 1998 12:31:55 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
To: | Andris Pavenis <pavenis AT lanet DOT lv> |
cc: | djgpp AT delorie DOT com, "Alexander S. Aganichev" <asa AT lan DOT eed DOT miee DOT ru> |
Subject: | Re: uclock () |
In-Reply-To: | <Pine.A32.3.91.980831104219.35380E-100000@ieva06.lanet.lv> |
Message-ID: | <Pine.SUN.3.91.980831123101.22974d-100000@is> |
MIME-Version: | 1.0 |
On Mon, 31 Aug 1998, Andris Pavenis wrote: > There is no other way if one does not want to introduce compatibility > problems. If somebody else will try to read PIC timer counter at the same > time (one process is interrupted in the middle of reading and the second > is doing the same reading) PIC timer will be messed up. I think that's why `uclock' keeps reading the timer output until the results are consistent.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |