From: Giacomo Catenazzi <cate@student.ethz.ch>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: "Giacomo A . Catenazzi" <cate@dplanet.ch>, linux-kernel@vger.kernel.org
Subject: Re: Coppermine is a PIII or a Celeron?
Date: Mon, 08 Jan 2001 11:09:00 +0100 [thread overview]
Message-ID: <3A5991BC.64525AF7@student.ethz.ch> (raw)
In-Reply-To: <fa.dl37erv.6j04hb@ifi.uio.no> <fa.hcv7gqv.s3k9qk@ifi.uio.no>
"J . A . Magallon" wrote:
>
> On 2001.01.02 Giacomo A. Catenazzi wrote:
> > Hello!
> >
> > When working in cpu autoconfiguration I found some problems:
> >
> > I have to identify this processor:
> > Vendor: Intel
> > Family: 6
> > Model: 8
> > Is it a "Pentium III (Coppermine)" (setup.c:1709)
> > or a "Celeron (Coppermine)" (setup.c:1650) ?
> >
>
> AFAIK, both. Coppermine is the code name of the low level arch of
> the chip.
>
> Really, the kernel should be querying the builder: Have you a
> Deschutes, a Mendocino or a Coppermine ? How much cache do you have ?
> But that is rarely known (Uh? I bought a Pentium III). You have to
> guess from the answer to:
> Have you a PII, an old Celeron (Mendocino) or a new Cel-PIII (Copper).
>
Thus the older Celerons should be compiled with CONFIG_M686 (Pentium
Pro),
but the Celeron Coppermine can be compiled with CONFIG_M686FXSR (Pentium
III), right?
In this case we should update the files Configure.help and the config.in
files.
giacomo
-
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 parent reply other threads:[~2001-01-08 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.dl37erv.6j04hb@ifi.uio.no>
[not found] ` <fa.hcv7gqv.s3k9qk@ifi.uio.no>
2001-01-08 10:09 ` Giacomo Catenazzi [this message]
2001-01-08 14:12 ` Coppermine is a PIII or a Celeron? J . A . Magallon
2001-01-08 21:25 ` Erik Mouw
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=3A5991BC.64525AF7@student.ethz.ch \
--to=cate@student.ethz.ch \
--cc=cate@dplanet.ch \
--cc=jamagallon@able.es \
--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