From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] tools/mkimage: Assume FDT image type for FIT images
Date: Wed, 25 Nov 2009 09:55:43 +0100 [thread overview]
Message-ID: <4B0CF10F.6090609@denx.de> (raw)
In-Reply-To: <1259102530-32071-1-git-send-email-ptyser@xes-inc.com>
Peter Tyser wrote:
> When building a Flattened Image Tree (FIT) the image type needs to be
> "flat_dt". Commit 89a4d6b12fd6394898b8a454cbabeaf1cd59bae5 introduced a
> regression which caused the user to need to specify the "-T flat_dt"
> parameter on the command line when building a FIT image. The "-T
> flat_dt" parameter should not be needed and is at odds with the current
> FIT image documentation.
I have found that recent commit 6a590c5f5fd12cdd27f3153522acfac3854590e7
has already fix this issue.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-11-25 8:55 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
2009-11-25 8:55 ` Stefano Babic [this message]
2009-12-05 0:13 ` [U-Boot] [PATCH 1/3] tools/mkimage: Assume FDT image type for FIT images 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=4B0CF10F.6090609@denx.de \
--to=sbabic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox