All of lore.kernel.org
 help / color / mirror / Atom feed
From: Becky Bruce <beckyb@kernel.crashing.org>
To: Eduard Fuchs <edfuchs@uni-kassel.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 8641D with linux 2.6.29 did'n show second cpu
Date: Tue, 31 Mar 2009 15:04:17 -0500	[thread overview]
Message-ID: <61576250-3589-4D1D-9335-30AA27BD3620@kernel.crashing.org> (raw)
In-Reply-To: <200903311706.55478.edfuchs@uni-kassel.de>

On Mar 31, 2009, at 10:06 AM, Eduard Fuchs wrote:

> Hi,
>
> Am Dienstag 31 M=E4rz 2009 15:20:21 schrieb Kumar Gala:
>> On Mar 31, 2009, at 5:15 AM, Eduard Fuchs wrote:
>>> Hi,
>>>
>>> I'm testing the evaluation board from freescale (MPC8641DHPCN) with
>>> the latest
>>> linux kernel (2.6.29) and the second core seems disabled. CONFIG_SPM
>>> is
>>> enabled but the /proc/cpuinfo shows only one cpu. With original
>>> 2.6.27 kernel
>>> both cpu cores appears in /proc/cpuinfo.
>>>
>>> Has anyone an idea how can i enable the second core?
>>
>> Are you using u-boot?  I can't remember if you need a newer u-boot to
>> deal with changes in how we bring up the second core.
>
> Yes. My u-boot version is 2009.03. Are there some additional config =20=

> keys for
> SMP support in u-boot?

Hrm, I am able to reproduce this here - the second processor is =20
reported as stuck and once we're booted, I only see one CPU online.  =20
Let me poke around and see if I can figure out what's going on here.

Cheers,
Becky

  reply	other threads:[~2009-03-31 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 10:15 8641D with linux 2.6.29 did'n show second cpu Eduard Fuchs
2009-03-31 13:20 ` Kumar Gala
2009-03-31 15:06   ` Eduard Fuchs
2009-03-31 20:04     ` Becky Bruce [this message]
2009-03-31 23:27     ` Kumar Gala
2009-04-01  4:10     ` Kumar Gala
2009-04-01 13:36       ` Eduard Fuchs
2009-04-01 13:48         ` Kumar Gala

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=61576250-3589-4D1D-9335-30AA27BD3620@kernel.crashing.org \
    --to=beckyb@kernel.crashing.org \
    --cc=edfuchs@uni-kassel.de \
    --cc=linuxppc-dev@ozlabs.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.