From: Kumar Gala <galak@kernel.crashing.org>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Rai Harninder-B01044 <B01044@freescale.com>
Subject: Re: [PATCH] powerpc/fsl: 85xx: add cache-sram support
Date: Wed, 13 Oct 2010 09:17:53 -0500 [thread overview]
Message-ID: <7CC89883-0AF0-42F3-B2E0-9DB7C69597C3@kernel.crashing.org> (raw)
In-Reply-To: <AANLkTi=8q-8+ZR=unxZdhQQZsn33hte_VNEvZpE0uGgp@mail.gmail.com>
On Oct 12, 2010, at 12:19 PM, Hollis Blanchard wrote:
> On Tue, Oct 12, 2010 at 10:02 AM, Rai Harninder-B01044
> <B01044@freescale.com> wrote:
>> Currently the design is that we divide the sram portion into 2 equal
>> parts for AMP
>> That was the part of initial requirement
>> Do we want to remove that?
>
> Why wouldn't you just pass different cache-sram-size/offset values to
> each kernel?
That was what I was suggesting, but probably wasn't clear :)
- k
prev parent reply other threads:[~2010-10-13 14:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 10:25 [PATCH] powerpc/fsl: 85xx: add cache-sram support harninder.rai
2010-10-12 14:09 ` Kumar Gala
2010-10-12 17:02 ` Rai Harninder-B01044
2010-10-12 17:19 ` Hollis Blanchard
2010-10-13 14:17 ` 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=7CC89883-0AF0-42F3-B2E0-9DB7C69597C3@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=B01044@freescale.com \
--cc=hollis@penguinppc.org \
--cc=linuxppc-dev@lists.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