From: Carlos Santos <casantos@datacom.ind.br>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] Make FIT support really optional
Date: Tue, 7 Jun 2016 21:18:17 -0300 (BRT) [thread overview]
Message-ID: <2013260423.2016960.1465345097365.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20160607223746.09c998f6@free-electrons.com>
> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> To: "Carlos Santos" <casantos@datacom.ind.br>
> Cc: "Tom Rini" <trini@konsulko.com>, u-boot at lists.denx.de
> Sent: Tuesday, June 7, 2016 5:37:46 PM
> Subject: Re: [U-Boot] [PATCH v2] Make FIT support really optional
> Carlos, Tom,
>
> On Sat, 4 Jun 2016 14:39:22 -0300 (BRT), Carlos Santos wrote:
>
>> > So, why? I don't like the idea of making FIT support in mkimage
>> > conditional.
>>
>> If FIT is not to be conditional then what's the purpose of the
>> CONFIG_FIT_SIGNATURE configuration option? Looks like it exists
>> exactly to make FIT support conditional, which seems to be a
>> reasonable approach, since it helps to reduce the size of the boot
>> loader.
>
> CONFIG_FIT_SIGNATURE is I guess optional because it requires OpenSSL at
> *build* time and the U-Boot developers don't want to force everyone to
> have OpenSSL available to build U-Boot.
>
> However, FIT support does not require any special build dependency, so
> probably there's little interest from the U-Boot folks to make it
> optional.
There is already a configuration that makes FIT optional (CONFIG_FIT) but it is partially broken because it does not really remove FIT-related functionality from mkimage. That's the reason why it was not possible to disable FIT in the Buildroot package. My patch aims to fix that defect.
Carlos Santos (Casantos)
DATACOM, P&D
next prev parent reply other threads:[~2016-06-08 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 15:06 [U-Boot] [PATCH 4/4] Make FIT support really optional Carlos Santos
2016-06-03 19:16 ` [U-Boot] [PATCH v2] " Carlos Santos
2016-06-04 12:09 ` Otavio Salvador
2016-06-04 13:06 ` Tom Rini
2016-06-04 17:39 ` Carlos Santos
2016-06-06 11:42 ` Carlos Santos
2016-06-07 20:37 ` Thomas Petazzoni
2016-06-08 0:18 ` Carlos Santos [this message]
2016-06-08 5:47 ` Thomas Petazzoni
2016-06-08 12:17 ` Tom Rini
2016-06-10 1:09 ` Simon Glass
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=2013260423.2016960.1465345097365.JavaMail.zimbra@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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