Re: Starting NetBSD/mips64 kernel up and Userland Questions

Michael <[email protected]>
Newsgroups gmane.os.netbsd.ports.mips.devel
Organization The NetBSD Foundation
Message-ID <20200101133223.2deb8d61@blackbush>
Hello,

On Thu, 2 Jan 2020 02:19:57 +0900
"Naruaki.Etomi" <[email protected]> wrote:

> I succeeded in starting NetBSD/mips64(GENERIC64_IP3x) up on Sgi O2.
> https://dmesgd.nycbug.org/index.cgi?do=view&id=5275
> 
> Here is the patch.
> https://github.com/nullnilaki/NetBSD-mips64/commits/master

Nice! Now I really need to get a new power supply for my O2...

> I have a question about NetBSD/mips64 userland.
> 
> I did the following.
> # ./build.sh -j 16 -O ../obj.sgimips64 -T  ../tools.sgimips64 -m
> sgimips64 -U sets
> However, it was a 32 bit userland binary.
> # file cat
> cat: ELF 32-bit MSB shared object, MIPS, N32 MIPS-III version 1
> (SYSV), dynamically linked, interpreter /libexec/ld.elf_so, missing
> section headers

We default to N32 userlands on all mips64 - as in 64bit registers etc.
enabled but 32bit address space.

> How can I make a 64 bit userland binary?

Not sure they work properly, but gcc -mabi=64 ... is probably what
you're looking for.

> # file ip32boot
> ip32boot: ELF 64-bit MSB executable, MIPS, MIPS-III (SYSV), statically
> linked, with unknown capability 0x410000000f676e75 = 0x1000000070403,
> for NetBSD 9.99.31, not stripped
> 
> > bootp()ip32boot  
...
> [  11.0455541] boot device: mec0
> [  11.0811551] root on mec0

I've been running n32 kernels on mine, LP64 ones always ended up
panicing on copyout() when entering userland. Good to see you got that
fixed :)

> By the way, porting sgi octane is working.
> *Fix early initialize Hardware.
> *Fix paging kernel.
> *Lot of driver Required...(Xbow,xheart,ioc,etc...)

Please commit, even if it only partially works, so other people can
work on it as well ( mostly referring to myself, I have an Octane
here... )

have fun
Michael
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.