In message <[EMAIL PROTECTED]> you wrote:
>
> There is intent and what the old code did. My feeling is that
> 'autostart = no' means to load the images but not actually jump to the
> new image.
Correct. To be a bit more specific, "load" here means to load the
kernel image to RAM (ove
On Aug 6, 2008, at 3:33 AM, Wolfgang Denk wrote:
> Dear Bartek,
>
> in message <[EMAIL PROTECTED]> you wrote:
>>
>> The test you're referring to was introduced by commit
>> 75fa002c47171b73fb4c1f2c2fe4d6391c136276 "[new uImage] Respect
>> autostart
>> setting in linux bootm" by Kumar -- he shou
Dear Bartek,
in message <[EMAIL PROTECTED]> you wrote:
>
> The test you're referring to was introduced by commit
> 75fa002c47171b73fb4c1f2c2fe4d6391c136276 "[new uImage] Respect autostart
> setting in linux bootm" by Kumar -- he should be better able to explain
> the details.
Thanks - and sorry f
Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
>> Its useful to know where the device tree is if we have set 'autostart'
>> to 'no. We come back to the prompt after a boot command and we can
>> than post process the device tree but we need to know where it was put
>> report this
In message <[EMAIL PROTECTED]> you wrote:
> Its useful to know where the device tree is if we have set 'autostart'
> to 'no. We come back to the prompt after a boot command and we can
> than post process the device tree but we need to know where it was put
> report this back via the env variable '
Its useful to know where the device tree is if we have set 'autostart'
to 'no. We come back to the prompt after a boot command and we can
than post process the device tree but we need to know where it was put
report this back via the env variable 'bootm_fdtaddr'.
Signed-off-by: Kumar Gala <[EMAIL
