From: Wolfgang Denk <wd@denx.de>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: Peter Tyser <ptyser@xes-inc.com>,
linuxppc-dev@ozlabs.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 3/3] powerpc: Add support for ram filesystems in FIT uImages
Date: Sun, 03 Jan 2010 10:50:32 +0100 [thread overview]
Message-ID: <20100103095032.8F05AE34A26@gemini.denx.de> (raw)
In-Reply-To: <87wrzzpq8c.fsf@macbook.be.48ers.dk>
Dear Peter,
In message <87wrzzpq8c.fsf@macbook.be.48ers.dk> you wrote:
>
> Wolfgang> Let's make this "uImage.old" (or "uImage.legacy" similar) and
> Wolfgang> "uImage", then.
>
> No, that would break stuff for the existing users. The existing format
> make/file names shouldn't change.
Well, with this argument you can block all progress and freeze all
development to some ancient state.
When the arch/ppc => arch/powerpc conversionm was done, we had similar
issues: the new "powerpc" uImages would not work as the old "ppc"
uImages dis, because you also needed the device tree blob, or you had
to use the cuImage files. Note that then the decision was made to
support the _new_ version as the default, using the default name,
which is IMO the Right Thing to do.
> The FIT images could be called fitimage or uImage.new or something.
I disagree. We want to make this the new default, so let's use the
default name for this, and continue to support he legacy image format
using another name.
Also, your approach does not scale. Assume we come up with an even
more advanced image format in the future - how should we name it then?
"uImage.newer" ? "uImage.verynew" ? "uImage.new2" ?
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
The world is coming to an end -- save your buffers!
next prev parent reply other threads:[~2010-01-03 9:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 1:50 [PATCH v2 0/3] powerpc: Add support for FIT uImages Peter Tyser
2009-12-22 1:50 ` [PATCH v2 1/3] powerpc: Use scripts/mkuboot.sh instead of 'mkimage' Peter Tyser
2009-12-30 22:25 ` Grant Likely
2009-12-22 1:50 ` [PATCH v2 2/3] powerpc: Add support for creating FIT uImages Peter Tyser
2009-12-22 3:48 ` Olof Johansson
2009-12-22 4:50 ` Peter Tyser
2009-12-30 22:57 ` Grant Likely
2010-01-01 14:18 ` Wolfgang Denk
2010-01-03 5:23 ` Grant Likely
2009-12-22 1:50 ` [PATCH v2 3/3] powerpc: Add support for ram filesystems in " Peter Tyser
2009-12-30 23:02 ` Grant Likely
2009-12-30 23:39 ` Peter Tyser
2009-12-31 0:01 ` Grant Likely
2009-12-31 1:10 ` Peter Tyser
2010-01-03 5:08 ` [U-Boot] " Grant Likely
2010-01-03 10:10 ` Wolfgang Denk
2010-01-04 1:07 ` Peter Tyser
2010-01-04 8:27 ` Grant Likely
2009-12-31 8:01 ` Peter Korsgaard
2010-01-01 14:12 ` Wolfgang Denk
2010-01-03 5:18 ` Grant Likely
2010-01-03 10:15 ` Wolfgang Denk
2009-12-31 22:44 ` Wolfgang Denk
2009-12-31 23:10 ` Peter Tyser
2010-01-01 10:44 ` Wolfgang Denk
2010-01-03 5:13 ` Grant Likely
2010-01-03 10:12 ` Wolfgang Denk
2010-01-03 8:06 ` Peter Korsgaard
2010-01-03 9:50 ` Wolfgang Denk [this message]
2010-01-03 14:27 ` Peter Korsgaard
2010-01-04 8:34 ` Grant Likely
2010-01-03 23:52 ` Peter Tyser
2010-01-03 5:10 ` Grant Likely
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=20100103095032.8F05AE34A26@gemini.denx.de \
--to=wd@denx.de \
--cc=jacmet@sunsite.dk \
--cc=linux-kbuild@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ptyser@xes-inc.com \
/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