public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Loïc Minier" <lool@dooz.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] zImage on ARM
Date: Fri, 3 Sep 2010 23:47:53 +0200	[thread overview]
Message-ID: <20100903214753.GA8552@bee.dooz.org> (raw)
In-Reply-To: <20100902224542.48A63153A79@gemini.denx.de>

On Fri, Sep 03, 2010, Wolfgang Denk wrote:
> > I have a client that has asked me to look into loading zImage files
> > instead of uImage for some ARM based boards.
> 
> Why?

 It's the direct output of the kernel build process; typically,
 distributions ship a /boot/zImage-foo which gets converted into an
 uImage and flashed if the bootloader is u-boot.  If that step could be
 skipped, it would make things easier!

> > Anyone familiar with the history of why uImage is the preferred
> > format?  Just trying to learn . . .
> 
> uImage, when done correctly, avoids that you have to add a pre-loader
> (including all of gzip and what else is needed to copy the uncom-
> pressed image to it's final location in RAM) to each and every kernel
> image - which is just a waste of time and resources as we already
> have all that code present in U-Boot.
> 
> Note that the mainline ARM kernel does not make use of this; instead,
> it adds the preloader anyway.  I never understood why.

 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?
 Or should u-boot just gain a new image type for zImage?

-- 
Lo?c Minier

  reply	other threads:[~2010-09-03 21:47 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 [this message]
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
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=20100903214753.GA8552@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