public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: SAL version checking
Date: Mon, 23 Feb 2004 21:21:01 +0000	[thread overview]
Message-ID: <20040223212101.GH25779@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040223210103.GG25779@parcelfarce.linux.theplanet.co.uk>

On Mon, Feb 23, 2004 at 01:09:20PM -0800, Jesse Barnes wrote:
> It looks reasonable to me, though I thought we were the only ones that
> cared about PROM revisions ;).  If you go ahead and push this in, we
> could use it in arch/ia64/sn/kernel/setup.c, where we check for
> incompatibilties bad enough to cause us to bail out...

Well, you *were* the only ones who cared about SAL revisions ;-)
Actually, this isn't quite what you want.  I'm asking the firmware
what rev of the SAL spec it reports; you want version number of the
prom.  I want sal_rev_major/minor; you want sal_b_rev_major/minor.

I don't see why we shouldn't do both, and possibly even print both.
I've occasionally wondered what rev of firmware I'm running and
rebooting to figure that out is less satisfactory than grovelling through
/var/log/dmesg.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  parent reply	other threads:[~2004-02-23 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 21:01 SAL version checking Matthew Wilcox
2004-02-23 21:09 ` Jesse Barnes
2004-02-23 21:21 ` Matthew Wilcox [this message]
2004-02-23 21:43 ` Jesse Barnes

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=20040223212101.GH25779@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --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