From: Tom Rini <trini@konsulko.com>
To: Yannick Gicquel <yannick.gicquel@iot.bzh>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH v2 4/4] kernel: fitimage: basic support for fitimage signature
Date: Wed, 20 Apr 2016 11:23:46 -0400 [thread overview]
Message-ID: <20160420152346.GF1924@bill-the-cat> (raw)
In-Reply-To: <1461160239-7799-5-git-send-email-yannick.gicquel@iot.bzh>
On Wed, Apr 20, 2016 at 03:50:39PM +0200, Yannick Gicquel wrote:
> This is an initial support of fitImage signature to enable U-Boot verified
> boot. This feature is implemented by adding a signature tag to the
> configuration section of the generated fit-image.its file.
>
> When a UBOOT_SIGN_ENABLE variable is set to "1", the signature procedure is
> activated and performs a second call to mkimage to sign the fitImage file and
> to include the public key in the deployed U-Boot device tree blob. (This
> implementation depends on the use of CONFIG_OF_SEPARATE in U-Boot.)
>
> As the U-Boot device tree blob is appended in the deploy dir, a dependency
> on 'u-boot:do_deploy' is added when the feature is activated.
>
> Signed-off-by: Yannick Gicquel <yannick.gicquel@iot.bzh>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
next prev parent reply other threads:[~2016-04-20 15:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:50 [RFC][PATCH v2 0/4] U-Boot verified boot basic support Yannick Gicquel
2016-04-20 13:50 ` [RFC][PATCH v2 1/4] u-boot: basic support of dtb append for verified boot Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:33 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 19:49 ` [RFC][PATCH v2 " Denys Dmytriyenko
2016-04-20 21:03 ` Tom Rini
2016-04-21 10:25 ` Yannick GICQUEL
2016-04-21 14:06 ` Andreas Oberritter
2016-04-21 19:55 ` Yannick GICQUEL
2016-04-24 12:56 ` Bernhard Reutner-Fischer
2016-04-20 13:50 ` [RFC][PATCH v2 2/4] u-boot: deploy u-boot-nodtb and dtb files Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:34 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 19:51 ` [RFC][PATCH v2 " Denys Dmytriyenko
2016-04-20 13:50 ` [RFC][PATCH v2 3/4] kernel: fitimage: support device tree compiler options Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:34 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 13:50 ` [RFC][PATCH v2 4/4] kernel: fitimage: basic support for fitimage signature Yannick Gicquel
2016-04-20 15:23 ` Tom Rini [this message]
2016-04-20 19:35 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 15:23 ` [RFC][PATCH v2 0/4] U-Boot verified boot basic support Tom Rini
2016-04-20 19:43 ` Denys Dmytriyenko
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=20160420152346.GF1924@bill-the-cat \
--to=trini@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yannick.gicquel@iot.bzh \
/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