So, I grabbed the `si' driver from the Sun 3 port and frobbed with it a 
little and have it `almost working' on my 4/260.  It autoconf's sd0 
(which is a Micropolis ESDI drive behind an Emulex SCSI adaptron) and st0 
(sort of -- it's one of those QIC-36 behind an Emulex frob that return 
empty ID strings, requiring a really braindead entry in scsiconf.c).  
However, I also have an sd1, a Maxtor, which (and I haven't actually 
pulled the beast apart yet to check) is probably at lun1 of this Emulex 
controller.  However, it doesn't seem to autoconf that disk.  I'm going 
to try `hardwiring' sd1 in the config file next, but was wondering if any 
of you had some ideas about this...

Also, there seems to be a weensy problem of `boot device not known'.  
Exactly how is bootdv supposed to be initialized on the 4/260?  If I pass 
in `-a', it does indeed ask me for a boot device, and that's fine, but it 
deref's a NULL pointer to print out the default name, which, luckily only 
resulted in garbage all over my screen this time.

In any case, I was able to boot into single-user off the disk, albeit 
with all SunOS binaries (since the only NetBSD stuff on this box at the 
moment is the kernel :-) and fsck the disk, run a program or two, etc.

I'll post si.c and related files in a bit...

--------------------------------------------------------------------------
Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffet Field, CA 94035                                 Pager: 415.428.6939