From: Dave Jones <davej@suse.de>
To: Patrick Mochel <mochel@osdl.org>
Cc: Markus Pfeiffer <profmakx@profmakx.org>, linux-kernel@vger.kernel.org
Subject: Re: CPU detection broken in 2.5.27?
Date: Tue, 23 Jul 2002 22:34:56 +0200 [thread overview]
Message-ID: <20020723223456.C16446@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0207231314390.954-100000@cherise.pdx.osdl.net>; from mochel@osdl.org on Tue, Jul 23, 2002 at 01:26:38PM -0700
On Tue, Jul 23, 2002 at 01:26:38PM -0700, Patrick Mochel wrote:
> Heh. They've always been there, then. I really did re-add the table from
> an older arch/i386/kernel/setup.c ;)
>
> The Celeron detection happens in init_intel().
Ah, ok. Then all those cases should magically work..
> Added. Wait, isn't Foster the one with HT?
AFAIK yes. Don't have one to test with, so can't say for sure.
> The ones I have say that they
> support it, so wouldn't that be a Foster (as well as stepping 5)?
Which stepping do you have ?
> Updated patch appended. This updated version hasn't been tested, as I
> don't have any of those processors at my disposal...
-ENOAPPENDAGE.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-07-23 20:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-21 13:37 heavy Disk I/O and system stops reacting for seconds Marc-Christian Petersen
2002-07-21 14:17 ` Adrian Bunk
2002-07-21 15:34 ` Marc-Christian Petersen
2002-07-21 16:07 ` CPU detection broken in 2.5.27? Markus Pfeiffer
2002-07-21 16:41 ` Dave Jones
2002-07-23 19:14 ` Patrick Mochel
2002-07-23 19:29 ` Dave Jones
2002-07-23 20:26 ` Patrick Mochel
2002-07-23 20:34 ` Dave Jones [this message]
2002-07-23 20:34 ` Patrick Mochel
2002-07-23 20:56 ` Dave Jones
2002-07-23 21:08 ` Patrick Mochel
2002-07-21 16:45 ` Time problem with 2.5.27 on Intel (and kernel freezes...) Oliver Pitzeier
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 0:52 CPU detection broken in 2.5.27? Mikael Pettersson
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=20020723223456.C16446@suse.de \
--to=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=profmakx@profmakx.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