linux-mips
[Top] [All Lists]

Re: Kernel 2.6 for R4600 Indy

To: Robin Humble <rjh@cita.utoronto.ca>
Subject: Re: Kernel 2.6 for R4600 Indy
From: "Stephen P. Becker" <geoman@gentoo.org>
Date: Fri, 24 Sep 2004 11:13:18 -0400
Cc: linux-mips@linux-mips.org
In-reply-to: <20040924134334.GB27739@lemming.cita.utoronto.ca>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <4152D58B.608@longlandclan.hopto.org> <4152E4FC.8000408@gentoo.org> <41536765.9000304@longlandclan.hopto.org> <41541B8D.3060500@gentoo.org> <20040924131734.GC26710@lemming.cita.utoronto.ca> <415420D0.60102@gentoo.org> <20040924134334.GB27739@lemming.cita.utoronto.ca>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 0.8 (X11/20040916)
day). Also, Indys don't support a large enough memory configuration that 64-bit would be worth it anyhow.


indeed they don't.
do you get access to more registers or more efficient instruction sets
like you do on x86_64?


What you would *really* want on such a machine would be n32 userland. You get full 64-bit instructions, but the binaries aren't huge.


Yeah, that is what n32 is for. You get more registers, but pointers are still 32-bit. You still need a mips64 CHOST to build n32 binaries, however.

Steve


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