From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: ratfink@xtra.co.nz (Brendan Black)
Cc: linux@cthulhu.engr.sgi.com (SGI/Linux mailing list)
Subject: Re: Linux/SGI
Date: Wed, 3 Sep 1997 19:53:47 -0700 (PDT) [thread overview]
Message-ID: <199709040253.TAA24709@oz.engr.sgi.com> (raw)
In-Reply-To: <340DF260.5D60941F@xtra.co.nz> from "Brendan Black" at Sep 4, 97 11:27:28 am
:
:Hi
:
:we don't have a spare Indy to play with, but have a
:spare Challenge S (single processor R5000)
:
:I was wondering if you thing this machine is possible, it would be
:used with a serial console (no X), for testing ;)
:--
If you feel up to the challenge, sure, please go ahead.
There may be a few assumptions in the current code which detects
the newport graphics console that this testing may uncover. If
you can fix this so it won't be Indy dependent, we win one more
possible platform !
Moreover, since a challenge-S doesn't have graphics anyway
Linux which is fast and compact may even outperform IRIX
on some benchmarks.
I would suggest that:
1) You join the mailing list:
To: majordomo@engr.sgi.com
Body: subscribe linux your@preferred.email.address
if you have questions, ask...
2) If you have Challenge-S patches, e-mail them to the list
and we can check that they didn't break anything and
merge them into the source tree.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: Brendan Black <ratfink@xtra.co.nz>
Cc: SGI/Linux mailing list <linux@cthulhu.engr.sgi.com>
Subject: Re: Linux/SGI
Date: Wed, 3 Sep 1997 19:53:47 -0700 (PDT) [thread overview]
Message-ID: <199709040253.TAA24709@oz.engr.sgi.com> (raw)
Message-ID: <19970904025347.B82GEG2aF9ULHKX82ysEP8qtGO1fdMJfASrl6dc_2wE@z> (raw)
In-Reply-To: <340DF260.5D60941F@xtra.co.nz> from "Brendan Black" at Sep 4, 97 11:27:28 am
:
:Hi
:
:we don't have a spare Indy to play with, but have a
:spare Challenge S (single processor R5000)
:
:I was wondering if you thing this machine is possible, it would be
:used with a serial console (no X), for testing ;)
:--
If you feel up to the challenge, sure, please go ahead.
There may be a few assumptions in the current code which detects
the newport graphics console that this testing may uncover. If
you can fix this so it won't be Indy dependent, we win one more
possible platform !
Moreover, since a challenge-S doesn't have graphics anyway
Linux which is fast and compact may even outperform IRIX
on some benchmarks.
I would suggest that:
1) You join the mailing list:
To: majordomo@engr.sgi.com
Body: subscribe linux your@preferred.email.address
if you have questions, ask...
2) If you have Challenge-S patches, e-mail them to the list
and we can check that they didn't break anything and
merge them into the source tree.
--
Peace, Ariel
next parent reply other threads:[~1997-09-04 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <340DF260.5D60941F@xtra.co.nz>
1997-09-04 2:53 ` Ariel Faigon [this message]
1997-09-04 2:53 ` Linux/SGI Ariel Faigon
1997-03-07 19:51 Linux/SGI Miguel de Icaza
1997-03-07 21:38 ` Linux/SGI Ralf Baechle
1997-03-07 21:38 ` Linux/SGI 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=199709040253.TAA24709@oz.engr.sgi.com \
--to=ariel@oz.engr.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ratfink@xtra.co.nz \
/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