Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!rice!sun-spots-request
From: smb@research.att.com
Newsgroups: comp.sys.sun
Subject: Re: Reading Sun 3 timer register within Kernel device driver
Keywords: SunOS
Message-ID: <3993@brazos.Rice.edu>
Date: 21 Dec 89 02:42:07 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 8
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v8n207, Replies: v8n215 v8n220
X-Sun-Spots-Digest: Volume 8, Issue 228, message 5 of 18

There are easier things to do than reading the clock chip.  For one thing,
there's an external struct timeval named 'time'; it's the variable the
gettimeofday() system call uses to return the current time.  (As such, of
course, it's limited to the precision of that call.)  Actually, that's not
quite true; there's a subroutine uniqtime() that takes a struct timeval*
as a parameter; it returns that structure, but will increment the
low-order bit (i.e., the microsecond value) to ensure that no two calls
yield the exact same time.