On 10 December 2013 14:47, Alexey Brodkin wrote:
> On Thu, 2013-11-28 at 13:55 +0400, Alexey Brodkin wrote:
>> On Wed, 2013-11-27 at 18:43 -0700, Simon Glass wrote:
>>
>>
>> > I have a similar patch locally, but it actually does memset() on the
>> > whole structure. Some archs handle this setup di
On Thu, 2013-11-28 at 13:55 +0400, Alexey Brodkin wrote:
> On Wed, 2013-11-27 at 18:43 -0700, Simon Glass wrote:
>
>
> > I have a similar patch locally, but it actually does memset() on the
> > whole structure. Some archs handle this setup differently. For example
> > both ARM and x86 now allocat
On Wed, 2013-11-27 at 18:43 -0700, Simon Glass wrote:
> I have a similar patch locally, but it actually does memset() on the
> whole structure. Some archs handle this setup differently. For example
> both ARM and x86 now allocate it in low level code so there is no need
> for the board_f code to
On 27 November 2013 11:32, Alexey Brodkin wrote:
> If U-Boot build with DEBUG enabled/defined the first call of "debug"
> function (that dumps data to any available console) will happen before
> zeroing of initial "gd" in init call "zero_global_data" in
> "init_sequence_f".
>
> And if stack was no
If U-Boot build with DEBUG enabled/defined the first call of "debug"
function (that dumps data to any available console) will happen before
zeroing of initial "gd" in init call "zero_global_data" in
"init_sequence_f".
And if stack was not filled with zeros chances are high that
"gd->have_console"
5 matches
Mail list logo
