From: Thomas Schwinge <thomas@codesourcery.com>
To: linux-sh@vger.kernel.org
Subject: Re: Migo-R (SH7722) vs. NUMA
Date: Thu, 08 Mar 2012 07:07:36 +0000 [thread overview]
Message-ID: <87ipifo9jb.fsf@schwinge.name> (raw)
In-Reply-To: <8762egpvhn.fsf@schwinge.name>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Hi!
On Wed, 7 Mar 2012 17:24:30 -0800, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> wrote:
> > I've been working on upgrading the kernel for our Migo-R (SH7722) board
> > From ancient 2.6.30.6 to something more modern, 3.2. But, based on
> > migor_defconfig, it wouldn't boot, and instead just hang after the boot
> > loader. I bisected this to commit
> > 19d8f84f86af867abee174be8bf1e4941a59143d (2010-05-10). (To build this
> > tree, you need to cherry-pick 06225c08ec2ad0f0dec063df7f08773a8358db12
> > and apply the equivalent of c77b29db74a0ea4fdce0564a63b8876798625d64 to
> > arch/sh/kernel/setup.c.)
> >
> > By chance I figured out that disabling NUMA support (which is enabled for
> > migor_defconfig) would make it work again for this tree, as well as later
> > versions, such as the 3.2 release. I guess this should be fixed
> > properly?
>
> I forgot detail of MIGO-R.
> But in my quick check,
> my MIGO-R .config doesn't have CONFIG_NUMA since around v2.6.32-rc5
Hmm, where do you see/check that?
$ git blame -L /^CONFIG_NUMA/,+1 v3.2 -- arch/sh/configs/migor_defconfig
70f784ec (Magnus Damm 2008-02-07 00:38:24 +0900 16) CONFIG_NUMA=y
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
next prev parent reply other threads:[~2012-03-08 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 10:15 Migo-R (SH7722) vs. NUMA Thomas Schwinge
2012-03-08 1:24 ` Kuninori Morimoto
2012-03-08 7:07 ` Thomas Schwinge [this message]
2012-03-08 8:04 ` Kuninori Morimoto
2012-03-08 14:22 ` Thomas Schwinge
2012-03-22 3:28 ` Paul Mundt
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=87ipifo9jb.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=linux-sh@vger.kernel.org \
/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.