Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: sr@dragon.engr.sgi.com (Steve Rikli)
To: linux@cthulhu.engr.sgi.com
Subject: Re: R3000 SGI machines
Date: Fri, 26 Sep 1997 11:58:50 -0700 (PDT)	[thread overview]
Message-ID: <199709261858.LAA67409@dragon.engr.sgi.com> (raw)
In-Reply-To: <199709261556.IAA10936@fir.engr.sgi.com> from "William J. Earl" at Sep 26, 97 08:56:09 am

William J. Earl wrote:
> LetherGlov@aol.com writes:
>>
>> You know I was just thinking about that this morning. I was more leaning
>> towards the personal iris, and the crimson with the video adapter that is not
>> supported in 6.2(the name isn't coming to me right now, GTX?). I was
>> wondering how we got the specs from the ethernet, bus, and serial controllers
>> from SGI. And the chip specs from mips. If I understand SGI history
>> correctly, there was a change in the CPU after revision 3, and we are going
>> to need to see if this is going to cause problems. another thing we need to
>> do(I'll do it) is call ID Software and get the code for DOOM so It can be
>> compiled for Linux.
> 
>      The MIPS processor specifications are public, and available as printed
> books.  Also, many of them are online at http://www.sgi.com/MIPS/.  
> 
>      With the approval of the appropriate division general manager, I 
> supplied the people doing the Indy port of linux with copies of the
> Indy hardware documentation.
> 
>      Since the Personal IRIX and Crimson use mostly VME controllers. those
> drivers should carry over from other VME ports.  I don't know if I can
> arrange to provide documentation for the graphics controllers.

This may not be exactly the kind of thing some of y'all are looking
for, but since we're talking about doc & info sources for old SGI
hardware I felt I should point this one out:

	http://www.geocities.com/SiliconValley/Pines/2258/4dfaq.html

Several handfulls of general notes about the 4D and/or other R3K 
platforms.

Hope someone finds it useful.

cheers,
sr.
-- 
|| Steve Rikli <sr@sgi.com> ||| Any sufficiently advanced technology is ||
|| Systems Administrator    ||| indistinguishable from a rigged demo.   ||
|| NSD, EIS Infrastructure  |||                                         ||
|| Silicon Graphics, Inc.   |||               - Andy Finkel             ||

  reply	other threads:[~1997-09-26 18:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-09-26 11:24 R3000 SGI machines LetherGlov
1997-09-26 15:56 ` William J. Earl
1997-09-26 18:58   ` Steve Rikli [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-09-26  6:39 Ralf Baechle
1997-09-26 15:10 ` Warner Losh
1997-09-26 15:58   ` William J. Earl
1997-09-27  0:36     ` Ralf Baechle
1997-09-27  0:36       ` Ralf Baechle
1997-09-26 15:50 ` 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=199709261858.LAA67409@dragon.engr.sgi.com \
    --to=sr@dragon.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