Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: lm@gate1-neteng.engr.sgi.com (Larry McVoy)
To: "Greg Chesson" <greg@xtp.engr.sgi.com>
Cc: "Alistair Lambie" <alambie@wellington.sgi.com>,
	linux@cthulhu.engr.sgi.com
Subject: Re: MIPS port kickoff meeting
Date: Tue, 23 Apr 1996 10:22:54 -0700	[thread overview]
Message-ID: <199604231722.KAA13743@neteng.engr.sgi.com> (raw)

Greg said:
: There are US Gov't customers for Linux on SGI boxes who require
: 64-bit OS.  So, let's support tho 32-bit ARCS boxes without compromising
: opportunities to sell new boxes (with 64-bit Linux).

We definitely want to do this.  And I don't want to do anything to derail
this because I want this badly.  And what I'm about to say does not imply 
that we don't do 64bit - I want both.  And it should be easy to do both.

One reason for thinking small, however, is that we could finesse the whole
Linux vs IRIX issue by raising awareness that Linux on MIPs could be a
really nice solution for the embedded market.  I personally would love
to see a full page in IEEE times in which MIPS announces the availablity
of embedded Linux for MIPs chips.  This may be the quickest path to getting
Linux embraced internally.  I'm pretty sure that Cygnus would be interested
in signing up for support for such a platform - that is a big part of their
business.  And I think that R3K is still the volume chip in the embedded
market, so we want that to work.

Thoughts?

             reply	other threads:[~1996-04-23 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-04-23 17:22 Larry McVoy [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-04-23 17:25 MIPS port kickoff meeting Larry McVoy
1996-04-20  0:22 Ariel Faigon
1996-04-23 14:15 ` Alistair Lambie
1996-04-23 16:39   ` Greg Chesson
1996-04-24  2:05     ` David S. Miller
1996-04-24  4:31       ` Greg Chesson

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=199604231722.KAA13743@neteng.engr.sgi.com \
    --to=lm@gate1-neteng.engr.sgi.com \
    --cc=alambie@wellington.sgi.com \
    --cc=greg@xtp.engr.sgi.com \
    --cc=linux@cthulhu.engr.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