From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/7] arm: mach-k3: Add secure device build support
Date: Wed, 13 Feb 2019 15:27:20 -0500 [thread overview]
Message-ID: <20190213202720.GX21737@bill-the-cat> (raw)
In-Reply-To: <20190213183712.7087-6-afd@ti.com>
On Wed, Feb 13, 2019 at 12:37:10PM -0600, Andrew F. Davis wrote:
> K3 HS devices require signed binaries for boot, use the SECDEV tools
> to sign the boot artifacts during build.
>
> Signed-off-by: Andrew F. Davis <afd@ti.com>
In general, since I suppose the answer to my question is "no", so:
Reviewed-by: Tom Rini <trini@konsulko.com>
But it feels like we're copying a lot of make-magic around that we have
for other hs devices. Can we find a common place for it for all TI
platforms? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190213/43613b00/attachment.sig>
next prev parent reply other threads:[~2019-02-13 20:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 18:37 [U-Boot] [PATCH 0/7] AM65x HS device support Andrew F. Davis
2019-02-13 18:37 ` [U-Boot] [PATCH 1/7] arm: K3: Avoid use of MCU_PSRAM0 before SYSFW is loaded Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 21:16 ` Andrew F. Davis
2019-02-14 3:32 ` Lokesh Vutla
2019-02-14 21:51 ` Andrew F. Davis
2019-02-18 4:40 ` Lokesh Vutla
2019-02-13 18:37 ` [U-Boot] [PATCH 2/7] firmware: ti_sci: Add support for firewall management Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-14 3:43 ` Lokesh Vutla
2019-02-13 18:37 ` [U-Boot] [PATCH 3/7] firmware: ti_sci: Modify auth_boot TI-SCI API to match new version Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 18:37 ` [U-Boot] [PATCH 4/7] arm: mach-k3: Add secure device support Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 18:37 ` [U-Boot] [PATCH 5/7] arm: mach-k3: Add secure device build support Andrew F. Davis
2019-02-13 20:27 ` Tom Rini [this message]
2019-02-13 21:20 ` Andrew F. Davis
2019-02-14 3:46 ` Lokesh Vutla
2019-02-14 22:55 ` Andrew F. Davis
2019-02-15 12:13 ` Lokesh Vutla
2019-02-16 22:18 ` Tom Rini
2019-02-18 13:05 ` Andrew F. Davis
2019-02-13 18:37 ` [U-Boot] [PATCH 6/7] configs: Add a config for AM65x High Security EVM Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 18:37 ` [U-Boot] [PATCH 7/7] doc: Update info on using K3 secure devices Andrew F. Davis
2019-02-13 20:27 ` Tom Rini
2019-02-13 21:12 ` [U-Boot] [PATCH 0/7] AM65x HS device support Andreas Dannenberg
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=20190213202720.GX21737@bill-the-cat \
--to=trini@konsulko.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