On 10/08/2009 09:54 AM, Syed Mohammed, Khasim wrote:


-----Original Message-----
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Gary Thomas
Sent: Thursday, October 08, 2009 10:17 AM
To: Menon, Nishanth
Cc: Adam Machalek; linux-omap@vger.kernel.org
Subject: Re: X-loader / U-Boot query

On 10/08/2009 09:14 AM, Menon, Nishanth wrote:
-----Original Message-----
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Adam Machalek
Sent: Thursday, October 08, 2009 9:47 AM
To: Gary Thomas
Cc: linux-omap@vger.kernel.org
Subject: Re: X-loader / U-Boot query

The problem is located in u-boot/cpu/arm_cortexa8/omap3/mem.c

Function do_sdrc_init()

There is an assumption that the RAM size on each CS is maximum of 128M.
See this line:

writel(RASWIDTH_13BITS | CASWIDTH_10BITS | ADDRMUXLEGACY |
        RAMSIZE_128 | BANKALLOCATION | B32NOT16 | B32NOT16 |
        DEEPPD | DDR_SDRAM,&sdrc_base->cs[cs].mcfg);

This discussion should really be taken to u-boot mailing list. Yes, any
additional patches would be good to have..

Where is that list??  I did ask this question in the original
email...

Sorry, I have not seen all the thread. Are you using x-loader? Then your DDR 
configuration happens in x-loader and not in u-boot as it skips it. In that 
case your question should be on x-loader and this is the right list to discuss 
the same.

If you use u-boot for RAM configuration then you should be on NOR flash.

I'm definitely using x-loader (followed by U-Boot).

Where is this set in X-loader?  Is there any guidance for
using the larger DRAM devices?

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to