Subject: [PATCH 02/14] omap: Map only available sram memory

From: [email-masked] (Tony Lindgren)
Date: Fri, 1 Oct 2010 15:53:03 -0700

* Grazvydas Ignotas <[email-masked]> [101001 13:07]:
> On Fri, Sep 17, 2010 at 12:47 PM, Santosh Shilimkar
> <[email-masked]> wrote:
> > Currently we map 1 MB section while setting up SRAM on OMAPs.
> > The actual physcal OCM RAM available on OMAP SOCs is in order
> > of KBs. This patch maps only available sram and removes some
> > non necessary cpu_is_xxx checks.
> >
> > On the newer ARMs with speculation, this is dangerous and can
> > result in untraceable aborts.
> >
> > Signed-off-by: Santosh Shilimkar <[email-masked]>
> 
> This hangs OMAP3 pandora:
> 
> [    0.000000] Linux version
> 2.6.36-rc6-next-20101001-00002-ge76bb53-dirty (notaz at pixelinis) (gcc
> version 4.3.3 (Sourcery G++ Lite 2009q1-20
> [    0.000000] CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c53c7f
> [    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing
> instruction cache
> [    0.000000] Machine: Pandora Handheld Console
> [    0.000000] Ignoring unrecognised tag 0x54410008
> [    0.000000] bootconsole [earlycon0] enabled
> [    0.000000] Reserving 6422528 bytes SDRAM for VRAM
> [    0.000000] Memory policy: ECC disabled, Data cache writeback
> [    0.000000] OMAP3430/3530 ES2.1 (l2cache iva sgx neon isp )
> [    0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
> (stuck here)
> 
> reverting this fixes the problem.

Hmm, boots fine here with overo. Any idea what in this patch breaks
pandora?

Tony