From: "Kip Walker" <kwalker@broadcom.com>
To: "Matthew Dharm" <mdharm@momenco.com>
Cc: Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: MIPS 64?
Date: Wed, 15 May 2002 14:55:39 -0700 [thread overview]
Message-ID: <3CE2D95B.E1E43662@broadcom.com> (raw)
In-Reply-To: 20020515214818.GA1991@nevyn.them.org
Since traditionally the mips kernel could only manage RAM reachable by
Kseg you were limited to 512MB, right? But now the High Memory stuff is
stable enough that you can reach any RAM that's physically addressable
in 32-bits. And after that, there's the 64bit-physical-address
extension which allows you to reach physical pages that need > 32-bits
to address.
Kip
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?
>
> >
> > What does it take to do a 64-bit port? The first problem I see is the
> > boot loader -- do I have to be in 64-bit mode when the kernel starts,
> > or can I start in 32-bit mode and then transfer to 64-bit mode?
> >
> > I looked in the arch/mips64/ directory, but I don't see much for
> > specific boards there, but there are references to the Malta
> > boards....
> >
> > 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
> >
> >
>
> --
> Daniel Jacobowitz Carnegie Mellon University
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-15 21:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 21:34 MIPS 64? Matthew Dharm
2002-05-15 21:48 ` Daniel Jacobowitz
2002-05-15 21:55 ` Kip Walker [this message]
2002-05-15 22:08 ` Matthew Dharm
2002-05-15 22:08 ` Matthew Dharm
2002-05-15 22:15 ` Kip Walker
2002-05-15 22:26 ` Matthew Dharm
2002-05-15 22:29 ` Kip Walker
2002-05-19 19:29 ` Ralf Baechle
2002-05-19 19:25 ` Ralf Baechle
2002-05-15 21:59 ` Jun Sun
2002-05-15 22:16 ` Matthew Dharm
2002-05-19 19:32 ` Ralf Baechle
2002-05-16 3:28 ` Dan Malek
2002-05-16 7:15 ` Kevin D. Kissell
2002-05-16 17:13 ` Jun Sun
2002-05-19 19:44 ` Ralf Baechle
2002-05-19 19:41 ` Ralf Baechle
2002-05-19 19:30 ` Ralf Baechle
2002-05-20 10:06 ` Maciej W. Rozycki
2002-05-20 15:57 ` Greg Lindahl
2002-05-20 16:05 ` Maciej W. Rozycki
2002-05-21 16:47 ` Florian Lohoff
2002-05-21 17:00 ` Greg Lindahl
2002-05-20 19:05 ` Ralf Baechle
2002-05-19 19:24 ` Ralf Baechle
2002-05-19 19:23 ` Ralf Baechle
2002-05-20 6:05 ` Matthew Dharm
2002-05-20 20:30 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CE2D95B.E1E43662@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@oss.sgi.com \
--cc=mdharm@momenco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox