README.SPL: Move the 'Estimating stack usage' from omap3 to here

The instructions are generic, so move to the generic doc.

Signed-off-by: Tom Rini <trini@ti.com>

1 files changed, 0 insertions, 22 deletions

diff --git a/doc/SPL/README.omap3 b/doc/SPL/README.omap3
index a543e65d39..c77ca4300a 100644
--- a/doc/SPL/README.omap3
+++ b/doc/SPL/README.omap3
@@ -50,25 +50,3 @@ For the areas that reside within DDR1 they must not be used prior to s_init()
 completing.  Note that CONFIG_SYS_TEXT_BASE must be clear of the areas that SPL
 uses while running.  This is why we have two versions of the memory map that
 only vary in where the BSS and malloc pool reside.
-
-Estimating stack usage
-----------------------
-
-With gcc 4.6 (and later) and the use of GNU cflow it is possible to estimate
-stack usage at various points in run sequence of SPL.  The -fstack-usage option
-to gcc will produce '.su' files (such as arch/arm/cpu/armv7/syslib.su) that
-will give stack usage information and cflow can construct program flow.
-
-Must have gcc 4.6 or later, which supports -fstack-usage
-
-1) Build normally
-2) Perform the following shell command to generate a list of C files used in
-SPL:
-$ find spl -name '*.su' | sed -e 's:^spl/::' -e 's:[.]su$:.c:' > used-spl.list
-3) Execute cflow:
-$ cflow --main=board_init_r `cat used-spl.list` 2>&1 | $PAGER
-
-cflow will spit out a number of warnings as it does not parse
-the config files and picks functions based on #ifdef.  Parsing the '.i'
-files instead introduces another set of headaches.  These warnings are
-not usually important to understanding the flow, however.