From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Mike Shaver <shaver@netscape.com>
Cc: "linux@cthulhu.engr.sgi.com" <linux@cthulhu.engr.sgi.com>
Subject: Re: indigo2 extreme
Date: Mon, 18 Jan 1999 21:53:29 -0800 [thread overview]
Message-ID: <199901190553.VAA08758@fir.engr.sgi.com> (raw)
In-Reply-To: <36A4120E.2FF847E0@netscape.com>
Mike Shaver writes:
> So I've got a decent deal on an indigo2[*] with the extreme kit lined
> up, and I'm wondering how much I'll regret it if I go ahead and purchase
> it. Will I live to see it run Linux? Will I be able to use the x86
> EISA code to get started?
...
As has been discussed here a number of times, the Indigo2 is
not too different from an Indy. The Extreme graphics, however, are
a challenge to support with open source software, and I do not yet
have authorization to release the hardware specifications for the
EISA interface either (although I keeping working on being able
to release all the hardware specifications).
next prev parent reply other threads:[~1999-01-19 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-19 5:03 indigo2 extreme Mike Shaver
1999-01-19 5:53 ` William J. Earl [this message]
1999-01-19 10:13 ` ralf
1999-01-19 16:52 ` Dave Olson
1999-01-21 21:15 ` indigo2 Andrew R. Baker
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=199901190553.VAA08758@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=shaver@netscape.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