See, it's answers like this that make me skeptical and confused... So MIPS64 denotes 64-bit data _and_ address? Great. But, what is the current state of the toolchain? I mean, what point is having the code if the tools won't compile it properly? I guess what I'm looking for is what I should tell someone who wants to run MIPS Linux 64-bit with 8 gigs of RAM. Matt -- Matthew D. Dharm Senior Software Designer Momentum Computer Inc. 1815 Aston Ave. Suite 107 (760) 431-8663 X-115 Carlsbad, CA 92008-7310 Momentum Works For You www.momenco.com > -----Original Message----- > From: Jason Gunthorpe [mailto:jgg@debian.org] > Sent: Monday, January 14, 2002 12:13 AM > To: Matthew Dharm > Cc: linux-mips@oss.sgi.com > Subject: Re: MIPS64 status? > > > > On Sun, 13 Jan 2002, Matthew Dharm wrote: > > > As I understand it, 64-bit support is really two > different things: 64-bit > > data path (i.e. unsigned long long) and 64-bit addressing > (for more than 4G > > of RAM). > > I suppose you could say that. I think I saw someone post to > this list > that they were working on a patch to enable 64 bit > registers with a 32 bit > kernel. > > > My understanding is that "MIPS64" generally refers to a > kernel which > > supports a 64-bit data path, but we're still limited to > 32-bit addressing. > > Is that correct? > > The mips64 tree in CVS is one that is a 64 bit addressing > capable kernel. > AFAIK the linx convention is that <foo>64 refers to > addressing (which > probably impiles register width too :>) > > I'm not sure what the current state of the ELF64 MIPS toolchain is. > > Jason >
