From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: linux@yon.engr.sgi.com
Subject: What target (was David ...)
Date: Tue, 23 Apr 1996 13:26:53 -0700 (PDT) [thread overview]
Message-ID: <199604232026.NAA00059@yon.engr.sgi.com> (raw)
In-Reply-To: <199604231951.MAA01292@titian> from "Mike McDonald" at Apr 23, 96 12:51:24 pm
Mike asked (not a dumb Q, BTW):
>
> A dumb question, what exactly is the purpose of porting Linux to
>SGI/Mips boxes?
>
Looks like there are many opinions. I don't care as long as we
manage to do this port. Whatever we port it to (and the wider the
port is) SGI is going to benefit tremendously. You may read
my Linux pages (http://info.engr/~ariel/linux) to understand why
my personal conviction (and others) is so strong.
Some of the nice things about Linux are:
1) It can work from RAM (virtual disk),
So it follows that it is easily ROMable and
embeddable (much more so than IRIX)
I have developed embedded apps for several years in my past
and I can tell you that my life would have been infinitely
easier had I been able to develop in a Linux env.
Only the thought of having the same env on the host
and the target is revolutionary by itself (and possible!)
2) It has a small footprint so naturally it is a good candidate
for embedded market.
3) It has a common single source code for 32-bit and 64-bit
machines (Alpha). So we shouldn't think of this as an "either/or"
proposition.
P.S.
gcc doesn't have support for 64 bit MIPS 27 ISA, I guess, but
nobody is stopping us from using our compilers (as well as gcc
at our convenience).
--
Peace, Ariel
next prev parent reply other threads:[~1996-04-23 20:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-23 19:51 David Miller is on the list Mike McDonald
1996-04-23 20:20 ` William J. Earl
1996-04-23 20:26 ` Ariel Faigon [this message]
1996-04-23 20:54 ` What target (was David ...) Mike McDonald
1996-04-23 22:27 ` Ariel Faigon
1996-04-23 22:27 ` Ariel Faigon
1996-04-23 22:43 ` Greg Chesson
1996-04-23 22:43 ` Greg Chesson
1996-04-23 22:39 ` 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=199604232026.NAA00059@yon.engr.sgi.com \
--to=ariel@yon.engr.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@yon.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 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.