From: Gary Thomas <gary@mlbassoc.com>
To: "Menon, Nishanth" <nm@ti.com>
Cc: Adam Machalek <adam.machalek@astc-design.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: X-loader / U-Boot query
Date: Thu, 08 Oct 2009 09:17:05 -0600 [thread overview]
Message-ID: <4ACE0271.2060402@mlbassoc.com> (raw)
In-Reply-To: <7A436F7769CA33409C6B44B358BFFF0C012A6FC720@dlee02.ent.ti.com>
On 10/08/2009 09:14 AM, Menon, Nishanth wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@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...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2009-10-08 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 12:58 X-loader / U-Boot query Gary Thomas
2009-10-08 13:52 ` shankarGanesh
2009-10-08 14:46 ` Adam Machalek
2009-10-08 14:48 ` Gary Thomas
2009-10-08 15:14 ` Menon, Nishanth
2009-10-08 15:17 ` Gary Thomas [this message]
2009-10-08 15:19 ` Menon, Nishanth
2009-10-08 15:54 ` Syed Mohammed, Khasim
2009-10-08 16:09 ` Gary Thomas
2009-10-08 16:17 ` Syed Mohammed, Khasim
2009-10-08 16:45 ` Dirk Behme
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=4ACE0271.2060402@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=adam.machalek@astc-design.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.