From: Scott Wood <scottwood@freescale.com>
To: Carl-Erwin GRIFFITH <carl.erwin@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: 82xx multiple soc support/initialization
Date: Tue, 26 May 2009 15:25:30 -0500 [thread overview]
Message-ID: <20090526202530.GA2342@b07421-ec1.am.freescale.net> (raw)
In-Reply-To: <5c90346a0905250723t2c9d30a0qd4fbebed38917cd7@mail.gmail.com>
On Mon, May 25, 2009 at 04:23:37PM +0200, Carl-Erwin GRIFFITH wrote:
> Hi guys,
>
>
> I'm working on an derived muas3001 board (kernel version 2.6.30-rc5),
>
> and so far I did not find an example of multiple SOCs initialization.
>
> The board has 3 cpus (only one core activated).
This is not currently supported -- there are lots of places, especially
in 82xx/CPM code, that assume there's only one instance of the SoC.
> 1) Is there a special syntax to use in the device tree ?
You'd have multiple instances of the soc node (plus kernel changes to
make this work). You'll probably need some way of indicating which one
contains the running core.
-Scott
prev parent reply other threads:[~2009-05-26 20:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 14:23 82xx multiple soc support/initialization Carl-Erwin GRIFFITH
2009-05-26 20:25 ` Scott Wood [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=20090526202530.GA2342@b07421-ec1.am.freescale.net \
--to=scottwood@freescale.com \
--cc=carl.erwin@gmail.com \
--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 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).