From: ralf@uni-koblenz.de
To: Greg Chesson <greg@xtp.engr.sgi.com>,
Alex deVries <adevries@engsoc.carleton.ca>
Cc: Ariel Faigon <ariel@cthulhu.engr.sgi.com>,
Fredrik Rovik <fredrov@hotmail.com>,
linux@cthulhu.engr.sgi.com
Subject: Re: Status
Date: Thu, 24 Dec 1998 19:05:45 +0100 [thread overview]
Message-ID: <19981224190545.A648@uni-koblenz.de> (raw)
In-Reply-To: <9812230951.ZM5336@xtp.engr.sgi.com>; from Greg Chesson on Wed, Dec 23, 1998 at 09:51:36AM -0800
On Wed, Dec 23, 1998 at 09:51:36AM -0800, Greg Chesson wrote:
> Indy, I2, and Challenge-S are all related.
> Challenge-S is an Indy (small blue box) with the media stuff removed,
> with basically the same motherboard. I don't know for sure whether
> it has the extra SCSI channel like the I2. The I2 is a different
> motherboard in a larger (than Indy) box. Core chipsets are the same.
>
> 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.
Ralf
next prev parent reply other threads:[~1998-12-25 16:22 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 ` ralf [this message]
1998-12-28 2:32 ` Status 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=19981224190545.A648@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--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 \
/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