building vxWorks for nitro-260

[wbrown@csg.lbl.gov (Bill Brown)]

We're trying to get to the point where we can use a couple of Heurikon
"Nitro-260" as iocs' in one of our systems that's heavily loaded.  It's
currently using 'mv167-s which are a bit too busy for comfort.

In order to do so, we need to configure the system with a lot of features
(like NFS, etc) turned on, which is not the way the kernel was configured
from Heurikon.

We got a copy of the 5.2 BSP from heurikon, and integrated it with the
BSPs that we already had.  After a little fooling around, we got the BSP
to compile with no complaint.

When we try to boot the newly-built BSP, the boot-loader crashes.  It _looks_
like perhaps part of the boot-loader is getting over-written by the down-
loaded kernel.  We're using the original EPROMS (5.1.1) which worked ok with
the original supplied kernel, but it seems like that ought to be ok.  It
seems like it's been a long time since there was a fatal conflict between a
new kernel and a previous boot-prom set.

Does anyone have any ideas about what I'm overlooking?  It's probably just
a "one-liner" in config.whosis, but I can't seem to figure it out.  I sent
email to Heurikon yesterday, but so far there has been no reply.  The target-
specific reference and the vxw 5.2 doc's haven't enlightened me; I've at
least tried to "RTFM!"  And a Fine Manual it is, too!

Any hints, pointers, (constructive) flames, etc. will be appreciated.

-bill