
6 Aug
2008
6 Aug
'08
4:40 p.m.
In message 2C702584-3214-4E3C-8F59-7C46C2F4E8AF@kernel.crashing.org you wrote:
I've been using as follows:
setenv autostart no bootm
<fdt fixups> bootepapr 0 $bootm_fdtaddr
Now I see where your intentions with the autostart are coming from.
Sorry, this is not the way it is supposed to work, and not the way it is documented.
Additionally these seems like the low level functionality needed if we want to move to the "scriptable" bootm were we decouple image loading from the actual boot mechanism.
In terms of splitting bootm into smaller units you are riught. In terms of implementation it's wrong.
I think I will back out the autostart patch because it introduces incorrect and undocumented behaviour.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Commitment, n.: Commitment can be illustrated by a breakfast
of ham and eggs. The chicken was involved, the pig was committed.