From: Martin Mielke <martin@jaleo.idecnet.com>
To: Ariel Faigon <ariel@cthulhu.engr.sgi.com>
Cc: "linux@cthulhu.engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: Port to R3000 Indigo
Date: Fri, 26 Mar 1999 22:21:01 +0000 [thread overview]
Message-ID: <36FC084C.52E747A5@jaleo.idecnet.com> (raw)
In-Reply-To: 199903262208.OAA31331@oz.engr.sgi.com
Ariel Faigon wrote:
> As Linus use to say: talk is cheap, show me the code... ;-)
>
> It won't happen by itself, only if someone devotes serious
> time to it. My personal feeling is that Linux on R3000
> will not happen (there are cheaper and faster old pentium 90's
> out there) but if someone builds it... I've been wrong before.
>
> :
> :And I know a group at KSC that's getting rid of a bunch of O2s. We'd love to
> :grab them and make a nice little Beowulf cluster out of them :-).
> :Unfortunately, we don't have the time at work to do a port :-(
> :
> :> I think it would be very relevant. My company recently sold around 30
> :> of the R3000 Indigo's. Just about every person who bought one of these
> :> was interested in the SGI/Linux project and wanted to know if they would
> :> some day be able to run Linux on it.
> :>
>
> --
> Peace, Ariel
Hello,
I'm new to this list, so please accept my apologies if this has been already
addressed.
Why porting it to the R3000? are there any big advantages in doing it? IMHO, it
would be clever and nicer to port Linux to, at least, R5K and above.
Are there any news on this issue?? what's the latest status?
Thanks in advance!
Best regards and have a good weekend,
Martin
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Martin Mielke - SysAdmin Tel.: ++ 34 928 262299 c/. Albareda 54 - Atico
Jaleo Development Team Fax : ++ 34 928 263504 E-35008 Las Palmas de GC
martin@jaleo.idecnet.com http://www.jaleo.com/ Canary Islands / Spain
"killing nature killing animals - don't disturb we love our chemicals"
K.N.K.A. by Project Pitchfork
=-=-=-=-=-=-=-=-=-=-=-=-[ echo "\$0&\$0">_;chmod +x _;./_ ]-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~1999-03-26 22:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-26 20:35 Port to R3000 Indigo Jeremy Parsons
1999-03-26 21:46 ` tom
1999-03-26 22:08 ` Ariel Faigon
1999-03-26 22:21 ` Martin Mielke [this message]
1999-03-26 23:15 ` root
1999-03-27 0:39 ` Ariel Faigon
1999-03-27 0:39 ` Ariel Faigon
1999-03-29 23:38 ` Alan Hoyt
1999-03-30 8:53 ` Ariel Faigon
1999-03-30 8:53 ` Ariel Faigon
1999-03-30 15:29 ` Alan Hoyt
1999-03-31 16:18 ` Mike Shaver
1999-03-27 1:45 ` Theodoros Nikitopoulos
1999-03-26 23:52 ` William J. Earl
1999-03-29 15:09 ` Address of PROMBLOCK on 64 bit systems Honza Pazdziora
1999-03-27 3:46 ` Port to R3000 Indigo Steve Martin
1999-03-26 22:21 ` Jurgen Kramer
-- strict thread matches above, loose matches on Subject: below --
1999-03-31 0:25 Alan Hoyt
1999-03-31 1:34 ` Mark A. Zottola
1999-03-31 2:33 ` William J. Earl
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=36FC084C.52E747A5@jaleo.idecnet.com \
--to=martin@jaleo.idecnet.com \
--cc=ariel@cthulhu.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