Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: "tiansm@lemote.com" <tiansm@lemote.com>,
	linux-mips@linux-mips.org, Fuxin Zhang <zhangfx@lemote.com>
Subject: Re: [PATCH] cheat for support of more than 256MB memory
Date: Wed, 6 Jun 2007 17:40:18 +0100	[thread overview]
Message-ID: <20070606164018.GA30017@linux-mips.org> (raw)
In-Reply-To: <cda58cb80706052338y461f707fq790e204f55a23cc0@mail.gmail.com>

On Wed, Jun 06, 2007 at 08:38:18AM +0200, Franck Bui-Huu wrote:

> >diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
> >index 4975da0..62ef100 100644
> >--- a/arch/mips/kernel/setup.c
> >+++ b/arch/mips/kernel/setup.c
> >@@ -509,6 +509,14 @@ static void __init resource_init(void)
> >                res->end = end;
> >
> >                res->flags = IORESOURCE_MEM | IORESOURCE_BUSY;
> >+#if defined(CONFIG_LEMOTE_FULONG) && defined(CONFIG_64BIT)
> >+               /* to keep memory continous, we tell system 0x10000000 - 
> >0x20000000 is reserved
> >+                * for memory, in fact it is io region, don't occupy it
> >+                *
> >+                * SPARSEMEM?
> 
> Definetly yes ! It has been designed for such issue and it should save
> you some memory.

A hole of 256MB size in the memory address map will cost 3.5MB with a 64-bit
kernel.  The other reason why I don't like this patch is that it drags
platform specific code into the generic MIPS code.

  Ralf

  reply	other threads:[~2007-06-06 16:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06  4:42 Lemote Loongson 2E patch update tiansm
2007-06-06  4:42 ` [PATCH] new files for lemote fulong mini-PC support tiansm
2007-06-06  4:42 ` [PATCH] arch related Makefile update for lemote fulong mini-PC tiansm
2007-06-06  4:42 ` [PATCH] Kconfig update for lemote fulong miniPC tiansm
2007-06-06  4:42 ` [PATCH] TO_PHYS_MASK for loongson2 tiansm
2007-06-06  4:42 ` [PATCH] add MACH_GROUP_LEMOTE & MACH_LEMOTE_FULONG tiansm
2007-06-06  4:42 ` [PATCH] define Hit_Invalidate_I to Index_Invalidate_I for loongson2 tiansm
2007-06-06  4:42 ` [PATCH] add Loongson processor definitions tiansm
2007-06-06  4:42 ` [PATCH] define MODULE_PROC_FAMILY for Loongson2 tiansm
2007-06-06  4:42 ` [PATCH] add serial port definition for lemote fulong tiansm
2007-06-06  4:42 ` [PATCH] make cpu_probe recognize Loongson2 tiansm
2007-06-06  4:42 ` [PATCH] add Loongson support to /proc/cpuinfo tiansm
2007-06-06  4:42 ` [PATCH] cheat for support of more than 256MB memory tiansm
2007-06-06  6:38   ` Franck Bui-Huu
2007-06-06 16:40     ` Ralf Baechle [this message]
2007-06-08  4:47       ` Tian
2007-06-08  7:52         ` Tian
2007-06-08  7:54           ` Tian
2007-06-06  4:42 ` [PATCH] define MODULE_PROC_FAMILY for Loongson2 tiansm
2007-06-06  4:42 ` [PATCH] tlb handling support for Loongson2 processor tiansm
2007-06-06  4:42 ` [PATCH] work around for more than 256MB memory support tiansm
2007-06-06 13:55 ` Lemote Loongson 2E patch update John W. Linville
2007-06-06 16:50   ` Ralf Baechle
2007-06-07  6:05     ` Fuxin Zhang

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=20070606164018.GA30017@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=linux-mips@linux-mips.org \
    --cc=tiansm@lemote.com \
    --cc=vagabon.xyz@gmail.com \
    --cc=zhangfx@lemote.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