mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@inf.utfsm.cl>
To: Rolf Fokkens <fokkensr@fokkensr.vertis.nl>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USER_HZ & NTP problems
Date: Wed, 11 Sep 2002 18:36:22 -0400	[thread overview]
Message-ID: <200209112236.g8BMaMMD016898@pincoya.inf.utfsm.cl> (raw)
In-Reply-To: Message from Rolf Fokkens <fokkensr@fokkensr.vertis.nl>  of "Tue, 10 Sep 2002 08:37:17 +0200." <200209100637.g8A6bMm01628@fokkensr.vertis.nl>

Rolf Fokkens <fokkensr@fokkensr.vertis.nl> said:
> On Tuesday 10 September 2002 08:09, Vojtech Pavlik wrote:
> > Actually, the clock true frequency is 1193181.8 Hz, although most
> > manuals say 1.19318 MHz, which, because truncating more digits, also
> > correct. But 1193180 Hz isn't. If you're trying to count the time
> > correctly, you should better use 1193182 Hz if staying in integers.
> 
> I copied the clock frequency from the kernel source, timex.h defines:
> 
> #define CLOCK_TICK_RATE 1193180
> 
> If what you're saying is correct, timex.h uses the wrong value as wel I guess.

I'd be _really_ surprised if that number is within 1% (+-11932 or so)
correct, an error in the last digit (0.0001%) is surely lost. 
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

  parent reply	other threads:[~2002-09-11 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 23:14 Rolf Fokkens
2002-09-10  6:09 ` Vojtech Pavlik
2002-09-10  6:37   ` Rolf Fokkens
2002-09-10  6:48     ` Vojtech Pavlik
2002-09-11 22:36     ` Horst von Brand [this message]
2002-09-11 22:56       ` george anzinger
2002-09-12  6:27         ` Vojtech Pavlik
2002-09-12  6:23       ` Vojtech Pavlik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200209112236.g8BMaMMD016898@pincoya.inf.utfsm.cl \
    --to=vonbrand@inf.utfsm.cl \
    --cc=fokkensr@fokkensr.vertis.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®