RE: Wall clock accuracy

=20

-----Original Message-----
From: Eugene Surovegin [mailto:ebs@ebshome.net]=20
Sent: Tuesday, August 09, 2005 12:21

Fair enough, why then instead of fixing the root cause you are making=20
ugly workarounds :) ?

Probably because I did not want to fiddle with the code that did the
original calculation, and I wanted to see if I could get it totally
accurate (for the case where there is not a whole number of ns in a
jiffy).

A proper fix would be for platfrom code to have a way to set time_nsec
instead of having it set by a constant.

I did say in my original email that thencluded code was not a proper
patch but more something to show on how a fix could look like, and to
start a discussion about it.

On Tue, Aug 09, 2005 at 01:21:09PM -0500, Rune Torgersen wrote:

A proper fix would be for platfrom code to have a way to set time_nsec
instead of having it set by a constant.

Or configure CLOCK_TICK_RATE in board/CPU specific fashion, e.g. like 
ARM does.

-- 
Eugene