Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "J. Scott Kasten" <jsk@tetracon-eng.net>
Cc: Brandon Barker <bebarker@meginc.com>,
	"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: Indy 64 or 32 bit?
Date: Wed, 8 Aug 2001 12:17:06 +0200	[thread overview]
Message-ID: <20010808121706.A602@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.SGI.4.33.0108072030380.20792-100000@thor.tetracon-eng.net>; from jsk@tetracon-eng.net on Tue, Aug 07, 2001 at 08:45:17PM -0400

On Tue, Aug 07, 2001 at 08:45:17PM -0400, J. Scott Kasten wrote:

> Well, it's kind of both.  The R4000 and up are 64 bit CPU's capable of
> running either 32 or 64 bit code.  The MIPS address space is a little
> wierd such that you can kinda munge 32 and 64 bit code togeather under the
> right circumstances.

Right circumstances = almost always.  Actually Linux makes sure that it's
indeed always.

> Some of the old hands here could tell you better how Irix behaves on those
> boxes.  I know you can compile code with 64 bit int and pointers and it
> will run on those boxes under Irix, but there is a little more to it than
> that.

That's not supported on all systems.  An Indy for example is limited to
128mb RAM as shipped by SGI (256 with aftermarket parts).  There is no
point in supporting 64-bit address space on such a system and so SGI doesn't
support only N32.

> I've used both linux and Irix on the Indy.  Quite frankly, I would
> consider getting a second HD if cheep enough so that you could keep both
> around.  (Note: don't put 2 high RPM drives in the Indy, or we are talking
> melt down of your pretty blue toy...)

External drives work just fine and can be hidden where their sound isn't so
annoying.

> I've found much to like in Irix in addition to the flexibility of Linux.

Yep and they co-exist nicely.

  Ralf

  reply	other threads:[~2001-08-08 10:19 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
2001-08-08  0:45 ` J. Scott Kasten
2001-08-08 10:17   ` Ralf Baechle [this message]
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=20010808121706.A602@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=bebarker@meginc.com \
    --cc=jsk@tetracon-eng.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox