[U-Boot] [PATCH V2] ARM: mxs: tools: Add mkimage support for MXS bootstream
Marek Vasut
marex at denx.de
Mon Aug 19 21:47:09 CEST 2013
Dear Tom Rini,
> On Tue, Aug 06, 2013 at 04:54:53PM +0200, Marek Vasut wrote:
> > Add mkimage support for generating and verifying MXS bootstream.
> > The implementation here is mostly a glue code between MXSSB v0.4
> > and mkimage, but the long-term goal is to rectify this and merge
> > MXSSB with mkimage more tightly. Once this code is properly in
> > U-Boot, MXSSB shall be deprecated in favor of mkimage-mxsimage
> > support.
> >
> > Note that the mxsimage generator needs libcrypto from OpenSSL, I
> > therefore enabled the libcrypto/libssl unconditionally.
> >
> > MXSSB: http://git.denx.de/?p=mxssb.git;a=summary
> >
> > The code is based on research presented at:
> > http://www.rockbox.org/wiki/SbFileFormat
> >
> > Signed-off-by: Marek Vasut <marex at denx.de>
> > Cc: Tom Rini <trini at ti.com>
> > Cc: Fabio Estevam <fabio.estevam at freescale.com>
> > Cc: Stefano Babic <sbabic at denx.de>
> > Cc: Otavio Salvador <otavio at ossystems.com.br>
> > ---
> >
> > arch/arm/cpu/arm926ejs/mxs/mxsimage.mx23.cfg | 6 +
> > arch/arm/cpu/arm926ejs/mxs/mxsimage.mx28.cfg | 8 +
> > common/image.c | 1 +
> > config.mk | 6 +
> > doc/README.mxsimage | 165 ++
> > include/image.h | 1 +
> > tools/Makefile | 2 +
> > tools/mkimage.c | 2 +
> > tools/mkimage.h | 1 +
> > tools/mxsimage.c | 2312
> > ++++++++++++++++++++++++++ tools/mxsimage.h
> > | 203 +++
> > 11 files changed, 2707 insertions(+)
> > create mode 100644 arch/arm/cpu/arm926ejs/mxs/mxsimage.mx23.cfg
> > create mode 100644 arch/arm/cpu/arm926ejs/mxs/mxsimage.mx28.cfg
> > create mode 100644 doc/README.mxsimage
> > create mode 100644 tools/mxsimage.c
> > create mode 100644 tools/mxsimage.h
> >
> > V2: Remove the time hack fixing timestamp at certain time
> >
> > Enable -lssl and -lcrypto only if CONFIG_MX23/CONFIG_MX28 is set
>
> I think this now breaks non-MX23/28 builds as we still build and try and
> link all of the crypto stuff.
It will, but only if CONFIG_MX23/MX28 is selected, so what's the problem
exactly?
> Please double check this with how Simon
> handled this for FIT signature stuff.
I wonder if we shouldn't just unconditionally link openssl anyway. But that's
for another discussion.
Best regards,
Marek Vasut
More information about the U-Boot
mailing list