All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Brandon Barker <bebarker@meginc.com>
Cc: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Indy 64 or 32 bit?
Date: Tue, 7 Aug 2001 16:42:49 +0200	[thread overview]
Message-ID: <20010807164249.B26419@bacchus.dhis.org> (raw)
In-Reply-To: <01080623471400.01828@linux>; from bebarker@meginc.com on Mon, Aug 06, 2001 at 11:47:36PM -0400

On Mon, Aug 06, 2001 at 11:47:36PM -0400, Brandon Barker wrote:

> I will be purchasing 2 SGI Indy R5000 models from reputable.com, and was 
> curious if these are 64 bit systems or 32 bit systems (for that matter, are 
> all/any Indys 32 or 64 bit systems).  My guess is 64 because I wiould think 
> IRIX has been 64 for quite some time, but was curious.  I use Linux on x86 
> but will probably use IRIX for a few weeks on the Indy's until I become 
> familiar enough with the machines to try installing Linux.  BTW, does gcc 
> work on IRIX?

By hardwareware it's a 64-bit system - like all SGI systems we support.
The kernel is just a 32-bit one though which is a reasonable compromise
for these systems.

  Ralf

  parent reply	other threads:[~2001-08-07 14:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07  3:47 Indy 64 or 32 bit? Brandon Barker
2001-08-07  3:56 ` George Gensure
2001-08-07  4:03   ` nick
2001-08-07  4:11     ` Nils C. Anderson
2001-08-07  4:11       ` Nils C. Anderson
2001-08-07 14:42 ` Ralf Baechle [this message]
2001-08-08  0:45 ` J. Scott Kasten
2001-08-08 10:17   ` Ralf Baechle
2001-08-08 15:02     ` J. Scott Kasten
2001-08-08 15:18       ` Ralf Baechle
2001-08-08 15:41         ` Thiemo Seufer
2001-08-08 20:12           ` J. Scott Kasten
2001-08-08 21:16             ` Thiemo Seufer
2001-08-09 12:08             ` Ralf Baechle

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=20010807164249.B26419@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=bebarker@meginc.com \
    --cc=linux-mips@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.