> I have finished (well, except for some cleanup) splitting the CS8900
> driver and making it machine-independent.  There is now a proper isa
> and ofisa front-end in machine-independent code.  It is confirmed to
> work on the Shark, and compiles on the i386.

> cs0 at ofisa0 (ethernet@i300): CRUS,CS8900 cs0: CS8900 rev. F, address
> 08:00:2b:81:63:01, media UTP

> Also, I have added ifmedia support, so it may actually be possible to
> enable 10Mb/full-duplex on the Shark now :-)

...
> If you encounter problems, or have questions, please let me know.

Well, I've finally managed to lay my hands on a Shark, but while I can 
boot the snapshot kernel on ftp.netbsd.org, kernels built from -current 
are failing completely.   After some probing, I discovered that the new 
code is failing to find the CS8900 chip, and while adding an entry to 
compatible_strings in dev/ofisa/if_cs_ofisa.c of the form "CS8900" allows 
the probe to find the chip, the attach is still failing because it can't 
find the media information.

Do I have a weird Open Firmware build, or are other people seeing this?

The banner when I start the Shark is:

DNARD Rev. 5, 8:0:2b:81:67:10 , 32 MB memory
Open Firmware, Built August 28, 1997 14:47:54
etc.


Is there any way to access the properties from the ROM monitor program?  I 
can't find much documentation on the monitor, but it seems to have far 
more than the help suggests.

Richard.