re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread matthew green
> > on sgimips? (or cobalt? :) > > evbmips this is what my sgimips64 kernel prints before hanging, stairsteps included.. (this doesn't happen with 32 bit kernel IIRC.) > boot -f bootp():rsdio/netbsd Setting $netaddr to 172.16.24.186 (from server space-24) Obtaining rsdio/netbsd from server sp

Re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread Matt Thomas
On Jun 1, 2014, at 9:45 PM, matthew green wrote: > > Matt Thomas writes: >> >> On Jun 1, 2014, at 1:29 PM, matthew green 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

re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread matthew green
Matt Thomas writes: > > On Jun 1, 2014, at 1:29 PM, matthew green 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 > > app

Re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread Matt Thomas
On Jun 1, 2014, at 1:29 PM, matthew green 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 loo

Re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread Michael
Hello, On Mon, 02 Jun 2014 06:29:44 +1000 matthew green wrote: > hmmm, isn't n32 kernel a relatively uncommon way of setting up the > new mips code? Yes. > 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

re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread matthew green
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 n6

Re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread Michael
On Sun, 1 Jun 2014 15:51:58 +0200 Martin Husemann wrote: > On Sun, Jun 01, 2014 at 09:45:55AM -0400, Michael wrote: > > Not sure, they ( o32 binaries of 5.99.19 vintage, last working userland > > I have before MIPS got borked ) crashed immediately even with > > COMPAT_NETBSD32 so for now at least

Re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread Martin Husemann
On Sun, Jun 01, 2014 at 09:45:55AM -0400, Michael wrote: > Not sure, they ( o32 binaries of 5.99.19 vintage, last working userland > I have before MIPS got borked ) crashed immediately even with > COMPAT_NETBSD32 so for now at least it doesn't seem to be a loss. The > problem this is supposed to wo

Re: CVS commit: src/sys/arch/sgimips/conf

2014-06-01 Thread Michael
Hello, On Sun, 01 Jun 2014 05:24:41 +1000 matthew green wrote: > "Michael Lorenz" writes: > > Module Name:src > > Committed By: macallan > > Date: Sat May 31 16:16:52 UTC 2014 > > > > Modified Files: > > src/sys/arch/sgimips/conf: std.sgimips64_32 > > > > Log Me

re: CVS commit: src/sys/arch/sgimips/conf

2014-05-31 Thread matthew green
"Michael Lorenz" writes: > Module Name: src > Committed By: macallan > Date: Sat May 31 16:16:52 UTC 2014 > > Modified Files: > src/sys/arch/sgimips/conf: std.sgimips64_32 > > Log Message: > we don't need or want COMPAT_NETBSD32 in a 32bit kernel > should cure pkgsrc MACHINE_ARCH