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 15:15:07 -0700 [thread overview]
Message-ID: <3CE2DDEB.5DA6E868@broadcom.com> (raw)
In-Reply-To: NEBBLJGMNKKEEMNLHGAIAEABCHAA.mdharm@momenco.com
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
next prev parent reply other threads:[~2002-05-15 22:14 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
2002-05-15 22:08 ` Matthew Dharm
2002-05-15 22:08 ` Matthew Dharm
2002-05-15 22:15 ` Kip Walker [this message]
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=3CE2DDEB.5DA6E868@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