Dear Grant Erickson,
In message <02a515f3-ccd2-4635-ad38-07de542a4...@gmail.com> you wrote:
>
> That makes sense; however, I have deployed boards in the field for
> which an in-place X-Loader update isn't trivial and for which
> interoperability is key. In light of that, are you willing to accept
On Jan 4, 2012, at 8:14 AM, Tom Rini wrote:
> On 01/04/2012 09:10 AM, Grant Erickson wrote:
>> On Jan 3, 2012, at 6:31 AM, Tom Rini wrote:
>>> On 12/22/2011 12:28 PM, Grant Erickson wrote:
Only attempt to configure and add DRAM at chip select 1 if the board has
configured more than one b
On 01/04/2012 09:10 AM, Grant Erickson wrote:
> On Jan 3, 2012, at 6:31 AM, Tom Rini wrote:
>> On 12/22/2011 12:28 PM, Grant Erickson wrote:
>>> Only attempt to configure and add DRAM at chip select 1 if the board has
>>> configured more than one bank of DRAM.
>>>
>>> This prevents boards that hav
On Jan 3, 2012, at 6:31 AM, Tom Rini wrote:
> On 12/22/2011 12:28 PM, Grant Erickson wrote:
>> Only attempt to configure and add DRAM at chip select 1 if the board has
>> configured more than one bank of DRAM.
>>
>> This prevents boards that have CONFIG_NR_DRAM_BANKS set to 1 from getting an
>>
On 12/22/2011 12:28 PM, Grant Erickson wrote:
> Only attempt to configure and add DRAM at chip select 1 if the board has
> configured more than one bank of DRAM.
>
> This prevents boards that have CONFIG_NR_DRAM_BANKS set to 1 from getting an
> incorrect DRAM size.
>
> Signed-off-by: Grant Eric
Only attempt to configure and add DRAM at chip select 1 if the board has
configured more than one bank of DRAM.
This prevents boards that have CONFIG_NR_DRAM_BANKS set to 1 from getting an
incorrect DRAM size.
Signed-off-by: Grant Erickson
Cc: Tom Rini
---
arch/arm/cpu/armv7/omap3/sdrc.c |
6 matches
Mail list logo
