From: "William J. Earl" <wje@fir.engr.sgi.com>
To: ralf@uni-koblenz.de
Cc: Greg Chesson <greg@xtp.engr.sgi.com>,
Alex deVries <adevries@engsoc.carleton.ca>,
Ariel Faigon <ariel@cthulhu.engr.sgi.com>,
Fredrik Rovik <fredrov@hotmail.com>,
linux@cthulhu.engr.sgi.com
Subject: Re: Status
Date: Sun, 27 Dec 1998 18:32:31 -0800 [thread overview]
Message-ID: <199812280232.SAA18705@fir.engr.sgi.com> (raw)
In-Reply-To: <19981224190545.A648@uni-koblenz.de>
ralf@uni-koblenz.de writes:
...
> > What we need to do is make it easy for Linux to determine what
> > chipsets are attached to the cpu. Bill Earl might have some straightforward
> > answers. I'm in favor of simply publishing the relevant sections
> > of Irix bootstrap code. Perhaps Santa Claus can make a code drop this year.
>
> Isn't that ``Full House'' vs. ``Guiness''? Linux knows that difference since
> it is running on the Indy.
The basic difference is between "FullHouse" (Indigo2) and "Guinness"
(Indy). Beyond that, there are smaller differences between Indy and Challenge S.
Challenge S does have an extra SCSI channel, but the configuration is not
identical to Indigo2. (I will look into that later.)
I am still working on an agreement to release more technical information
about a variety of our systems.
prev parent reply other threads:[~1998-12-28 2:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-21 16:45 Status Fredrik Rovik
1998-12-21 20:06 ` Status Ariel Faigon
1998-12-21 20:06 ` Status Ariel Faigon
1998-12-21 20:36 ` Status Honza Pazdziora
1998-12-21 20:58 ` Status Mark A. Zottola
1998-12-21 21:22 ` Status Alex deVries
1998-12-21 22:16 ` Status Greg Chesson
1998-12-23 3:50 ` Status Alex deVries
1998-12-23 5:44 ` Status Dave Olson
1998-12-23 5:44 ` Status Dave Olson
1998-12-23 17:51 ` Status Greg Chesson
1998-12-24 18:05 ` Status ralf
1998-12-28 2:32 ` William J. Earl [this message]
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=199812280232.SAA18705@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=fredrov@hotmail.com \
--cc=greg@xtp.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
/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