| To: | Thomas Bogendoerfer <tsbogend@alpha.franken.de>, Alex deVries <adevries@engsoc.carleton.ca> |
|---|---|
| Subject: | Re: challenge s boots linux |
| From: | ralf@uni-koblenz.de |
| Date: | Thu, 24 Sep 1998 01:59:38 +0200 |
| Cc: | Richard Hartensveld <richardh@infopact.nl>, Rob Lembree <lembree@sgi.com>, linux@cthulhu.engr.sgi.com |
| In-reply-to: | <19980923212241.01963@alpha.franken.de>; from Thomas Bogendoerfer on Wed, Sep 23, 1998 at 09:22:41PM +0200 |
| References: | <36081982.8D3B6975@infopact.nl> <Pine.LNX.3.96.980922201845.10292B-100000@lager.engsoc.carleton.ca> <19980923212241.01963@alpha.franken.de> |
| Sender: | owner-linux@cthulhu.engr.sgi.com |
On Wed, Sep 23, 1998 at 09:22:41PM +0200, 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. Did I missunderstand the 95's documentation - I thought we can abuse the 95 as a 93, thereby saving alot of driver work for now? Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | VINO, Thomas Bogendoerfer |
|---|---|
| Next by Date: | Re: challenge s boots linux, Richard Hartensveld |
| Previous by Thread: | Re: challenge s boots linux, Richard Masoner |
| Next by Thread: | Re: challenge s boots linux, Richard Hartensveld |
| Indexes: | [Date] [Thread] [Top] [All Lists] |