From: Tim Riker <TimR@CalderaSystems.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Processor Rev.
Date: Thu, 10 Aug 2000 03:54:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205304@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205295@msgid-missing>
There is some documentation on serial #s (the stickers not the
electronic IDs) in the Intel literature. In my "Intel Workstation SDV,
A1 Stepping Processor Replacement" manual there is a section on page 20
entitled "Identification of Upgrade Processor Stepping" with a table
mapping the 4 digit postfix to the A2 and A3 stepping. This also
includes some comments about the state of software revision detection.
I do not know if this info is truly public, so I have not copied this
info here. Perhaps someone from Intel would like to comment?
These postfixes are of the format Q[letter][number][number]. I would
assume there is a complete table available someplace that would include
A1-A3 and B0-B1 stepping maps, but I have not seen it.
The only reliable option I know of is to open a QuAD ticket on the
system and ask Intel.
Don Dugger wrote:
>
> John-
>
> The only way to find the revision that I know of is to check the
> paper work that came with your machine, that should list it. There's
> no instruction that will give that information at this point in
> time.
>
> On Wed, Aug 09, 2000 at 11:55:28AM -0400, John Baboval wrote:
> > What is a good way to check the processor revision on the lion machines. I
> > see people on the list refering to A1 or A2 stepping machines, but /proc/cpuinfo on
> > our machines only shows this:
> >
> > processor : 3
> > vendor : GenuineIntel
> > family : IA-64
> > model : Itanium
> > revision : 0
> > archrev : 0
> >
> > plus the serial numbers and MHz and such. Does this just mean we have old
> > CPUs, or is there a different way to check?
> >
> > --
> > John V. Baboval (baboval@missioncriticallinux.com)
> --
> Don Dugger
> "Censeo Toto nos in Kansa esse decisse." - D. Gale
> n0ano@valinux.com
> Ph: 303/938-9838
--
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.
prev parent reply other threads:[~2000-08-10 3:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-09 10:53 [Linux-ia64] Processor Rev Gerrit.Huizenga
2000-08-09 15:55 ` John Baboval
2000-08-09 16:54 ` Don Dugger
2000-08-09 21:34 ` Stephane Eranian
2000-08-09 21:41 ` Broadfoot, KenX
2000-08-09 21:52 ` David Mosberger
2000-08-09 21:58 ` Chris McDermott/Beaverton/IBM
2000-08-10 3:54 ` Tim Riker [this message]
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=marc-linux-ia64-105590678205304@msgid-missing \
--to=timr@calderasystems.com \
--cc=linux-ia64@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