From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] socfpga: Add a signing tool that automatically signs the preloader.
Date: Thu, 20 Feb 2014 08:40:40 -0500 [thread overview]
Message-ID: <20140220134040.GC19081@bill-the-cat> (raw)
In-Reply-To: <20140220112323.C8D62380CEA@gemini.denx.de>
On Thu, Feb 20, 2014 at 12:23:22PM +0100, Wolfgang Denk wrote:
> Dear Charles,
>
> In message <201402201358.19495.manningc2@actrix.gen.nz> you wrote:
> >
> > I looked at doing a mkimage integration, but is this really the way to go in
> > all cases?
>
> ...only where it fits, of course.
>
> > The signed image does not really apply a header as such. It mashes in
> > a "header" at position 0x40 and then appends a checksum at the end, then pads
> > the file out to 64k.
> >
> > The final file is:
> > * 64 bytes of executable (interrupt vector table)
> > * "header"
> > * more code
> > *crc32
> > *padding with 0x00 to 64k.
>
> Sounds exactly as if you were making an image, so yes, mkimage fits.
Right. This is like the omapimage case or similar where we take input,
beat it around and add stuff, then have what the HW wants, but not a
file we can further query with mkimage, and that's fine.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140220/20449294/attachment.pgp>
next prev parent reply other threads:[~2014-02-20 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 23:01 [U-Boot] [PATCH] socfpga: Add a signing tool that automatically signs the preloader Charles Manning
2014-02-20 0:32 ` Tom Rini
2014-02-20 0:58 ` Charles Manning
2014-02-20 11:23 ` Wolfgang Denk
2014-02-20 13:40 ` Tom Rini [this message]
2014-02-22 17:26 ` Gerhard Sittig
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=20140220134040.GC19081@bill-the-cat \
--to=trini@ti.com \
--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