From: "sarah.ddff" <sarah.ddff@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: two linux 2.6 kernels on two ppc405 (xupv2p) ?
Date: Fri, 12 Dec 2008 08:13:26 -0800 (PST) [thread overview]
Message-ID: <20978466.post@talk.nabble.com> (raw)
Hi all,
I want to implement a multiprocessor system managed by a linux kernel on the
xupv2p.
I knwo that there is no cache coherency between the two ppc405 cores.
Consequently,
SMP linux can not be used.
So the only solution is to install two linux kernels, each on a ppc
processor,
and to make them communicate with shared memory.
My questions are:
does someone succeed in doing this?
Is it possible to do this ?
thanks
--
View this message in context: http://www.nabble.com/two-linux-2.6-kernels-on-two-ppc405-%28xupv2p%29---tp20978466p20978466.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next reply other threads:[~2008-12-12 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 16:13 sarah.ddff [this message]
2008-12-13 1:29 ` two linux 2.6 kernels on two ppc405 (xupv2p) ? Josh Boyer
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=20978466.post@talk.nabble.com \
--to=sarah.ddff@gmail.com \
--cc=linuxppc-embedded@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).