public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan_Kwahk@Dell.com
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] Two questions
Date: Wed, 07 Mar 2001 19:32:49 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005260@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005254@msgid-missing>

Obviouslly, W460GXBS2 is the chipset notation (Workstation 460GX chipset,
Big Sur).
89B is the build number for the BIOS.
P03 is production build.  In this case, it's build 3.

If I recall correctly (it's been a very long time), the last string includes
the date of build.  I'm not sure what the other digits mean.

J

-----Original Message-----
From: Hall, Jenna S [mailto:jenna.s.hall@intel.com]
Sent: Wednesday, March 07, 2001 12:01 PM
To: linux-ia64@linuxia64.org
Subject: RE: [Linux-ia64] Two questions


As far as the 30+ digit BIOS revision, the only significant part would be
the "0089B" in the number below:

W460GXBS2.86E.0089B.P03.200012151745

So that's all you really have to record or report to Intel when clarifying
BIOS revision.

Jenna

-----Original Message-----
From: Stephane Eranian [mailto:eranian@frankl.hpl.hp.com]
Sent: Wednesday, March 07, 2001 9:35 AM
To: linux-ia64@linuxia64.org
Subject: Re: [Linux-ia64] Two questions


On Wed, Mar 07, 2001 at 12:19:05PM +0100, Francis Galiegue wrote:
> 1. Where can I get precise info about firmware revisions, etc etc? I only
know
> about what a 'ver' displays at the EFI prompt and what the files in /proc
> display... As to noting the 30+ digit BIOS revision, I do it by hand for
now...

Could you explain exactly what do you mean by precise ? version numbers ?
If so, you can get the pal version in  /proc/pal/cpu0/version_info. As for
EFI and SAL, at this point, there is no /proc interface to them. So your
only chance is by dmesg because the kernel prints the versions when it
boots.
The rest is probably coming from ACPI, I guess.

--
-Stephane

_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64


_______________________________________________
Linux-IA64 mailing list
Linux-IA64@linuxia64.org
http://lists.linuxia64.org/lists/listinfo/linux-ia64


  parent reply	other threads:[~2001-03-07 19:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07 11:19 [Linux-ia64] Two questions Francis Galiegue
2001-03-07 13:35 ` Matt_Domsch
2001-03-07 17:35 ` Stephane Eranian
2001-03-07 18:01 ` Hall, Jenna S
2001-03-07 18:06 ` Jim Wilson
2001-03-07 19:32 ` Jonathan_Kwahk [this message]
2001-03-09 21:18 ` Khalid Aziz

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-105590693005260@msgid-missing \
    --to=jonathan_kwahk@dell.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