linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vivek Mahajan <vivek.mahajan@freescale.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: kumar.gala@freescale.com, Vivek Mahajan <vivek.mahajan@freescale.com>
Subject: [PATCH 1/4] powerpc/fsl: 85xx: document cache-sram size as a kernel parametric option
Date: Wed, 23 Sep 2009 17:03:21 +0530	[thread overview]
Message-ID: <1253705604-1986-1-git-send-email-vivek.mahajan@freescale.com> (raw)

Adds documentation for the size parameter of Freescale's QorIQ
based cache-sram

Signed-off-by: Vivek Mahajan <vivek.mahajan@freescale.com>
---
 Documentation/kernel-parameters.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 0f17d16..3213844 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -412,6 +412,9 @@ and is between 256 and 4096 characters. It is defined in the file
 
 	c101=		[NET] Moxa C101 synchronous serial card
 
+	cache-sram-size=	[PPC] Size of Freescale's QorIQ Cache SRAM
+			See Documentation/powerpc/fsl_85xx_cache_sram.txt.
+
 	cachesize=	[BUGS=X86-32] Override level 2 CPU cache size detection.
 			Sometimes CPU hardware bugs make them report the cache
 			size incorrectly. The kernel will attempt work arounds
-- 
1.5.6.5

             reply	other threads:[~2009-09-23 11:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 11:33 Vivek Mahajan [this message]
2009-09-23 11:33 ` [PATCH 2/4] powerpc/fsl: 85xx: document cache-sram Vivek Mahajan
2009-09-23 11:33   ` [PATCH 3/4] powerpc/fsl: 85xx: add mbar() Vivek Mahajan
2009-09-23 11:33     ` [PATCH 4/4] powerpc/fsl: 85xx: add cache-sram support Vivek Mahajan
2009-09-24  9:10 [PATCH 1/4] powerpc/fsl: 85xx: document cache-sram size as a kernel parametric option Vivek Mahajan

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=1253705604-1986-1-git-send-email-vivek.mahajan@freescale.com \
    --to=vivek.mahajan@freescale.com \
    --cc=kumar.gala@freescale.com \
    --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;
as well as URLs for NNTP newsgroup(s).