Re: mips64eb seems to be mostly 32-bit

Denis Ovsienko <[email protected]>
Newsgroups gmane.os.netbsd.ports.mips.devel
Message-ID <20210707214843.6059230c@basepc>
On Wed, 07 Jul 2021 18:44:13 +1000
Simon Burge <[email protected]> wrote:

> The problem here is that "fatload usb 0 $(loadaddr) netbsd" doesn't
> leave any info at all on how or where that kernel was loaded from
> (that I'm aware of, certainly not in a uboot variable).
> 
> If you look at how Linux boots on an ER-4 (I don't have a USB in my
> Erlite at the moment), you'll see
> 
> 	bootoctlinux ... root=/dev/mmcblk0p2
> 
> We need to do something similar for NetBSD.  For the DD images that
> have root on dk1 and a wedge called "octeon-root", either of the
> following work
> 
> 	fatload usb 0 $(loadaddr) netbsd
> 	bootoctlinux $(loadaddr) root=dk1
> 
> or
> 
> 	fatload usb 0 $(loadaddr) netbsd
> 	bootoctlinux $(loadaddr) root=wedge:octeon-root
> 
> Both of these will boot like this:

Thank you Simon.

I tried searching for a way to specify NetBSD root block device
explicitly, but for some reason could not find this. I have tested the
suggestions above using octeon.img.gz 202107071010Z (both mips64eb and
mipsn64eb) and confirm they indeed work as described.

-- 
    Denis Ovsienko
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.