[U-Boot-Users] bootm change for standalone images

[Wolfgang Denk]

In message <1091121391.19389.33.camel at mud> you wrote:
>
> Well I may just do (1), but I wanted to make it easier for the next poor
> soul that had the same issue. It is not obvious at all that RTEMS would
> work for more than just RTEMS.

Well, it will work for anything which has the same call interface.

> The other thing with names is that standalone sure doesn't standalone
> when it uses U-Boot to do console IO for it. So when I was looking at

"standalone" is intended to mean "runs without  OS".  You  just  have
special  requirements  which don;t fit in the implemented model. [You
could work around these, though. For example you  could  implement  a
"real"  U-Boot  standalone  proram,  which first disables interrupts,
then installs it's own exception vector table, and then goes on doing
whatever it likes to do.]

> the code and doing mkimage I saw the choices and though well my
> code wants to standalone, so the standalone image sounds good.
> Sure the README describes standalone very well, but it doesn't help
> when it seems to go against the dictionary definition of the word.

You are expected to read the documentation. It says: "runnable in the
environment provided by U-Boot" and "continue to work in U-Boot after
return from the Standalone Program". 

> So I don't want to push for changing names around, but I hope you at
> least understand my confusion.

Maybe you can suggest a better description of  "Standalone  Programs"
that what's give in the README to avoid confusion like uyours?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
This is a story about sex and drugs and Music with Rocks In.  Well...
...one out of three ain't bad.  Actually, it's only thirty-three per-
cent, but it could be worse.          - Terry Pratchett, _Soul Music_