Re: [U-Boot] [PATCH 1/1] arm: mach-omap2: Fix secure file generation

2017-01-09 Thread Tom Rini
On Fri, Jan 06, 2017 at 04:20:02PM -0600, Andrew F. Davis wrote: > When TI_SECURE_DEV_PKG is not defined we warn that the file '*_HS' was > not generated but generate an unsigned one anyway, first fix this > warning to say that it was generated but not secured. > > When the user then exports

[U-Boot] [PATCH 1/1] arm: mach-omap2: Fix secure file generation

2017-01-06 Thread Andrew F. Davis
When TI_SECURE_DEV_PKG is not defined we warn that the file '*_HS' was not generated but generate an unsigned one anyway, first fix this warning to say that it was generated but not secured. When the user then exports TI_SECURE_DEV_PKG after getting this warning, and tries to re-build, 'make'

Re: [U-Boot] [PATCH 1/1] arm: mach-omap2: Fix secure file generation

2016-12-08 Thread Tom Rini
On Thu, Dec 08, 2016 at 04:48:07PM -0600, Andrew F. Davis wrote: > When TI_SECURE_DEV_PKG is not defined we warn that the file '*_HS' was > not generated but generate an unsigned one anyway. When TI_SECURE_DEV_PKG > is exported and the user re-builds, make will detect this file as > unchangedand

[U-Boot] [PATCH 1/1] arm: mach-omap2: Fix secure file generation

2016-12-08 Thread Andrew F. Davis
When TI_SECURE_DEV_PKG is not defined we warn that the file '*_HS' was not generated but generate an unsigned one anyway. When TI_SECURE_DEV_PKG is exported and the user re-builds, make will detect this file as unchangedand and so assume it does not need to be re-generated. This causes it to pack