From cse.psu.edu!9fans-outgoing-owner Fri Mar  1 12:04:06 1996
Received: from colossus.cse.psu.edu ([130.203.1.2]) by cannon.ecf.toronto.edu with SMTP id <2214>; Fri, 1 Mar 1996 12:03:58 -0500
Received: by colossus.cse.psu.edu id <78419>; Fri, 1 Mar 1996 11:50:59 -0500
Received: from plan9.ecf.toronto.edu ([128.100.8.8]) by colossus.cse.psu.edu with SMTP id <78420>; Fri, 1 Mar 1996 11:50:41 -0500
From:	steve@plan9.ecf.toronto.edu
To:	9fans@cse.psu.edu
Date:	Fri, 1 Mar 1996 11:49:59 -0500
Subject: beta indy kernel available for testing
Message-Id: <96Mar1.115041est.78420@colossus.cse.psu.edu>
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
Status: RO

A limited (but functional) indy cpuserver kernel is now working.

The boddle is at ftp://ftp.ecf.toronto.edu/pub/plan9/steve/indy.bod
To apply the boddle, create /sys/src/9/indy, and copy all the files
from /sys/src/9/chm to it, then run the boddle and copy the new files
to /sys/src/9/indy.

This is a cpu kernel, so it does not support the Indy graphics.
It also has problems getting the ethernet address from the nvram,
so the ethernet driver (devseq.c) has been kludged to force the correct
address for my indy. You'll have to hardwire it for your system
until this is fixed. Just search for 'kludge' in devseq.c

Since this kernel is based on the 9chm kernel, they share the other
limitations listed in "The Various Ports".

My indy has an R4000SC cpu, so I'd be interested in hearing from people
with other cpus. Send comments to steve@ecf.toronto.edu please.

Thanks to forsyth, jmk, and presotto for their guidance.