linux-mips
[Top] [All Lists]

RE: MIPS 64?

To: "Kip Walker" <kwalker@broadcom.com>
Subject: RE: MIPS 64?
From: "Matthew Dharm" <mdharm@momenco.com>
Date: Wed, 15 May 2002 15:26:08 -0700
Cc: "Linux-MIPS" <linux-mips@oss.sgi.com>
Importance: Normal
In-reply-to: <3CE2DDEB.5DA6E868@broadcom.com>
Sender: owner-linux-mips@oss.sgi.com
Right....

So, how should my boot code convey that info?  With more
add_memory_region() calls?  Is that really all I need?

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: owner-linux-mips@oss.sgi.com
> [mailto:owner-linux-mips@oss.sgi.com]On Behalf Of Kip Walker
> Sent: Wednesday, May 15, 2002 3:15 PM
> To: Matthew Dharm
> Cc: Linux-MIPS
> Subject: Re: MIPS 64?
>
>
> Matthew Dharm wrote:
> >
> > I don't suppose anyone has a primer or white paper on the
> High Memory
> > stuff?  i.e. Applications, requirements, or a quick HOWTO?
>
> Well, the CONFIG option is at the bottom of the Machine
> Selection menu.
> With a fairly recent 2.4 or 2.5 kernel, it should build at work.
> Basically, if your firmware/boot code conveys info about
> regions above
> physical address 0x1fffffff, the kernel will allocate "struct page"
> entries for it, and add them to the pool of allocatable memory.  The
> kernel gets at them by mapping them into Kseg2/Kseg3 temporarily.
>
> turn it on, see what happens!  I haven't looked for a primer.
>
> Kip
>


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