On Mon, May 07, 2018 at 04:46:41AM +0000, m...@netbsd.org wrote: > Attach console cable and ethernet cable. > On host, configure it to a known IP, e.g. I use > ifconfig re0 192.168.0.1 > enable tftp via uncommenting the /etc/inetd.conf entry and restarting > inetd. > in /tftpboot, place ERLITE INSTALL kernel. > e.g. /tftpboot/erlite-install > > cu -s 115200 -l /dev/ttyU0 > > On u-boot console (not in linux): > set serverip 192.168.0.1 > set ipaddr 192.168.0.5 > tftp $loadaddr erlite-install > bootoctlinux > > netbsd should boot fine. ignore the installer. > In the msdos filesystem, replace vmlinux.64 with a netbsd ERLITE kernel > (not INSTALL). > replace the ext4 filesystem with a better root filesysttem for > netbsd,like FFSv2. > > Configure networking to fetch the sets from the host. Use mips64eb sets. > ifconfig cnmac0 192.168.0.5 > route add default 192.168.0.1 > > scp myhostusername@192.168.0.1:/path/to/sets/*.tgz . > cd / cd /targetroot > for i in *.tgz; do tar xzpf $i; done cd /targetroot/dev sh MAKEDEV all echo "rc_configured=YES" >> /targetroot/etc/rc.conf Adjust /etc/fstab
> > Reboot. > > It works, but some things are not supported as good as e.g. amd64.
