From: Scott Wood <scottwood@freescale.com>
To: Mahajan Vivek-B08308 <B08308@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Gala Kumar-B11780 <B11780@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>
Subject: Re: [PATCH v3 3/3] powerpc/fsl: 85xx: add cache-sram support
Date: Fri, 20 Nov 2009 11:38:59 -0600 [thread overview]
Message-ID: <20091120173859.GC18967@loki.buserror.net> (raw)
In-Reply-To: <F2F605B667B24B489C904986E0D60A08012221DF@zin33exm23.fsl.freescale.net>
On Thu, Nov 19, 2009 at 11:45:32PM -0700, Mahajan Vivek-B08308 wrote:
> > I really don't like setting the physical address this way,
> > can we not do this via the device tree?
>
> Cache-sram does not have any device tree entry since it is not a
> hardware as such. Putting it under chosen can be another option.
> I think, Scott (cc'ed) was of the opinion that since 32b base
> address support is missing; so there is no point in moving this
> address to the command line and .config should be okay for now
> for it.
I don't know what you mean by "32b base address support is missing". I have
no objection to putting it on the command line.
-Scott
next prev parent reply other threads:[~2009-11-20 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 12:50 [PATCH v3 1/3] powerpc/fsl: 85xx: document cache-sram size as a kernel parametric option Vivek Mahajan
2009-10-21 12:50 ` [PATCH v3 2/3] powerpc/fsl: 85xx: document cache-sram Vivek Mahajan
2009-10-21 12:50 ` [PATCH v3 3/3] powerpc/fsl: 85xx: add cache-sram support Vivek Mahajan
2009-11-19 14:21 ` Kumar Gala
2009-11-19 14:29 ` Kumar Gala
2009-11-19 17:45 ` Scott Wood
2009-11-19 18:51 ` Kumar Gala
2009-11-20 6:45 ` Mahajan Vivek-B08308
2009-11-20 17:38 ` Scott Wood [this message]
2009-12-01 5:36 ` Mahajan Vivek-B08308
2009-12-01 17:04 ` Scott Wood
2009-12-02 3:26 ` Kumar Gala
2009-10-21 17:50 ` [PATCH v3 2/3] powerpc/fsl: 85xx: document cache-sram Wolfgang Denk
2009-10-21 18:01 ` Scott Wood
2009-10-22 5:42 ` Mahajan Vivek-B08308
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=20091120173859.GC18967@loki.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B08308@freescale.com \
--cc=B11780@freescale.com \
--cc=linuxppc-dev@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).