Date: Wed, 05 Jan 2011 14:23:11 -0700 From: Warner Losh <imp@bsdimp.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Juli Mallett <jmallett@FreeBSD.org>, svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r216969 - head/sys/mips/conf Message-ID: <4D24E13F.3040807@bsdimp.com> In-Reply-To: <20110105185309.N14966@maildrop.int.zabbadoz.net> References: <201101041909.p04J95i8051538@svn.freebsd.org> <20110105185309.N14966@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/05/2011 11:54, Bjoern A. Zeeb wrote: > On Tue, 4 Jan 2011, Juli Mallett wrote: > >> Author: jmallett >> Date: Tue Jan 4 19:09:05 2011 >> New Revision: 216969 >> URL: http://svn.freebsd.org/changeset/base/216969 >> >> Log: >> Remove OCTEON1-32. Since moving to the Cavium SDK, we've lost our >> support for >> running an o32 kernel safely, and would have to add interrupt >> disabling and >> reenabling to a bunch of macros in the Simple Executive sources to >> support it. >> >> The only reason one would run an o32 kernel on Octeon would be to >> run o32 world, >> which is better worked towards by adding o32 binary compatibility to >> n64 kernels >> along with, eventually, supporting multilib systems so o32 binaries >> can run >> alongside n32 and n64 ones. >> >> Discussed with: imp > > Thanks for fixing. > > Can anyone look at MALTA64 OCTEON1 SWARM64 SWARM64_SMP and XLR64 as > well? Those seem to be the last kernels failing on universe now. Yes. They are. In a n64 world they build fine. I'll look at the loops to see why they are even built, because they shouldn't be since we haven't integrated the n64 stuff into the MACHINE_ARCH name yet. Warner > > >> Deleted: >> head/sys/mips/conf/OCTEON1-32 >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D24E13F.3040807>