From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Regarding MPC8640D second core initialization
Date: Wed, 02 Dec 2009 10:41:04 +0100 [thread overview]
Message-ID: <20091202094104.283964C025@gemini.denx.de> (raw)
In-Reply-To: <37EF3A462AFE4B5090E87F6B7F3F330F@itd210>
Dear "Thirumalai",
In message <37EF3A462AFE4B5090E87F6B7F3F330F@itd210> you wrote:
> Hi denx,
> I am using 2009-06 u-boot for MPC8640D based board. i just want to
> know whether the second core of MPC8640D is kicked off automatically or will
> it required by the user to kick. Also if am enabling the CONFIG_MP macro and
> CONFIG_NUM_CPUS as 2, then the reset command of the target is not
> working(means board is getting hanged). I have mentioned the value of
> CONFIG_SYS_SCRATCH_VA as 0xf5000000.
>
> Kindly suggest me what might be the error.
Which "MPC8640D based board" is this exactly?
At the moment we have 3 MPC86xx boards in mainline, and the
MAINTAINERS file will tell you who is responsible for these.
If you have a custom board with an out-of-tree port you will have to
ask those who provided the port to you.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Alles Gescheite ist schon gedacht worden, man mu? nur versuchen,
es noch einmal zu denken. -- Goethe, Maximen und Reflexionen
next prev parent reply other threads:[~2009-12-02 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 9:34 [U-Boot] Regarding MPC8640D second core initialization Thirumalai
2009-12-02 9:41 ` Wolfgang Denk [this message]
2009-12-02 9:55 ` Thirumalai
2009-12-02 21:06 ` Becky Bruce
2009-12-02 22:04 ` [U-Boot] [PATCH] Jon Loeliger is not maintaining any Freescale board Jon Loeliger
2009-12-02 22:59 ` Wolfgang Denk
2009-12-03 4:36 ` [U-Boot] Regarding MPC8640D second core initialization Thirumalai
2009-12-03 17:39 ` Becky Bruce
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=20091202094104.283964C025@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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.