From: Richard Hartensveld <richardh@infopact.nl>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Alex deVries <adevries@engsoc.carleton.ca>,
Rob Lembree <lembree@sgi.com>,
linux@cthulhu.engr.sgi.com
Subject: Re: challenge s boots linux
Date: Wed, 23 Sep 1998 22:54:22 +0200 [thread overview]
Message-ID: <36095FFD.F4A33EEC@infopact.nl> (raw)
In-Reply-To: 19980923212241.01963@alpha.franken.de
Thomas Bogendoerfer wrote:
> On Tue, Sep 22, 1998 at 08:24:20PM -0400, Alex deVries wrote:
> > 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. The wd33c93 is what we already support.
> As long as the harddisk are attached to it, it should work. The wd33c95
> is a rather strange chip, and from the datasheet I have here, it looks like
> a lot of work to write a driver for it, because besides the kernel code,
> you have to write sequence code for the chip, too.
>
> > The install kernel you're using (and oh god, is it ever a bad one)
> > is broken in that serial console won't work. Yes, I should have looked
> > into it way back when.
>
> When I did the new console code, I first made the serial console working.
> As far as I remember I had to do some ugly hacks, but I'll try to clean
> it up and check it in.
>
I'm going to build the cross compiler right now and get myself involved in
linux/sgi porting, i've got
a reasonable amount of sgi's overhere to test on and maybe even get linux to boot
a kernel on a non-indy machine.
Richard
next prev parent reply other threads:[~1998-09-23 20:51 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 [this message]
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 ` challenge s boots linux Richard Masoner
1998-09-23 23:59 ` 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=36095FFD.F4A33EEC@infopact.nl \
--to=richardh@infopact.nl \
--cc=adevries@engsoc.carleton.ca \
--cc=lembree@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=tsbogend@alpha.franken.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