linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Eduard Fuchs <edfuchs@uni-kassel.de>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	u-boot-dev U-Boot-UBOOTDEV <ubootdev@freescale.com>
Subject: Re: 8641D with linux 2.6.29 did'n show second cpu
Date: Wed, 1 Apr 2009 08:48:23 -0500	[thread overview]
Message-ID: <88CDAB76-B128-4C01-9834-05B9A480EB98@kernel.crashing.org> (raw)
In-Reply-To: <200904011536.39689.edfuchs@uni-kassel.de>


On Apr 1, 2009, at 8:36 AM, Eduard Fuchs wrote:

> Hi,
>
> Am Mittwoch 01 April 2009 06:10:36 schrieb Kumar Gala:
>> 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) =20
>>>>> with
>>>>> the latest
>>>>> linux kernel (2.6.29) and the second core seems disabled. =20
>>>>> 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-=20
>>>> 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
>>> keys for
>>> SMP support in u-boot?
>>
>> It appears we introduced a bug in v2009.03 of u-boot.
>
> I never thought that the problem could be in u-boot. I tested the =20
> board with
> u-boot v2009.01 and it works well.

the u-boot bug is that we are over-writting the page of code we need =20
to bring up the second core.  Thus when the kernel releases the 2nd =20
core it goes off in the weeds.

I've sent some patches to the u-boot list that should fix the problem =20=

by making sure that u-boot avoids using the page of memory we need for =20=

the 2nd core.

- k=

      reply	other threads:[~2009-04-01 13:48 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
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 [this message]

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=88CDAB76-B128-4C01-9834-05B9A480EB98@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=edfuchs@uni-kassel.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ubootdev@freescale.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;
as well as URLs for NNTP newsgroup(s).