On Tue, Sep 2, 2014 at 10:46 PM, Simon Glass sjg@chromium.org wrote:
On 2 September 2014 18:44, Otavio Salvador otavio@ossystems.com.br wrote:
On Tue, Sep 2, 2014 at 8:14 PM, Simon Glass sjg@chromium.org wrote:
On 2 September 2014 15:44, Otavio Salvador otavio@ossystems.com.br wrote:
On Tue, Sep 2, 2014 at 4:19 PM, Simon Glass sjg@chromium.org wrote: ...
We are using tools-only as part of the Debian packaging, what we are trying to build is a usable generic version of mkimage (and potentially other tools in the future) which can be placed in a generic u-boot-tools package which is separate from the u-boot package(s) which contain(s) u-boot binaries.
mkimage has additional support for verified/secure boot, but only if enabled at build time. It is enabled for sandbox. So if you want full functionality you should use that build.
However there are exceptions for it. For example MX28 has special mxsimage support when it is in use.
Yes, I see the '#ifdef CONFIG_MXS' at the top of tools/mksimage.c. That seem wrong to me - do you know the reason for it?
This is to avoid linking with SSL library[1].
However now we have FIT signature I think we can enable it and drop the MXS special usage.
Do you agree?
I agree (not sure about others). For sandbox we have SSL anyway so it should be fine.
I will wait Marek to comment here and if he agrees I prepare a patch for it. Marek?