With commit 47a4bea6af77b01d59a410d09a4c34b2dd14cf50 ("ARM: omap4: Update sdram setting for panda rev A6") which attempted to "fix" Panda ES B3 problem of a different DDR by checking for CPU revision and changing configuration as per Panda for configuration that is common for SDP4430 and Panda.
This resulted in all OMAP4430 SDP with processor boards > ES2.3 being now broken. This does not obviously help the situation :). So fix it by doing the missing DMM configuration needed for Panda as an override of the weak function and revert the bad commit.
based on v2015.01-rc3 tag.
Bootlogs: http://slexy.org/view/s2r58bpvpp (Panda ES B3) http://slexy.org/view/s20v9cq7mc (SDP4430 ES2.3)
previously (broken v2015.01-rc3 for SDP4430 ES2.3 : http://slexy.org/view/s2fPVW28hd)
Nishanth Menon (2): ARM: OMAP4: Panda: rework DMM logic Revert "ARM: omap4: Update sdram setting for panda rev A6"
arch/arm/cpu/armv7/omap4/sdram_elpida.c | 4 ---- arch/arm/include/asm/arch-omap4/sys_proto.h | 3 +++ board/ti/panda/panda.c | 16 ++++++++++++++++ 3 files changed, 19 insertions(+), 4 deletions(-)