From: "William J. Earl" <wje@fir.engr.sgi.com>
To: darkaeon@cubicsky.com
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Indigo2 & Linux
Date: Thu, 11 Mar 1999 13:29:15 -0800 [thread overview]
Message-ID: <199903112129.NAA22834@fir.engr.sgi.com> (raw)
In-Reply-To: <36E85AC2.25F7C9B0@kotetsu.cubicsky.com>
Steve Martin writes:
> I'm curious as to what the current progress is with Linux and the
> Indigo2(R4400SC 150Mhz Elan)
> Also, I remember hearing something about running Xsgi on Linux, has that
> been successfully(not stable, just enough to see it start up, maybe not
> usable) done yet?
One recent change is that I and other SGI engineers now have
authorization to release interface details of the system and graphics
hardware for Indigo2, as we have previously had authorization for
Indy. Unfortunately, I have not yet had time to locate the additional
documentation (where Indigo2 differs from Indy). Also, the policy
for source code disclosure is still not settled, and being able
to release selected bits of low-level IRIX code would make the whole
effort much simpler. (Everyone is agreed in principle that SGI should
release some such source code to interested Linux developers, but we
need a formal policy to authorize people to, in effect, give away
SGI intellectual property. Admittedly, the value of the relevant
code is small, but individual employees are not ordinarily authorized
to make such contributions, although that is obviously changing in
respect to Linux-based work.)
next prev parent reply other threads:[~1999-03-11 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-12 0:07 Indigo2 & Linux Steve Martin
1999-03-11 21:29 ` William J. Earl [this message]
1999-03-11 22:24 ` Ariel Faigon
1999-03-12 10:17 ` Honza Pazdziora
1999-03-12 18:14 ` Miguel de Icaza
1999-03-13 2:35 ` Thomas Bogendoerfer
1999-03-12 15:59 ` Andrew R. Baker
1999-03-14 23:09 ` Richard Hartensveld
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=199903112129.NAA22834@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=darkaeon@cubicsky.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.