From: Andrew May <acmay@acmay.homeip.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bootm change for standalone images
Date: Thu, 29 Jul 2004 10:16:31 -0700 [thread overview]
Message-ID: <1091121391.19389.33.camel@mud> (raw)
In-Reply-To: <20040728212212.EB885C109F@atlas.denx.de>
On Wed, 2004-07-28 at 14:22, Wolfgang Denk wrote:
> In message <1091044779.17855.13.camel@mud> you wrote:
> To avoid duplicating code or to use misleading names I see two simple
> options: (1) just use "-O RTEMS" when building your images and gnash
> your teeth when you see "RTEMS" printed instead of
> "your_custom_code_without_a_proper_name", or (2) give your code a
> name which we can add as new OS type, and let's use the RTEMS booter
> for your new "OS", too.
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.
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
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.
So I don't want to push for changing names around, but I hope you at
least understand my confusion.
next prev parent reply other threads:[~2004-07-29 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 1:21 [U-Boot-Users] bootm change for standalone images Andrew May
2004-07-27 22:05 ` Wolfgang Denk
2004-07-27 22:31 ` Andrew May
2004-07-28 8:57 ` Wolfgang Denk
2004-07-28 19:59 ` Andrew May
2004-07-28 21:22 ` Wolfgang Denk
2004-07-29 17:16 ` Andrew May [this message]
2004-07-29 17:29 ` Wolfgang Denk
2004-07-29 18:00 ` Andrew May
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091121391.19389.33.camel@mud \
--to=acmay@acmay.homeip.net \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox