1) how can we tell if procnto-600 is running at all? 
It would be nice to have a form that allows the poor BSP developer to set a minimum number of things up 
in syspage that indicates that *something* is going on. 
At a minimum is a pointer to a function to display a single char to provide a kprintf() functionality. 
I am not even sure if it gets to the point of assuming the dispatcher is working. [topc3638]

2) does proctno-600 mess at all with BAT 4..7? we need them for the hardware addresses, but there is code 
in the BSP that disables the BAT 4..7 (I commented it out) 

3) what does procnto-600 do with the MMU? 
for example, the various utlities are in the address range of 0x40000000 
I assume procnto-600 deals with the MMU in this case and the BAT 0..3 is enough. 

5) the 'patch' parts of the callouts is pretty obscure. 
I looked thru the docs, but didn't find anything that details this. 
Of course, I can be blind. There is some handwaving, but the most
concrete descriptions are for the ID and EOI callouts.
What it looks like is it modifies the code to set the base address of a device (in device driver cases).

6) There is a great lack of comments in the BSP startup code. 
I am rather sad about that. 

7) not clear if procnto-600 does anything with the watchdog. 
I am not sure if it is active - we are using uboot to setup the hardware. 
I am pretty sure it is not active (which is my issue), but how does procnto-600 
stroke the dog to keep it awake? I assume a callout. 
The other choice, the logical one, is some sort of health task that strokes the watchdog. (Just looking for reality 
check.)