On 2/13/19 2:27 PM, Tom Rini wrote: > 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 <a...@ti.com> > > In general, since I suppose the answer to my question is "no", so: > Reviewed-by: Tom Rini <tr...@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! >
Well actually the answer is more a "maybe", I just don't know the right spot. For mach-keystone/config.mk HS we link to the make-magic in mach-omap2/config_secure.mk. I did consider doing the same for this, but putting stuff in mach-omap2, even stuff that is not available on any OMAP platform device seemed wrong. Perhaps we could factor the HS magic out into a top-level makefile at some point. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
