From: Andy Whitcroft <apw@shadowen.org>
To: rmk+lkml@arm.linux.org.uk, haveblue@us.ibm.com
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: Finding what change broke ARM
Date: Fri, 24 Jun 2005 13:35:49 +0100 [thread overview]
Message-ID: <20050624123549.GA10636@shadowen.org> (raw)
In-Reply-To: <20050624113258.A27909@flint.arm.linux.org.uk>
> Well, this fixes the problem, but I doubt people will like it.
This looks like a problem with the way the configuration options where
changed to allow more than two memory models for SPARSMEM. I think the
right fix is the patch below. Russell could you try this one instead.
Dave, you did most of the work on the configuration side could you look
this over (assuming it works!).
-apw
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
---
Kconfig | 3 +--
1 files changed, 1 insertion(+), 2 deletions(-)
diff -upN reference/arch/arm/Kconfig current/arch/arm/Kconfig
--- reference/arch/arm/Kconfig
+++ current/arch/arm/Kconfig
@@ -161,7 +161,6 @@ config ARCH_RPC
config ARCH_SA1100
bool "SA1100-based"
select ISA
- select DISCONTIGMEM
config ARCH_S3C2410
bool "Samsung S3C2410"
@@ -345,7 +344,7 @@ config PREEMPT
config ARCH_DISCONTIGMEM_ENABLE
bool
- default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
+ default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM) || ARCH_SA1100
help
Say Y to support efficient handling of discontiguous physical memory,
for architectures which are either NUMA (Non-Uniform Memory Access)
next prev parent reply other threads:[~2005-06-24 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 9:19 Finding what change broke ARM Russell King
2005-06-24 9:53 ` Russell King
2005-06-24 10:32 ` Russell King
2005-06-24 12:35 ` Andy Whitcroft [this message]
2005-06-24 15:02 ` Dave Hansen
2005-06-24 11:04 ` Matthias Urlichs
2005-06-24 11:32 ` Alecs King
2005-06-24 12:39 ` Petr Baudis
2005-06-24 16:03 ` Linus Torvalds
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=20050624123549.GA10636@shadowen.org \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.