All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] tools/mkimage: Print FIT image contents after creation
Date: Sat, 05 Dec 2009 01:14:04 +0100	[thread overview]
Message-ID: <20091205001404.86C643F6E3@gemini.denx.de> (raw)
In-Reply-To: <1259102530-32071-3-git-send-email-ptyser@xes-inc.com>

Dear Peter Tyser,

In message <1259102530-32071-3-git-send-email-ptyser@xes-inc.com> you wrote:
> Previously, there was no indication to the user that a FIT image was
> successfully created after executing mkimage.  For example:
> 
>   $ mkimage -f uImage.its uImage.itb
>   DTC: dts->dtb  on file "uImage.its"
> 
> Adding some additional output after creating a FIT image lets the user
> know exactly what is contained in their image, eg:
> 
>   $ mkimage -f uImage.its uImage.itb
>   DTC: dts->dtb  on file "uImage.its"
>   FIT description: Linux kernel 2.6.32-rc7-00201-g7550d6f-dirty
>   Created:         Tue Nov 24 15:43:01 2009
>    Image 0 (kernel at 1)
>     Description:  Linux Kernel 2.6.32-rc7-00201-g7550d6f-dirty
>     Type:         Kernel Image
>     Compression:  gzip compressed
>     Data Size:    2707311 Bytes = 2643.86 kB = 2.58 MB
>     Architecture: PowerPC
>     OS:           Linux
>     Load Address: 0x00000000
>     Entry Point:  0x00000000
>     Hash algo:    crc32
>     Hash value:   efe0798b
>     Hash algo:    sha1
>     Hash value:   ecafba8c95684f2c8fec67e33c41ec88df1534d7
>    Image 1 (fdt at 1)
>     Description:  Flattened Device Tree blob
>     Type:         Flat Device Tree
>     Compression:  uncompressed
>     Data Size:    12288 Bytes = 12.00 kB = 0.01 MB
>     Architecture: PowerPC
>     Hash algo:    crc32
>     Hash value:   a5cab676
>     Hash algo:    sha1
>     Hash value:   168722b13e305283cfd6603dfe8248cc329adea6
>    Default Configuration: 'config at 1'
>    Configuration 0 (config at 1)
>     Description:  Default Linux kernel
>     Kernel:       kernel at 1
>     FDT:          fdt at 1
> 
> This brings the behavior of creating a FIT image in line with creating a
> standard uImage, which also prints out the uImage contents after
> creation.
> 
> Signed-off-by: Peter Tyser <ptyser@xes-inc.com>
> ---
>  tools/mkimage.c |   51 ++++++++++++++++++++++++++-------------------------
>  1 files changed, 26 insertions(+), 25 deletions(-)

Applied, thanks.

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 at denx.de
Some programming languages manage to  absorb  change,  but  withstand
progress.          -- Epigrams in Programming, ACM SIGPLAN Sept. 1982

  reply	other threads:[~2009-12-05  0:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 22:42 [U-Boot] [PATCH 1/3] tools/mkimage: Assume FDT image type for FIT images Peter Tyser
2009-11-24 22:42 ` [U-Boot] [PATCH 2/3] tools/fit_image.c: Remove unused fit_set_header() Peter Tyser
2009-12-05  0:11   ` Wolfgang Denk
2009-11-24 22:42 ` [U-Boot] [PATCH 3/3] tools/mkimage: Print FIT image contents after creation Peter Tyser
2009-12-05  0:14   ` Wolfgang Denk [this message]
2009-11-25  8:55 ` [U-Boot] [PATCH 1/3] tools/mkimage: Assume FDT image type for FIT images Stefano Babic
2009-12-05  0:13 ` Wolfgang Denk
2009-12-05  0:18   ` Peter Tyser
2009-12-05  0:51     ` 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=20091205001404.86C643F6E3@gemini.denx.de \
    --to=wd@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.