All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerrit.Huizenga@us.ibm.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Processor Rev.
Date: Wed, 09 Aug 2000 10:53:49 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205295@msgid-missing> (raw)

In addition to /proc/cpuinfo, there's a bunch of interesting stuff
in /proc/palinfo/*, for instance:

[gerrit@elm3a86 palinfo]$ cat /proc/palinfo/version_info
PAL_vendor     : 0xff (min=0xff)
PAL_A revision : 0x9 (min=0x9)
PAL_A model    : 0x22 (min=0x22)
PAL_B mode     : 0x9 (min=0x0)
PAL_B revision : 0x22 (min=0x0)

There is other stuff of interest in /proc/palinfo.

Chris pointed out that the minor numbers of the version aren't included here.

Also, reading one of the files here caused a panic with the B1 CPU steppings.

gerrit

> 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)
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 


             reply	other threads:[~2000-08-09 10:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-09 10:53 Gerrit.Huizenga [this message]
2000-08-09 15:55 ` [Linux-ia64] Processor Rev 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

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-105590678205295@msgid-missing \
    --to=gerrit.huizenga@us.ibm.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 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.