From: Scott Ashcroft <scott.ashcroft@talk21.com>
To: linux-mips@linux-mips.org
Subject: [PATCH] Time runs too quickly on Cobalt
Date: Fri, 06 Oct 2006 16:54:54 +0100 [thread overview]
Message-ID: <45267C4E.8090101@talk21.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
If I build a kernel with HZ==250 then time runs about 4 four times too
quickly on my Cobalt RaQ2.
The following patch seems to fix it but I'm not sure this is the correct
thing to do.
Signed-off-by: Scott Ashcroft <scott.ashcroft@talk21.com>
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 551 bytes --]
diff --git a/arch/mips/cobalt/setup.c b/arch/mips/cobalt/setup.c
index c01a017..f7c6eb2 100644
--- a/arch/mips/cobalt/setup.c
+++ b/arch/mips/cobalt/setup.c
@@ -51,8 +51,8 @@ const char *get_system_type(void)
void __init plat_timer_setup(struct irqaction *irq)
{
- /* Load timer value for 1KHz (TCLK is 50MHz) */
- GALILEO_OUTL(50*1000*1000 / 1000, GT_TC0_OFS);
+ /* Load timer value for HZ (TCLK is 50MHz) */
+ GALILEO_OUTL(50*1000*1000 / HZ, GT_TC0_OFS);
/* Enable timer */
GALILEO_OUTL(GALILEO_ENTC0 | GALILEO_SELTC0, GT_TC_CONTROL_OFS);
next reply other threads:[~2006-10-06 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 15:54 Scott Ashcroft [this message]
2006-10-07 23:32 ` [PATCH] Time runs too quickly on Cobalt Ralf Baechle
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=45267C4E.8090101@talk21.com \
--to=scott.ashcroft@talk21.com \
--cc=linux-mips@linux-mips.org \
/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