From: Android <android@abac.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.18 release notes
Date: Mon, 11 Dec 2000 21:24:22 +0000 [thread overview]
Message-ID: <00121121242201.00885@cy60022-a> (raw)
In-Reply-To: <E145f1E-0000a9-00@the-village.bc.nu>
In-Reply-To: <E145f1E-0000a9-00@the-village.bc.nu>
> ... added basic support for the Pentium IV. Unfortunately Intel
chose to
> ignore all precedent in model numbering via cpuid and report a
> family of '15'. This sudden jump broke assumptions in the
> kernel tree without any warning. Intel have failed to provide
> good reasons for their change. We have chosen to continue to
> report the Pentium IV as a '686' class processor. The full
> family data is provided via cpuinfo.
>
> In addition the early Pentium IV chips appear to have some
> problems. You should be using stepping 7 or higher processors
> with the latest shipping microcode update if you wish to run
> Linux on a Pentium IV processor.
>
> + Intel Pentium IV support
How is the Pentium IV more advanced than the Pentium III, other than speed?
Why would LInux care about a 1500 MHz clock or 400 MHz bus speed?
Just treat the PIV as a faster PIII.
-- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-12 5:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 2:18 Linux 2.2.18 release notes Alan Cox
2000-12-11 21:24 ` Android [this message]
2000-12-12 5:39 ` Peter Samuelson
2000-12-12 10:30 ` Bruce Korb
2000-12-12 12:28 ` Alan Cox
2000-12-13 1:24 ` Igmar Palsenberg
2000-12-13 1:28 ` Mark Hahn
2000-12-12 3:30 ` Paul Fulghum
2000-12-12 3:47 ` Peter Samuelson
2000-12-12 12:26 ` Alan Cox
2000-12-12 12:28 ` Lars Marowsky-Bree
2000-12-12 11:31 ` David Weinehall
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=00121121242201.00885@cy60022-a \
--to=android@abac.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