> > well, it's not exactly 508 kHz as the docs claims, but it's 14.7456 Mhz
> > divided by 29 = 508496. The timer is 16-bit only, you can't feed it with
> > this value anyway.
Yeah, I noticed... =)
It's one of those things that you should list as the first things to check
when the results aren't as expected. (As well as not using N as the last index
to a N-size array...)
> Actually I found 5084 gives a better system clock. Using adjtimex and some
> clockwatching allows one to have a system clock with an accuracy of about
> 2ppm (assuming a fairly constant environment). That's about 1 sec drift in
> 5 days.
While on the subject... It looks like in the code that Timer 4 is actually
used to compensate for the driftoff somehow. If not, what is the purpose of
counting "lost jiffies" as the comment says?
Thanks
Per Öberg
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|