From: "Loïc Minier" <lool@dooz.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] zImage on ARM
Date: Thu, 9 Sep 2010 01:27:53 +0200 [thread overview]
Message-ID: <20100908232753.GA20336@bee.dooz.org> (raw)
In-Reply-To: <20100907230439.14834153798@gemini.denx.de>
On Wed, Sep 08, 2010, Wolfgang Denk wrote:
> zImage does not contain any visible information about what it is,
> when it was build, etc. It is not checksum protected so you cannot
> verify if the image you just downloaded is good enough to erase what
> you have in flash, etc. etc.
These are indeed nice features of uImages (checksums +
build date information); but they are not needed in all use cases for
U-Boot. Distributions are shipping zImage for ARM nowadays and when
shipping zImage files withing packages (.deb for instance), there are
already checksums, file timestamps, public build logs etc. as part of
the distro toolkit.
Also, this means end-user systems need mkimage installed (because
uImage differ slightly across boards). Not a problem for an embedded
developer obviously, but would prefer avoiding this need on an end-user
system.
(Nitpick: if you want an accurate time for the kernel build, them this
should rather be recorded during the upstream linux kernel build rather
than at the time the uImage is created, which could be quite some time
later!)
> > Seems zImage is quite widespread now; would it make sense to allow
> > builing u-boot without that code and rely on the kernel code to unpack?
> Why duplicating the stuff again and again and again?
Well, I'm proposing skipping one copy ;-) the U-Boot one
> > Or should u-boot just gain a new image type for zImage?
> Why not use uImage like we do with other architectures?
> Why is it that ARM always has to try to reinvent the wheels?
Eh, zImage has been around for a while!
I guess it's just that we don't /need/ the couple extra uImage
features, and would rather ship zImage directly.
It would also remove the need for maintaining the table of magic values
for uImage / uInitrd generation; a problem I described recently on
another list:
http://lists.linaro.org/pipermail/linaro-dev/2010-August/000493.html
So we'd be happy if you'd take patches to have U-Boot accept this
"dumber" format.
Cheers,
--
Lo?c Minier
next prev parent reply other threads:[~2010-09-08 23:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 21:43 [U-Boot] zImage on ARM Steve Sakoman
2010-09-02 22:45 ` Paulraj, Sandeep
2010-09-02 22:45 ` Wolfgang Denk
2010-09-03 21:47 ` Loïc Minier
2010-09-07 23:04 ` Wolfgang Denk
2010-09-08 20:23 ` Scott Wood
2010-09-08 20:32 ` Wolfgang Denk
2010-09-08 20:34 ` Scott Wood
2010-09-08 20:43 ` Wolfgang Denk
2010-09-08 21:00 ` Scott Wood
2010-09-09 7:26 ` Wolfgang Denk
2010-09-09 16:28 ` Scott Wood
2010-09-09 17:22 ` Wolfgang Denk
2010-09-09 14:07 ` Lei Wen
2010-09-08 23:27 ` Loïc Minier [this message]
2010-09-09 8:57 ` Wolfgang Denk
2010-09-12 15:07 ` Loïc Minier
2010-09-12 17:37 ` Wolfgang Denk
2010-09-13 4:20 ` Nicolas Pitre
2010-09-13 9:17 ` Wolfgang Denk
2010-09-13 13:37 ` Nicolas Pitre
2010-09-13 21:59 ` Wolfgang Denk
2010-09-14 3:23 ` Nicolas Pitre
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=20100908232753.GA20336@bee.dooz.org \
--to=lool@dooz.org \
--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