From: takada <takada@mbf.nifty.com>
To: linux-kernel@vger.kernel.org
Subject: i386: pit_latch_buggy has no effect.
Date: Sat, 10 Feb 2007 17:34:45 +0900 (JST) [thread overview]
Message-ID: <20070210.173445.242527990.takada@mbf.nifty.com> (raw)
Hi.
Eliminated the arch/i386/kernel/timers in 2.6.18, use clocksoures instead.
pit_latch_buggy was referred in timers/timer_tsc.c, and currently removed.
Therefore nobody refer it.
Until 2.6.17, MediaGX's TSC works correctly. after 2.6.18, warned
"TSC appears to be running slowly. Marking it as unstable". So marked
unstable TSC when CS55x0.
diff -Naru a/arch/i386/kernel/cpu/cyrix.c b/arch/i386/kernel/cpu/cyrix.c
--- a/arch/i386/kernel/cpu/cyrix.c 2007-02-05 03:44:54.000000000 +0900
+++ b/arch/i386/kernel/cpu/cyrix.c 2007-02-10 16:11:31.000000000 +0900
@@ -278,7 +278,7 @@
* The 5510/5520 companion chips have a funky PIT.
*/
if (pci_dev_present(cyrix_55x0))
- pit_latch_buggy = 1;
+ mark_tsc_unstable();
#endif
c->x86_cache_size=16; /* Yep 16K integrated cache thats it */
diff -Naru a/arch/i386/kernel/time.c b/arch/i386/kernel/time.c
--- a/arch/i386/kernel/time.c 2007-02-05 03:44:54.000000000 +0900
+++ b/arch/i386/kernel/time.c 2007-02-10 16:12:04.000000000 +0900
@@ -70,8 +70,6 @@
#include <asm/i8259.h>
-int pit_latch_buggy; /* extern */
-
#include "do_timer.h"
unsigned int cpu_khz; /* Detected as we calibrate the TSC */
diff -Naru a/include/asm-i386/timer.h b/include/asm-i386/timer.h
--- a/include/asm-i386/timer.h 2007-02-05 03:44:54.000000000 +0900
+++ b/include/asm-i386/timer.h 2007-02-10 16:12:21.000000000 +0900
@@ -5,8 +5,6 @@
#define TICK_SIZE (tick_nsec / 1000)
void setup_pit_timer(void);
-/* Modifiers for buggy PIT handling */
-extern int pit_latch_buggy;
extern int timer_ack;
extern int recalibrate_cpu_khz(void);
reply other threads:[~2007-02-10 8:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070210.173445.242527990.takada@mbf.nifty.com \
--to=takada@mbf.nifty.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®