From: Ralf Baechle <ralf@cobaltmicro.com>
To: wje@fir.engr.sgi.com (William J. Earl)
Cc: imp@village.org, ralf@cobaltmicro.com,
linux@cthulhu.engr.sgi.com, ab@ivm.net
Subject: Re: R3000 SGI machines
Date: Fri, 26 Sep 1997 17:36:25 -0700 (PDT) [thread overview]
Message-ID: <199709270036.RAA02682@dns.cobaltmicro.com> (raw)
In-Reply-To: <199709261558.IAA10949@fir.engr.sgi.com> from "William J. Earl" at Sep 26, 97 08:58:19 am
> Warner Losh writes:
> > In message <199709260639.XAA09959@dull.cobaltmicro.com> Ralf Baechle writes:
> > : I receive an increasing number of emails asking for Linux as replacement
> > : operating system for older R3000 SGI machines as well as Mips Inc.
> > : machines. Is there still documentation available for these systems
> > : that would make a port possible?
> >
> > I'll have to search my email archive (which would take some doing),
> > but someone at SGI offered to get me the sources to RISCos, or at
> > least the device drivers. They were donated to berkeley, who didn't
> > integrate them into their 4.4 or 4.4lite release, was the story I was
> > told. Might be worth looking into. Wouldn't help with some of the
> > older SGI machines, but would help with the MIPS co boxes.
>
> The RISCos driver source was supplied with every system, and we
> did donate the source to Berkeley. Most of the VME controllers were
> common to MIPS and SGI VME systems, so most of the drivers, other than
> graphics, would be covered.
I think I can still get access to RISC/os 5.x system, maybe also old
RISC/os 4.51 tapes. What files should I try to look for?
Andy, I think you still have Resi in use, don't you? Any driver sources
included?
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@cobaltmicro.com>
To: "William J. Earl" <wje@fir.engr.sgi.com>
Cc: imp@village.org, ralf@cobaltmicro.com,
linux@cthulhu.engr.sgi.com, ab@ivm.net
Subject: Re: R3000 SGI machines
Date: Fri, 26 Sep 1997 17:36:25 -0700 (PDT) [thread overview]
Message-ID: <199709270036.RAA02682@dns.cobaltmicro.com> (raw)
Message-ID: <19970927003625.2TriX0KQB30Z9zCx231Yaw09FfswD-sZ91Qb2yeIzJA@z> (raw)
In-Reply-To: <199709261558.IAA10949@fir.engr.sgi.com> from "William J. Earl" at Sep 26, 97 08:58:19 am
> Warner Losh writes:
> > In message <199709260639.XAA09959@dull.cobaltmicro.com> Ralf Baechle writes:
> > : I receive an increasing number of emails asking for Linux as replacement
> > : operating system for older R3000 SGI machines as well as Mips Inc.
> > : machines. Is there still documentation available for these systems
> > : that would make a port possible?
> >
> > I'll have to search my email archive (which would take some doing),
> > but someone at SGI offered to get me the sources to RISCos, or at
> > least the device drivers. They were donated to berkeley, who didn't
> > integrate them into their 4.4 or 4.4lite release, was the story I was
> > told. Might be worth looking into. Wouldn't help with some of the
> > older SGI machines, but would help with the MIPS co boxes.
>
> The RISCos driver source was supplied with every system, and we
> did donate the source to Berkeley. Most of the VME controllers were
> common to MIPS and SGI VME systems, so most of the drivers, other than
> graphics, would be covered.
I think I can still get access to RISC/os 5.x system, maybe also old
RISC/os 4.51 tapes. What files should I try to look for?
Andy, I think you still have Resi in use, don't you? Any driver sources
included?
Ralf
next prev parent reply other threads:[~1997-09-27 0:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-26 6:39 R3000 SGI machines Ralf Baechle
1997-09-26 15:10 ` Warner Losh
1997-09-26 15:58 ` William J. Earl
1997-09-27 0:36 ` Ralf Baechle [this message]
1997-09-27 0:36 ` Ralf Baechle
1997-09-26 15:50 ` William J. Earl
-- strict thread matches above, loose matches on Subject: below --
1997-09-26 11:24 LetherGlov
1997-09-26 15:56 ` William J. Earl
1997-09-26 18:58 ` Steve Rikli
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=199709270036.RAA02682@dns.cobaltmicro.com \
--to=ralf@cobaltmicro.com \
--cc=ab@ivm.net \
--cc=imp@village.org \
--cc=linux@cthulhu.engr.sgi.com \
--cc=wje@fir.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