From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [PATCH v3 0/5] rockchip: make it possible to sign the u-boot.itb
Date: Fri, 19 Jun 2020 12:47:53 +0200 [thread overview]
Message-ID: <1771932.GX4JDnMVzI@phil> (raw)
In-Reply-To: <280d8788-b881-35d1-98d2-4ab63fe0f9aa@rock-chips.com>
Hi Kever,
Am Sonntag, 31. Mai 2020, 10:28:45 CEST schrieb Kever Yang:
> This patch set make rk3288 series board build fail. Could you help
> to check again?
the additional patch in v4 adding the ifdef CONFIG_SPL_FIT clamp,
should hopefully fix this
Heiko
> On 2020/5/26 ??6:44, Heiko Stuebner wrote:
> > From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> >
> > This series makes it possible to sign a generated u-boot.itb automatically
> > even if the its-source got created by a generator script.
> >
> > To let the SPL know about the key, the -K option for mkimage points
> > to the dts/dt-spl.dtb which can then get included into the spl binary.
> >
> > Tested on Rockchip PX30 with a TPL -> SPL -> U-Boot.itb bootchain.
> >
> > I've split out the the rsa/crypto fixes into a separate series
> > starting at [0].
> >
> > [0] https://patchwork.ozlabs.org/project/uboot/patch/20200522141937.3523692-1-heiko at sntech.de/
> >
> >
> > changes in v3:
> > - add patch to fix imx make_fit_atf.sh error handling
> > - split out rsa fixes into separate series
> > changes in v2.1:
> > - depend on $(CONFIG_SPL_FIT_SIGNATURE)$(U_BOOT_ITS)
> > instead of only $(CONFIG_SPL_FIT_GENERATOR)
> > changes in v2:
> > - add received reviews
> > - fix commit message typo
> > - add doc snippet explaining CONFIG_SPL_FIT_GENERATOR_KEY_HINT
> >
> > Heiko Stuebner (5):
> > imx: mkimage_fit_atf: Fix FIT image if BL31.bin missing
> > mkimage: fit_image: handle multiple errors when writing signatures
> > spl: fit: enable signing a generated u-boot.itb
> > spl: fit: add Kconfig option to specify key-hint for fit_generator
> > rockchip: make_fit_atf: add signature handling
> >
> > Kconfig | 16 ++++++++
> > Makefile | 11 +++++-
> > arch/arm/mach-imx/mkimage_fit_atf.sh | 4 +-
> > arch/arm/mach-rockchip/make_fit_atf.py | 51 +++++++++++++++++++++++++-
> > doc/uImage.FIT/howto.txt | 13 +++++++
> > tools/image-host.c | 2 +-
> > 6 files changed, 92 insertions(+), 5 deletions(-)
> >
>
>
>
next prev parent reply other threads:[~2020-06-19 10:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 10:44 [PATCH v3 0/5] rockchip: make it possible to sign the u-boot.itb Heiko Stuebner
2020-05-26 10:44 ` [PATCH v3 1/5] imx: mkimage_fit_atf: Fix FIT image if BL31.bin missing Heiko Stuebner
2020-05-26 12:53 ` Peng Fan
2020-05-26 10:44 ` [PATCH v3 2/5] mkimage: fit_image: handle multiple errors when writing signatures Heiko Stuebner
2020-05-31 14:07 ` Simon Glass
2020-06-19 10:47 ` Heiko Stuebner
2020-05-26 10:44 ` [PATCH v3 3/5] spl: fit: enable signing a generated u-boot.itb Heiko Stuebner
2020-05-31 14:07 ` Simon Glass
2020-05-26 10:44 ` [PATCH v3 4/5] spl: fit: add Kconfig option to specify key-hint for fit_generator Heiko Stuebner
2020-05-26 10:44 ` [PATCH v3 5/5] rockchip: make_fit_atf: add signature handling Heiko Stuebner
2020-05-31 14:07 ` Simon Glass
2020-05-31 8:28 ` [PATCH v3 0/5] rockchip: make it possible to sign the u-boot.itb Kever Yang
2020-06-19 10:47 ` Heiko Stuebner [this message]
2020-06-26 1:12 ` 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=1771932.GX4JDnMVzI@phil \
--to=heiko@sntech.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