Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: lm@neteng.engr.sgi.com (Larry McVoy)
To: Steve Alexander <sca@refugee.engr.sgi.com>
Cc: "Christopher W. Carlson" <carlson@heaven.newport.sgi.com>,
	linux@cthulhu.engr.sgi.com
Subject: Re: Getting X on Linux/SGI
Date: Fri, 20 Jun 1997 00:34:26 -0700	[thread overview]
Message-ID: <199706200734.AAA18987@neteng.engr.sgi.com> (raw)

: "Christopher W. Carlson" <carlson@heaven.newport.sgi.com> writes:
: >My point was that SGI is into making hardware.  That's how it started
: >and that is still its main focus.  Yes, it is true that our software
: >is very important because it takes advantage of the proprietary stuff
: >in the hardware, but the main income for SGI is hardware.
: 
: How many people buy the hardware and program the bare metal?

We own MIPS.  MIPS sold or licensed 19.2 million chips last year.  About
19 million of those were of the type "program the bare metal".

Much of the Linux/MIPS interest is for embedded systems.  We should have
done this years ago, there is no reason why not to do it other than NIH.

             reply	other threads:[~1997-06-20  7:34 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-20  7:34 Larry McVoy [this message]
1997-06-20  9:55 ` Getting X on Linux/SGI William Fisher
1997-06-20  9:17   ` David S. Miller
1997-06-20 10:12     ` Ralf Baechle
1997-06-20 10:12       ` Ralf Baechle
1997-06-20 20:16     ` Nigel Gamble
1997-06-20  9:55   ` William Fisher
1997-06-20 13:42   ` Todd Shrider
1997-06-20 14:07     ` Ralf Baechle
1997-06-20 14:07       ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
1997-06-24  0:55 Steve Alexander
1997-06-22 17:50 Larry McVoy
1997-06-22 17:50 ` Larry McVoy
1997-06-23 19:43 ` Christopher W. Carlson
1997-06-22 17:36 Larry McVoy
1997-06-20 21:43 Steve Alexander
1997-06-20 21:43 ` Steve Alexander
1997-06-20 16:45 Larry McVoy
1997-06-20 17:06 ` Todd Shrider
1997-06-20 16:40 Larry McVoy
1997-06-20 16:51 ` Mike Shaver
1997-06-20 16:51   ` Mike Shaver
1997-06-20 16:59 ` richard offer
1997-06-20  8:39 Steve Alexander
1997-06-20 15:22 ` Martin Knoblauch
1997-06-20  7:59 Steve Alexander
1997-06-20  7:59 ` Steve Alexander
1997-06-20  8:16 ` David S. Miller
1997-06-20  7:21 Steve Alexander
     [not found] ` <sca@refugee.engr.sgi.com>
1997-06-20 17:28   ` Christopher W. Carlson
1997-06-23  7:07     ` Martin Knoblauch
1997-06-23 19:31   ` Christopher W. Carlson
1997-06-18 23:16 Larry McVoy
1997-06-18 23:42 ` Nigel Gamble
     [not found]   ` <nigel@cthulhu.engr.sgi.com>
1997-06-19 15:46     ` Christopher W. Carlson
1997-06-19  6:40 ` Ralf Baechle
1997-06-19  6:40   ` Ralf Baechle
     [not found] <199706181641.JAA05598@darwin.esd.sgi.com>
1997-06-18 19:41 ` John Chen
1997-06-18 19:41   ` John Chen
1997-06-18 19:56   ` David S. Miller
1997-06-18 20:15     ` Alex deVries
1997-06-19 20:01       ` William J. Earl
1997-06-18  0:00 Good news: no more begging for HW John Wiederhirn
1997-06-18  0:34 ` Getting X on Linux/SGI Ariel Faigon
1997-06-18  0:34   ` Ariel Faigon
1997-06-18 16:28   ` Christopher W. Carlson
1997-06-18 19:30     ` Nigel Gamble

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=199706200734.AAA18987@neteng.engr.sgi.com \
    --to=lm@neteng.engr.sgi.com \
    --cc=carlson@heaven.newport.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=sca@refugee.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