linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Ming Liu" <eemingliu@hotmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Xilinx FX60
Date: Wed, 5 Sep 2007 16:55:10 -0600	[thread overview]
Message-ID: <fa686aa40709051555m7f10bd95r48bd2eac7c7d0830@mail.gmail.com> (raw)
In-Reply-To: <BAY138-F27BF81B9795BD26A16564BB2CB0@phx.gbl>

On 9/5/07, Ming Liu <eemingliu@hotmail.com> wrote:
>
> > > Is it then possible to run two independent kernels, one on each PPC??
> >
> >Absolutely.
>
> Are you meaning two entirely seperate systems, or two ones which share a
> common HW such as memory space? Is that possible without any memory
> confliction?

You can share physical memory as long as each processor is dedicated
to separate regions.  However, Linux on power expects memory to be
based at 0.  Therefore you need to tweak the memory design so that the
second processor sees a different area of the ram based at zero.

You can even setup a shared memory region between the two processors,
but you that region should be cache-inhibited.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-09-05 22:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 18:42 Xilinx FX60 Robert Woodworth
2007-09-05 18:56 ` Wood, Robert (GE Indust, GE Fanuc)
2007-09-05 19:30   ` Robert Woodworth
2007-09-05 20:00     ` Wood, Robert (GE Indust, GE Fanuc)
2007-09-05 19:42 ` Sergey Temerkhanov
2007-09-05 20:20   ` Robert Woodworth
2007-09-05 20:31     ` Grant Likely
2007-09-05 20:39       ` Ming Liu
2007-09-05 22:55         ` Grant Likely [this message]
2007-09-05 21:36     ` Sergey Temerkhanov
2007-09-05 20:40   ` Ming Liu
2007-09-05 22:05     ` Sergey Temerkhanov
  -- strict thread matches above, loose matches on Subject: below --
2007-09-18 20:58 Robert Woodworth
2007-09-18 21:02 ` Grant Likely
2007-09-18 21:14   ` Robert Woodworth
2007-09-18 22:13     ` Koss, Mike (Mission Systems)

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=fa686aa40709051555m7f10bd95r48bd2eac7c7d0830@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=eemingliu@hotmail.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).