> Hi there,
> 
> I've been using gcc under NetBSD on my shark to boot my own 
> bootloader/scheduler for research purposes. I understand that the firmware 
> expects an aout format binary. I got tired of rebooting into NetBSD all the 
> time, so decided to build arm-aout gcc (et al) on my Linux workstation. 
> Anyway, the sharks seem to not want to digest this new image - on netboot it 
> starts the spinning cursor, and then just stops:
> 
> Send a line break to stop the booting process.
> Boot device: /isa/ethernet  Arguments: 
> -
> 
> The same code compiles and links with the same options under NetBSD, and works 
> fine. Is there some magic in the NetBSD/gcc setup that I need to be aware of?
> 
> Sorry for the off topicness of this posting. If enough people care, I'm 
> willing to setup a Shark specific mailing list and host it.

It's probably your assembler linker that are causing the problems.  NetBSD 
uses a specific magic number and the firmware may be expecting that.

R.