From: Daniel Hobi <dhobi@gmx.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC:new multi image format
Date: Mon, 19 Mar 2007 17:16:14 +0100 [thread overview]
Message-ID: <45FEB74E.5020106@gmx.net> (raw)
In-Reply-To: <D87DF9BC-1392-42F1-8642-D3D9D80D646E@kernel.crashing.org>
On 13.03.2007 03:59, Kumar Gala wrote:
> The current multi image format doesn't really provide any information
> about what the images contained inside the multi image are.
>
> [...]
>
> Are other fields useful or should we just duplicate the image_header
> completely?
If the fields of the current image header suffice to describe the images
contained in a multi-image, you can just wrap each sub-image with a
image header. That is, first create a number of (single-image) uImages,
then create a multi-image out of these uImages.
Best Regards,
Daniel
next prev parent reply other threads:[~2007-03-19 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 2:59 [U-Boot-Users] RFC:new multi image format Kumar Gala
2007-03-13 8:25 ` Wolfgang Denk
2007-03-15 7:17 ` Tolunay Orkun
2007-03-22 1:38 ` Kumar Gala
2007-03-15 7:07 ` Tolunay Orkun
2007-03-19 16:16 ` Daniel Hobi [this message]
2007-03-19 18:43 ` Wolfgang Denk
2007-03-19 23:02 ` John Rigby
2007-03-19 23:39 ` Wolfgang Denk
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=45FEB74E.5020106@gmx.net \
--to=dhobi@gmx.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