| To: | Matthew Dharm <mdharm@momenco.com> |
|---|---|
| Subject: | Re: MIPS 64? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Sun, 19 May 2002 12:29:11 -0700 |
| Cc: | Kip Walker <kwalker@broadcom.com>, Linux-MIPS <linux-mips@oss.sgi.com> |
| In-reply-to: | <NEBBLJGMNKKEEMNLHGAICEACCHAA.mdharm@momenco.com>; from mdharm@momenco.com on Wed, May 15, 2002 at 03:26:08PM -0700 |
| References: | <3CE2DDEB.5DA6E868@broadcom.com> <NEBBLJGMNKKEEMNLHGAICEACCHAA.mdharm@momenco.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5.1i |
On Wed, May 15, 2002 at 03:26:08PM -0700, Matthew Dharm wrote: > So, how should my boot code convey that info? With more > add_memory_region() calls? Is that really all I need? Yes. At this time you just have to make sure you don't add_memory_region() areas which aren't supported by your particular kernel configuration. There is also a second limit which is memory above physical address 4GB; if you need that you have to enable CONFIG_64BIT_PHYS_ADDR as well. 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?, Kip Walker |
| Next by Thread: | Re: MIPS 64?, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |