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: Tue, 30 Mar 1999 15:29:04 +0000	[thread overview]
Message-ID: <3700EDC0.29E677A4@unidial.com> (raw)
In-Reply-To: 199903300853.AAA52093@oz.engr.sgi.com

Ariel Faigon wrote:

> I believe this was referred to by Bill Earl in an earlier post.
> Clearly, this needs further explanation.
>
> Since the interfaces with SGI proprietary hardware were never meant
> to be public, the only documentation you can really rely on to be
> accurate and reliable is the (working) IRIX source code.  We would really
> like to avoid publishing material that's incomplete, outdated, and
> turns out to be more confusing than it is worth.
>
> Now, if it were entirely in my hands, I would have gladly published
> some source code.  The problem is much more complex than that.  The
> IRIX source code includes licensed code from many external commercial
> sources, AT&T SVR4, Sun, Xerox, etc. each surrounded by its own complex
> licensing terms, so the lawyers need to look into this lest SGI
> becomes liable by just making some "innocent goodwill" happen.
>
> I know it sounds lame, and I as much as anyone, hate this, but
> this is reality, and it isn't simple as it may appear to some.
> It requires a lot of legal (inspection and clearance) + engineering
> (sanitize and clean up code) time which I'm not sure we can afford
> on a global scale.
>
> The good news is that SGI is clearly putting much more emphasis
> these days on developing hardware that is much more standard
> and opening more and more source code (after legal has looked into
> it and approved it).  Everything we have been doing in the past
> year on the Linux front makes this clear that this is where we're
> going.  I would like to request a bit of patience and support...
> You are preaching to the choir here.
>
> --
> Peace, Ariel

One last question:

I have an old Indigo and Indigo 2 - I am very interested and very serious about
porting Linux to one of these systems.  However, without detailed hardware specs.
a very difficult job becomes much much harder.  Can you throw a dog a bone?  Are
there any hardware specs. (NOT source code) that you are willing and/or capable
of providing at this time to get the ball rolling- without further delays
perpetrated by your legal department?

Thanks

 - Alan Hoyt -

  parent reply	other threads:[~1999-03-30 15:53 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
1999-03-30  8:53           ` Ariel Faigon
1999-03-30  8:53             ` Ariel Faigon
1999-03-30 15:29             ` Alan Hoyt [this message]
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=3700EDC0.29E677A4@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