From: "Chris McDermott/Beaverton/IBM" <mcdermoc@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Processor Rev.
Date: Wed, 09 Aug 2000 21:58:11 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205300@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205295@msgid-missing>
It happened here on 2 entries: perfmon_info and power_info.
Chris
Stephane Eranian <eranian@frankl.hpl.hp.com>@linuxia64.org on 08/09/2000
02:34:06 PM
Please respond to <eranian@hpl.hp.com>
Sent by: linux-ia64-admin@linuxia64.org
To: linux-ia64@linuxia64.org
cc:
Subject: Re: [Linux-ia64] Processor Rev.
Hi,
>
> [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.
In the latest kernel patch the output is slightly different. Here the minor
number is .9. So 0x22 0x9 is read 2.2.9 for PAL version.
>
> Also, reading one of the files here caused a panic with the B1 CPU
steppings.
>
Yes, I am aware of this problem. I noticed yesterday while trying it out
on our B1. I don't recall exactly which entry it is. I will be checking
for that.
_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64
next prev parent reply other threads:[~2000-08-09 21:58 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 [this message]
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-105590678205300@msgid-missing \
--to=mcdermoc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox