From: Alexei Gerasimov <alex@netbynet.ru>
To: linux-ia64@vger.kernel.org
Subject: Re: Linux on Intel "Big Sur"
Date: Mon, 10 Dec 2007 19:11:14 +0000 [thread overview]
Message-ID: <475DB7BE.5080309@netbynet.ru> (raw)
In-Reply-To: <475C2CF3.9010206@netbynet.ru>
Bjorn Helgaas wrote:
> I've only used the HP i2000 version, and even that's been a long time,
> but my guess is that the firmware upgrade would be safe, and that the
> appropriate HP-UX version would probably run on it.
>
I've discovered a small detail about updates: the firmware update seems
to be safe, but the BIOS update (to the version 1.30) available from the
HP website is marked as for CPU's with C2 stepping. According to my
CPUID, my Itanium's are C0 stepping, therefore an update to the version
dedicated for CPU's with different stepping might be fatal. Personally,
I don't know what stepping is, thus cannot be sure to make any
conclusions. What do you think about this?
Alex.
next prev parent reply other threads:[~2007-12-10 19:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 15:36 Linux on Intel "Big Sur" Alexei Gerasimov
2007-12-10 17:11 ` Luck, Tony
2007-12-10 18:33 ` Bjorn Helgaas
2007-12-10 19:11 ` Alexei Gerasimov [this message]
2007-12-11 0:09 ` Bjorn Helgaas
2007-12-11 6:17 ` Peter Chubb
2007-12-11 12:21 ` Robin Holt
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=475DB7BE.5080309@netbynet.ru \
--to=alex@netbynet.ru \
--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