From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] ARM: mxs: tools: Add mkimage support for MXS bootstream
Date: Mon, 19 Aug 2013 21:47:09 +0200 [thread overview]
Message-ID: <201308192147.09842.marex@denx.de> (raw)
In-Reply-To: <20130819143132.GD1311@bill-the-cat>
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@denx.de>
> > Cc: Tom Rini <trini@ti.com>
> > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > Cc: Stefano Babic <sbabic@denx.de>
> > Cc: Otavio Salvador <otavio@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
next prev parent reply other threads:[~2013-08-19 19:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 14:54 [U-Boot] [PATCH V2] ARM: mxs: tools: Add mkimage support for MXS bootstream Marek Vasut
2013-08-07 13:50 ` [U-Boot] [PATCH V3] " Marek Vasut
2013-08-19 14:31 ` [U-Boot] [PATCH V2] " Tom Rini
2013-08-19 19:47 ` Marek Vasut [this message]
2013-08-19 19:52 ` Tom Rini
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=201308192147.09842.marex@denx.de \
--to=marex@denx.de \
--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