From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 13/13] bootm: add initial FIT support
Date: Mon, 18 Jan 2016 08:31:40 +0100 [thread overview]
Message-ID: <20160118073140.GE13058@pengutronix.de> (raw)
In-Reply-To: <87mvs6kg5u.fsf@gmail.com>
On Fri, Jan 15, 2016 at 04:37:17PM +0100, Holger Schurig wrote:
> Sascha Hauer <s.hauer@pengutronix.de> writes:
> Hi,
>
> > +config CMD_BOOTM_FITIMAGE
> > + bool
> > + prompt "FIT image support"
> > + select FITIMAGE
> > + depends on CMD_BOOTM && ARM
> > + help
> > + Support using FIT Images. Have a look at the u-boot source
> > + tree in the "doc/uImage.FIT" folder for more information:
> > + http://git.denx.de/?p=u-boot.git;a=tree;f=doc/uImage.FIT
>
> I know that you've posted a link here, and I even went there.
>
> Still I think it would be better if the abbrev "FIT" get's explained
> or spelled out at least once. Neither this help text nor the commit
> text is really enlightening.
You are right. I rephrased that to:
Support using Flattened Image Tree (FIT) Images. FIT is an image
format introduced by U-Boot. A FIT image contains one or multiple
kernels, device trees and initrds. The FIT image itself is a flattened
device tree binary. Have a look at the u-boot source tree
in the "doc/uImage.FIT" folder for more information:
http://git.denx.de/?p=u-boot.git;a=tree;f=doc/uImage.FIT
Does that sound ok?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-01-18 7:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 15:07 [PATCH v3] " Sascha Hauer
2016-01-15 15:07 ` [PATCH 01/13] ARM: zImage: add missing free() in appended device tree code Sascha Hauer
2016-01-15 15:07 ` [PATCH 02/13] bootm: Do not call uimage_close twice Sascha Hauer
2016-01-15 15:07 ` [PATCH 03/13] bootm: introduce bootm_get_os_size Sascha Hauer
2016-01-15 15:07 ` [PATCH 04/13] bootm: use names instead of numbers for image parts Sascha Hauer
2016-01-15 15:07 ` [PATCH 05/13] ARM: bootm: Use kernel handler to start barebox image Sascha Hauer
2016-01-15 15:07 ` [PATCH 06/13] bootm: Push dryrun to handlers Sascha Hauer
2016-01-15 15:07 ` [PATCH 07/13] bootm: move initrd code together Sascha Hauer
2016-01-15 15:07 ` [PATCH 08/13] bootm: move oftree " Sascha Hauer
2016-01-15 15:07 ` [PATCH 09/13] bootm: Initialize bootm_data defaults in single place Sascha Hauer
2016-01-15 15:07 ` [PATCH 10/13] crypto: add digest_alloc_by_algo() Sascha Hauer
2016-01-15 15:07 ` [PATCH 11/13] crypto: add RSA support Sascha Hauer
2016-01-15 15:07 ` [PATCH 12/13] bootm: make verifying/hashing configurable Sascha Hauer
2016-01-15 15:07 ` [PATCH 13/13] bootm: add initial FIT support Sascha Hauer
2016-01-15 15:37 ` Holger Schurig
2016-01-18 7:31 ` Sascha Hauer [this message]
2016-01-15 15:50 ` [PATCH v3] " Yegor Yefremov
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=20160118073140.GE13058@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.com \
/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