linux-mips
[Top] [All Lists]

Re: IP32 - issues with last CVS snapshoot

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: IP32 - issues with last CVS snapshoot
From: "Stephen P. Becker" <geoman@gentoo.org>
Date: Fri, 11 Feb 2005 14:38:59 -0500
Cc: "Ilya A. Volynets-Evenbakh" <ilya@total-knowledge.com>, Frederic TEMPORELLI - astek <ftemporelli@astek.fr>, linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.61L.0502111915510.30117@blysk.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <420CEE7F.3080201@astek.fr> <420CF611.5030705@gentoo.org> <Pine.LNX.4.61L.0502111825300.30117@blysk.ds.pg.gda.pl> <420D006E.3000107@total-knowledge.com> <Pine.LNX.4.61L.0502111915510.30117@blysk.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 0.8 (Windows/20040913)
Maciej W. Rozycki wrote:
On Fri, 11 Feb 2005, Ilya A. Volynets-Evenbakh wrote:


O64 may not be supported ABI, but it provides us with a feature that is really
usefull:
specifically, it generates 32 bit symbol addresses instead of 64 bit ones.
This cuts
down on code size considerably. If this feature was implemented in toolchain
as separate
switch, O64 hack could go away.


Well, the topic has been beaten to death here, so you don't really need to illuminate me -- it's only due to this popular request I've implemented the ability to do 32-bit builds for 64-bit kernel. I just wonder why people insisting on such a setup don't actually contribute some code to do that cleanly and keep switching between hacks as they stop working one by one...


Well, it wasn't my intention to beat anything to death mentioning the o64 hack. I'm just pointing out that using n64 for an ip32 kernel results in a broken kernel at this point in time...plain and simple. Therefore we have to use this hack. Another point though is that n64 kernels are very large, and apparently ip32 has issues booting kernels larger than about 8mb. So either way, n64 isn't a good idea for o32 at this time.

Steve


<Prev in Thread] Current Thread [Next in Thread>