From: Segher Boessenkool <segher@kernel.crashing.org>
To: Stefan Roese <sr@denx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/2] [POWERPC] Add L2 cache node to AMCC Taishan dts file
Date: Tue, 18 Mar 2008 23:40:47 +0100 [thread overview]
Message-ID: <23bc1271d080c41ab54a4917d256a76b@kernel.crashing.org> (raw)
In-Reply-To: <1205847466-17854-1-git-send-email-sr@denx.de>
> + L2C0: l2c@30 {
> + compatible = "ibm,l2-cache-440gx", "ibm,l2-cache";
> + dcr-reg = <20 8 /* Internal SRAM DCR's */
> + 30 8>; /* L2 cache DCR's */
The unit address is based on the _first_ entry in "reg". No2 this
is "dcr-reg", but you don't really want to be more incompatible than
necessary...
Segher
next prev parent reply other threads:[~2008-03-18 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 13:37 [PATCH 2/2] [POWERPC] Add L2 cache node to AMCC Taishan dts file Stefan Roese
2008-03-18 22:40 ` Segher Boessenkool [this message]
2008-03-19 6:30 ` Stefan Roese
2008-03-18 23:24 ` David Gibson
2008-03-19 6:24 ` Stefan Roese
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=23bc1271d080c41ab54a4917d256a76b@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sr@denx.de \
/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).