| To: | Daniel Jacobowitz <dan@debian.org> |
|---|---|
| Subject: | Re: MIPS 64? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Sun, 19 May 2002 12:24:19 -0700 |
| Cc: | Matthew Dharm <mdharm@momenco.com>, Linux-MIPS <linux-mips@oss.sgi.com> |
| In-reply-to: | <20020515214818.GA1991@nevyn.them.org>; from dan@debian.org on Wed, May 15, 2002 at 05:48:18PM -0400 |
| References: | <NEBBLJGMNKKEEMNLHGAIOEPPCGAA.mdharm@momenco.com> <20020515214818.GA1991@nevyn.them.org> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5.1i |
On Wed, May 15, 2002 at 05:48:18PM -0400, Daniel Jacobowitz wrote: > On Wed, May 15, 2002 at 02:34:47PM -0700, Matthew Dharm wrote: > > So... I'm looking at porting Linux to a system with 1.5GiB of RAM. > > That kinda blows the 32-bit MIPS port option right out of the water... > > Not unless you count bits differently than I do... 32-bit is 4 GiB. Is > there any reason MIPS has special problems in this area? The basic assumption is that we can address all memory through KSEG0. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: MIPS 64?, Ralf Baechle |
|---|---|
| Next by Date: | Re: MIPS 64?, Ralf Baechle |
| Previous by Thread: | Re: MIPS 64?, Ralf Baechle |
| Next by Thread: | Re: MIPS 64?, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |