From: "Mahajan Vivek-B08308" <Vivek.Mahajan@freescale.com>
To: "Wolfgang Denk" <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org, Gala Kumar-B11780 <kumar.gala@freescale.com>
Subject: RE: [PATCH v3 2/3] powerpc/fsl: 85xx: document cache-sram
Date: Thu, 22 Oct 2009 11:12:21 +0530 [thread overview]
Message-ID: <F2F605B667B24B489C904986E0D60A080122179E@zin33exm23.fsl.freescale.net> (raw)
In-Reply-To: <20091021175012.ED29819F73@gemini.denx.de>
Wolfgang Denk Sent: Wednesday, October 21, 2009 11:20 PM
> > * How to enable it from a low level driver
> > * How to set its size
> ...
> > +The size of the above cache SRAM memory window is passed via the=20
> > +kernel command line as <cache-sram-size=3D....>
>=20
> Would it not make more sense to configure this property=20
> through the device tree?=20
Since this parameter needs to be passed run time to the kernel=20
and it was not preconfigured by u-boot; so it landed in the=20
cmdline instead of the device tree.
>=20
> Best regards,
>=20
> Wolfgang Denk
>=20
Thanks,
Vivek
prev parent reply other threads:[~2009-10-22 5:42 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
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 [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=F2F605B667B24B489C904986E0D60A080122179E@zin33exm23.fsl.freescale.net \
--to=vivek.mahajan@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@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).