From: Kumar Gala <galak@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] 85xx: Add basic Uniprocessor MPC8572 DS port
Date: Thu, 13 Sep 2007 16:23:50 -0500 [thread overview]
Message-ID: <C5470240-1B7C-4AE2-912B-62B280C0904E@kernel.crashing.org> (raw)
In-Reply-To: <5bba19e33a518178eb46f2a1758cff40@kernel.crashing.org>
On Sep 13, 2007, at 11:53 AM, Segher Boessenkool wrote:
>>> What is a "front side cache"? What exactly does it cache? If it's
>>> a cache for one CPU only, that fact should be shown in the device
>>> tree somehow.
>>
>> Its in front of the memory controllers. Its not specific to a
>> given CPU.
>
> Ah, I see. That relationship is implicit in the device tree already,
> both this cache controller and that memory controller are child nodes
> of the same soc node, so your device tree is fine.
>
> Just for my own understanding, is this a coherent cache? (I'm too
> lazy to read the manual ;-) )
yes its coherent. Our caches tend to be coherent.
- k
next prev parent reply other threads:[~2007-09-13 21:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 6:29 [PATCH] [POWERPC] 85xx: Add basic Uniprocessor MPC8572 DS port Kumar Gala
2007-09-11 14:17 ` Scott Wood
2007-09-11 15:58 ` Kumar Gala
2007-09-12 13:20 ` Segher Boessenkool
2007-09-13 3:27 ` Kumar Gala
2007-09-13 16:53 ` Segher Boessenkool
2007-09-13 21:23 ` Kumar Gala [this message]
2007-09-11 14:18 ` Olof Johansson
2007-09-11 15:50 ` Kumar Gala
2007-09-11 15:55 ` Olof Johansson
2007-09-11 16:00 ` Kumar Gala
2007-09-11 17:15 ` Olof Johansson
2007-09-11 17:21 ` Scott Wood
2007-09-11 17:33 ` Olof Johansson
2007-09-11 17:48 ` Scott Wood
2007-09-11 17:59 ` Kumar Gala
2007-09-12 3:00 ` David Gibson
2007-09-12 3:35 ` Kumar Gala
2007-09-12 3:37 ` David Gibson
2007-09-12 3:37 ` Olof Johansson
2007-09-12 13:20 ` Segher Boessenkool
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=C5470240-1B7C-4AE2-912B-62B280C0904E@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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