On 05/30/2012 10:04 AM, Tom Warren wrote:
> On Tue, May 29, 2012 at 4:47 PM, Stephen Warren wrote:
>> On 05/29/2012 05:19 PM, Tom Warren wrote:
>>> On Tue, May 29, 2012 at 3:12 PM, Stephen Warren
>>> wrote:
On 05/29/2012 03:47 PM, Lucas Stach wrote:
> The RAM configuration is set by the
On Tue, May 29, 2012 at 4:47 PM, Stephen Warren wrote:
> On 05/29/2012 05:19 PM, Tom Warren wrote:
>> On Tue, May 29, 2012 at 3:12 PM, Stephen Warren
>> wrote:
>>> On 05/29/2012 03:47 PM, Lucas Stach wrote:
The RAM configuration is set by the bootrom to values specified by the BCT.
To
On 05/29/2012 05:19 PM, Tom Warren wrote:
> On Tue, May 29, 2012 at 3:12 PM, Stephen Warren wrote:
>> On 05/29/2012 03:47 PM, Lucas Stach wrote:
>>> The RAM configuration is set by the bootrom to values specified by the BCT.
>>> To query the available RAM size of a board we can easily read back th
On Tue, May 29, 2012 at 3:12 PM, Stephen Warren wrote:
> On 05/29/2012 03:47 PM, Lucas Stach wrote:
>> The RAM configuration is set by the bootrom to values specified by the BCT.
>> To query the available RAM size of a board we can easily read back those
>> values instead of using the hardcoded OD
On 05/29/2012 03:47 PM, Lucas Stach wrote:
> The RAM configuration is set by the bootrom to values specified by the BCT.
> To query the available RAM size of a board we can easily read back those
> values instead of using the hardcoded ODMdata. This allows for a single
> u-boot image on similar boa
The RAM configuration is set by the bootrom to values specified by the BCT.
To query the available RAM size of a board we can easily read back those
values instead of using the hardcoded ODMdata. This allows for a single
u-boot image on similar boards with different amount of RAM.
Note that the re
6 matches
Mail list logo