On Jun 1, 2014, at 9:45 PM, matthew green <m...@eterna.com.au> wrote:
> > Matt Thomas writes: >> >> On Jun 1, 2014, at 1:29 PM, matthew green <m...@eterna.com.au> wrote: >> >>> >>> hmmm, isn't n32 kernel a relatively uncommon way of setting up the >>> new mips code? i'm not sure matt ever tested that properly, but >>> it seems to me it should be capable of running o32, n32 and n64 >>> applications, but matt should have a look at this.. >>> >>> (i'm pretty sure the designed method is to run n64 kernels and >>> to have n32 userland default, with both o32 and n64 userland >>> compat available.) >> >> N32 or N64 kernels are fine. I've used both. > > on sgimips? (or cobalt? :) evbmips > what userland in both cases? n32 and o32.
