> bfs: boot server/Sonic ethernet
>
> So, Instead of doing "setenv bootfile bootp()netbsd "
> I do a "setenv bootfile bfs()netbsd"
>
> However, a tcpdump gives me the following.
>
> 09:31:50.944379 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
> 09:31:53.179810 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
> 09:31:56.179930 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
> 09:31:59.180050 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
> 09:32:02.180170 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
> 09:32:05.180290 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
> 09:32:08.180410 192.168.1.22.2200 > 192.168.1.0.2201: udp 39
>
> And of course the boot fails.
>
> I assume this is not a normal bootp request, is that correct?

It's MIPSco's proprietary UDP downloading to boot kernel.  I remember
that RISCos once contained an _entire_ set of ROM monitor source code
and development support program like bfsd.  I heard that 4.51 or 4.52
does not them anymore.

Either of R3000 Magnum and R4000 Magnum hardware is designed Endian
neutral.  Chip registers are aligned 4byte or 8byte and as long as
each register is accessed thru lw/sw or ld/sd there is no Endian
issue.

Tohru Nishimura