Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alan Hoyt <neuroinc@unidial.com>
To: Ariel Faigon <ariel@cthulhu.engr.sgi.com>,
	"linux@engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: Port to R3000 Indigo
Date: Mon, 29 Mar 1999 23:38:10 +0000	[thread overview]
Message-ID: <37000EE1.6C336FD0@unidial.com> (raw)
In-Reply-To: 199903270039.QAA24143@oz.engr.sgi.com

Ariel Faigon wrote:


> Regarding MIPS, for similar reasons, having the Indy port 'finished'
> (it is not yet really easy to get up and running) or having support
> for O2s, seems (at least to me) to be much more attractive than
> R3000 Indigos.
>
> Again, It is not that I don't want it to happen.  I'm just
> asking myself, what would I (and many others) prefer to put
> available talent energies on.   If we don't set priorities,
> we run the risk of getting lost in multiple unfinished ports
> and dilute our efforts and end results.
>
> ... <section omitted for brevity> ...
>
> I believe Bill Earl tried to locate some very old specs but
> couldn't find them (and he can correct me if I'm wrong).  Indy
> specs were sent (sorry I only have paper versions) to those
> who have shown they are really serious and can make a difference
> and asked for them.  The best source for older SGI machines
> data is at:
>
>         http://www.geocities.com/SiliconValley/Pines/2258/4dfaq.html
>
> This is the best I could find on anything before my times at SGI...
>
> --
> Peace, Ariel

Two questions:

Does this mean that you are going to be posting the hardware specifications
for the Indigo 2, O2, etc.. (i.e. SGI's more recent systems) on your web
server for public access, or will this information be disseminated through
controlled channels?

Also,  if you are going to post the specs - when will they be available?

Just curious, since HP publicly released some detailed hardware specs for
their systems in PDF format to assist their Linux porting project - it's very
nice.

Thanks

 - Alan Hoyt -

  parent reply	other threads:[~1999-03-30  0:03 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
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 [this message]
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=37000EE1.6C336FD0@unidial.com \
    --to=neuroinc@unidial.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