From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon /proc/cpuinfo anomaly [minor]
Date: 25 Nov 2001 13:36:14 -0800 [thread overview]
Message-ID: <9tro8e$po1$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111221653290.28285-100000@netfinity.realnet.co.sz> <Pine.LNX.4.33.0111221552260.20788-100000@Appserv.suse.de>
Followup to: <Pine.LNX.4.33.0111221552260.20788-100000@Appserv.suse.de>
By author: Dave Jones <davej@suse.de>
In newsgroup: linux.dev.kernel
>
> On Thu, 22 Nov 2001, Zwane Mwaikambo wrote:
>
> > hmm i've always been under the impression that those strings are hard
> > encoded into the CPU so even if we're on a motherboard/bios which doesn't
> > "support" that particular CPU we can do a cpuid and get the same string.
>
> It likely has a less descriptive hardware default, but it can be
> (and is advised to be for bios writers) overridden in software.
>
No, the defaults are in the CPU if the CPU is recent enough.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2001-11-25 21:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 14:57 Athlon /proc/cpuinfo anomaly [minor] Zwane Mwaikambo
2001-11-22 14:53 ` Dave Jones
2001-11-25 21:36 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-21 9:53 Alastair Stevens
2001-11-21 11:18 ` Alan Cox
2001-11-21 11:19 ` Alastair Stevens
2001-11-21 11:20 ` Jens Axboe
2001-11-21 11:42 ` Dave Jones
2001-11-21 11:47 ` Jens Axboe
2001-11-21 11:55 ` Dave Jones
2001-11-21 12:08 ` Jens Axboe
2001-11-21 12:19 ` Dave Jones
2001-11-21 15:41 ` Matthew Sell
2001-11-21 11:49 ` Stefan Smietanowski
2001-11-21 11:40 ` Dave Jones
2001-11-21 23:44 ` Stuart Young
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='9tro8e$po1$1@cesium.transmeta.com' \
--to=hpa@zytor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.