From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Oleg I. Vdovikin" <vdovikin@jscc.ru>
Cc: Richard Henderson <rth@twiddle.net>,
alan@redhat.com, torvalds@transmeta.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch] Re: alpha - generic_init_pit - why using RTC for calibration?
Date: Thu, 05 Jul 2001 04:47:38 -0400 [thread overview]
Message-ID: <3B4429AA.208BB183@mandrakesoft.com> (raw)
In-Reply-To: <022901c10095$f4fca650$4d28d0c3@jscc.ru> <20010629211931.A582@jurassic.park.msu.ru> <20010704114530.A1030@twiddle.net> <003e01c10522$1c9cf580$4d28d0c3@jscc.ru> <3B441618.638A3FC@mandrakesoft.com> <00a001c1052d$a3201320$4d28d0c3@jscc.ru>
Oleg,
How is this relative to HZ, when you remove all references to HZ?
> -#define CALIBRATE_LATCH (52 * LATCH)
> -#define CALIBRATE_TIME (52 * 1000020 / HZ)
> +#define CALIBRATE_LATCH 0xffff
[...]
> + /* and the final result in HZ */
> + return ((unsigned long)cc * CLOCK_TICK_RATE) / CALIBRATE_LATCH;
and in asm-alpha/timex.h,
> #define CLOCK_TICK_RATE 1193180 /* Underlying HZ */
--
Jeff Garzik | Thalidomide, eh?
Building 1024 | So you're saying the eggplant has an accomplice?
MandrakeSoft |
next prev parent reply other threads:[~2001-07-05 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 12:20 alpha - generic_init_pit - why using RTC for calibration? Oleg I. Vdovikin
2001-06-29 17:19 ` Ivan Kokshaysky
2001-07-02 9:52 ` Oleg I. Vdovikin
2001-07-03 13:06 ` Oleg I. Vdovikin
2001-07-04 18:45 ` [patch] " Richard Henderson
2001-07-05 7:14 ` Oleg I. Vdovikin
[not found] ` <3B441618.638A3FC@mandrakesoft.com>
2001-07-05 8:36 ` Oleg I. Vdovikin
2001-07-05 8:47 ` Jeff Garzik [this message]
2001-07-06 8:45 ` Oleg I. Vdovikin
2001-07-05 9:43 ` Ivan Kokshaysky
2001-07-06 9:03 ` Oleg I. Vdovikin
2001-07-06 12:00 ` Ivan Kokshaysky
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=3B4429AA.208BB183@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=torvalds@transmeta.com \
--cc=vdovikin@jscc.ru \
/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