From: Peter Korsgaard <peter@korsgaard.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] Re: [PATCH v3 1/5] sunxi: a64: Enable FIT Signature
Date: Thu, 14 Dec 2017 09:51:08 +0100 [thread overview]
Message-ID: <87374d4rr7.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAD6G_RSz0K=a7L2usvdn0P7D6GV-DZb-pG3Mssp+ZFmTPRB_5g@mail.gmail.com> (Jagan Teki's message of "Thu, 14 Dec 2017 13:46:52 +0530")
>>>>> "Jagan" == Jagan Teki <jagannadh.teki@gmail.com> writes:
> On Wed, Dec 13, 2017 at 9:38 PM, Peter Korsgaard <peter@korsgaard.com> wrote:
>>>>>>> "Maxime" == Maxime Ripard <maxime.ripard@free-electrons.com> writes:
>>
>> Hi,
>>
>> >> +++ b/arch/arm/mach-sunxi/Kconfig
>> >> @@ -179,6 +179,7 @@ config MACH_SUN50I
>> >> select SUNXI_DRAM_DW_32BIT
>> >> select FIT
>> >> select SPL_LOAD_FIT
>> >> + imply FIT_SIGNATURE
>>
>> > I'm really not sure we should force it by default. How much code size
>> > is it adding?
>>
>> Not only that, enabling FIT_SIGNATURE support disables support for the
>> legacy images (uImage / boot.scr) for security reasons, so it may very
>> well break existing setups.
> Sorry, I didn't get why legacy images will disable with fit? It
> depends how user can go with it, whether he want legacy or fit both
> will work.
Not when you enable CONFIG_FIT_SIGNATURE. That option disables support
for the legacy images.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-12-14 8:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 6:03 [U-Boot] [PATCH v3 1/5] sunxi: a64: Enable FIT Signature Jagan Teki
2017-12-13 6:03 ` [U-Boot] [PATCH v3 2/5] sunxi: arm64: Increase CONFIG_SYS_BOOTM_LEN to 32MB Jagan Teki
2017-12-13 15:34 ` Maxime Ripard
2017-12-13 6:03 ` [U-Boot] [PATCH v3 3/5] docs: Document verified-boot for sunxi a64 Jagan Teki
2017-12-13 15:38 ` Maxime Ripard
2017-12-13 16:11 ` Jagan Teki
2017-12-14 9:07 ` Maxime Ripard
2017-12-13 15:59 ` Quentin Schulz
2017-12-13 16:16 ` Jagan Teki
2017-12-13 16:25 ` Andre Przywara
2017-12-13 16:35 ` Jagan Teki
2017-12-13 16:47 ` Andre Przywara
2017-12-14 1:28 ` Tom Rini
2017-12-13 6:03 ` [U-Boot] [PATCH v3 4/5] docs: README.sunxi: Move sunxi64 documentation Jagan Teki
2017-12-13 15:38 ` Maxime Ripard
2017-12-13 16:21 ` Jagan Teki
2017-12-13 16:12 ` Andre Przywara
2017-12-14 1:30 ` Tom Rini
2017-12-13 6:03 ` [U-Boot] [PATCH v3 5/5] docs: README.sunxi: Move nand documentation Jagan Teki
2017-12-13 15:39 ` [U-Boot] [PATCH v3 1/5] sunxi: a64: Enable FIT Signature Maxime Ripard
2017-12-13 16:08 ` [U-Boot] [linux-sunxi] " Peter Korsgaard
2017-12-14 8:16 ` Jagan Teki
2017-12-14 8:51 ` Peter Korsgaard [this message]
2017-12-14 8:33 ` [U-Boot] " Jagan Teki
2017-12-15 13:41 ` Maxime Ripard
2017-12-15 14:36 ` Andre Przywara
2017-12-15 15:05 ` Jagan Teki
2017-12-15 15:31 ` Andre Przywara
2017-12-15 15:02 ` Jagan Teki
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=87374d4rr7.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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