From: Matthew Wilcox <willy@debian.org>
To: Tom <palinux@alaskatech.org>
Cc: Grant Grundler <grundler@puffin.external.hp.com>,
"James P. Kinney III" <jkinney@localnetsolutions.com>,
palinux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Firmware upgraded, STI console problem
Date: Wed, 12 Dec 2001 21:02:42 +0000 [thread overview]
Message-ID: <20011212210242.E22198@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0112121147380.4162-100000@goliath.alaskatech.org>; from palinux@alaskatech.org on Wed, Dec 12, 2001 at 11:50:02AM -0900
On Wed, Dec 12, 2001 at 11:50:02AM -0900, Tom wrote:
> Okay - is there some short of note on which systems are 32-bit and which
> are 64-bit? Something like, "PA7000-series are 32-bit, PA-8000 (up to the
> 8x00) is 64-bit with 32-bit PDC and PA-8000 (after 8x00) is fully 64-bit".
> I just picked up a C180 and have a line on a C240 and was beginning to
> wonder the same things...
workstations: everything up to C360/J2240 has 32-bit firmware; B1000
and up have dual-32/64 bit firmware.
servers: N, L & A500 have 64-bit only firmware; A180 is 32-bit only.
don't know about other models.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2001-12-12 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 19:34 [parisc-linux] Firmware upgraded, STI console problem James P. Kinney III
2001-12-12 19:57 ` Matthew Wilcox
2001-12-12 20:39 ` Grant Grundler
2001-12-12 20:50 ` Tom
2001-12-12 21:02 ` Matthew Wilcox [this message]
[not found] ` <1008218517.2031.1.camel@crudball>
2001-12-13 5:20 ` Matthew Wilcox
2001-12-13 14:21 ` Ryan Bradetich
2001-12-14 18:58 ` 735 and SCSI (was: Re: [parisc-linux] Firmware upgraded, STI console problem) Phil Anderson
2001-12-14 22:55 ` Richard Hirst
2001-12-17 5:43 ` Ryan Bradetich
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=20011212210242.E22198@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=grundler@puffin.external.hp.com \
--cc=jkinney@localnetsolutions.com \
--cc=palinux@alaskatech.org \
--cc=parisc-linux@lists.parisc-linux.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