Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "William J. Earl" <wje@cthulhu.engr.sgi.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, brett <brett@madhouse.org>,
	Bruce Leggett <bleggett@sofamordanek.com>,
	linux@cthulhu.engr.sgi.com, linux-mips@fnet.fr,
	linux-mips@vger.rutgers.edu
Subject: Re: Linux on O2?
Date: Sat, 19 Feb 2000 01:03:31 +0100	[thread overview]
Message-ID: <20000219010331.B19004@uni-koblenz.de> (raw)
In-Reply-To: <14509.54953.882688.741736@liveoak.engr.sgi.com>

On Fri, Feb 18, 2000 at 03:32:57PM -0800, William J. Earl wrote:

> Ralf Baechle writes:
>  > On Thu, Feb 17, 2000 at 05:14:25PM -0800, brett wrote:
>  > 
>  > > Im still wainting to hear anything about the indigo i hear alot of talk
>  > > about the indigo2 but nothing about the original blue boxes
>  > 
>  > The problem is that the origin docs are gone by now and SGI can't
>  > just go and ship the IRIX source to hackers ...
> 
>       We might be able to help out with some Indigo R4000 information,
> if someone is seriously interested, since the Indigo R4000 is close to
> Indigo2 and Indy.  Indigo R3000 is probably hopeless (that development
> project was something like 12 years ago, after all).  The graphics is
> a tougher problem, since all but Newport and Starter (Indigo) graphics
> have geometry engines with relatively complex interfaces.  
> 
>      Ralf is quite right about the IRIX source.  Since it is based
> on source licensed from SCO, Sun, and others, we do not have the right
> to hand it out without cost to others.  

How about if myself and possibly others who currently are under NDA for SGI
would support such projects by describing things via email where
neither docs nor uncontaminated source is available and possibly some
source where it's (C)-clean and managment aproved.  Could something like
that be made working?  It's a shame that still nobody so far has had an
actual chance to start working on an O2 port or something like that.

  Ralf

  reply	other threads:[~2000-02-19  0:56 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-18  0:52 Linux on O2? Bruce Leggett
2000-02-18  1:14 ` brett
2000-02-18  1:32   ` William J. Earl
2000-02-18  1:42     ` brett
2000-02-18  2:53   ` Ralf Baechle
2000-02-18 22:13     ` brett
2000-02-18 23:32     ` William J. Earl
2000-02-19  0:03       ` Ralf Baechle [this message]
2000-02-19  3:42         ` William J. Earl
2000-02-19 12:29         ` Harald Koerfgen
2000-02-19 21:00           ` Brian D. Moffet
2000-02-19  8:30     ` Marc Esipovich
2000-02-19 23:14       ` Ralf Baechle
2000-02-20 19:11         ` Geert Uytterhoeven
2000-02-20 21:05           ` Ralf Baechle
2000-02-20 21:05             ` Ralf Baechle
2000-02-20 22:32             ` Richard
2000-02-20 23:03               ` Ralf Baechle
2000-02-21 19:44                 ` Richard
  -- strict thread matches above, loose matches on Subject: below --
2000-02-20  0:29 Bill Halchin
2000-02-20  1:01 ` Ralf Baechle
2000-02-29  3:05 Bastiaan.N.Veelo
2000-02-29  3:39 ` James Simmons
2000-03-01  1:56 ` Ralf Baechle
2000-02-29 18:39 jallan
2000-02-29 18:39 ` jallan
2000-03-01  8:11 ` Richard
2000-03-01 14:40   ` James A Simmons

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=20000219010331.B19004@uni-koblenz.de \
    --to=ralf@oss.sgi.com \
    --cc=bleggett@sofamordanek.com \
    --cc=brett@madhouse.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@vger.rutgers.edu \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=wje@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