In message <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] Commitment, n.: Commitment can be illustrated by a breakfast of ham and eggs. The chicken was involved, the pig was committed. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
