From: richardm@bif.cd.com (Richard Masoner)
To: linux@cthulhu.engr.sgi.com
Subject: Re: challenge s boots linux
Date: Wed, 23 Sep 1998 16:30:21 -0500 (CDT) [thread overview]
Message-ID: <199809232130.QAA28013@bif.cd.com> (raw)
In-Reply-To: <19980923212241.01963@alpha.franken.de> from "Thomas Bogendoerfer" at Sep 23, 98 09:22:41 pm
> > First, I wonder how much of the kernel will actually work on the
> > Challenge S; I'm told there are SCSI controller differences.
>
> looking linus.linux.sgi.com, which is AFAIK a Challenge S, it seems the
> Challenge has a wd33c93 and a wd33c95.
Correct. Challenge S has the same wd33c93 SCSI chip on it that the
Indy has. Additionally, it has the wd33c95 chip for more SCSI buses
in place of of video and audio that's on the Indy.
--
Richard F. Masoner Digi International
richardm@cd.com 1602 Newton Drive
http://www.cd.com/ Champaign, IL 61822 USA
next prev parent reply other threads:[~1998-09-23 21:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-22 21:11 challenge s boots linux Richard Hartensveld
1998-09-22 21:01 ` Rob Lembree
1998-09-22 21:41 ` Richard Hartensveld
1998-09-23 0:24 ` Alex deVries
1998-09-23 19:22 ` Thomas Bogendoerfer
1998-09-23 20:54 ` Richard Hartensveld
1998-09-23 21:11 ` Alex deVries
1998-09-24 4:47 ` Jeremy John Welling
1998-09-24 9:38 ` Richard Hartensveld
1998-09-24 14:15 ` Alan Cox
1998-09-24 14:15 ` Alan Cox
1998-09-24 16:33 ` Alex deVries
1998-09-24 16:44 ` William J. Earl
1998-09-24 22:42 ` Richard Hartensveld
1998-09-25 5:45 ` Cool Jeremy John Welling
1998-09-23 21:30 ` Richard Masoner [this message]
1998-09-23 23:59 ` challenge s boots linux ralf
1998-09-24 0:17 ` Richard Hartensveld
1998-09-24 0:21 ` ralf
1998-09-24 9:29 ` Thomas Bogendoerfer
1998-09-24 16:14 ` Alex deVries
1998-09-24 5:44 ` Robin Humble
1998-09-24 5:44 ` Robin Humble
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=199809232130.QAA28013@bif.cd.com \
--to=richardm@bif.cd.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=richardm@cd.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