From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] fsl_sec : Add hardware accelerated SHA256 and SHA1
Date: Thu, 25 Sep 2014 08:30:42 -0700 [thread overview]
Message-ID: <54243522.5070708@freescale.com> (raw)
In-Reply-To: <1410407925-25437-1-git-send-email-ruchika.gupta@freescale.com>
On 09/10/2014 08:58 PM, Ruchika Gupta wrote:
> SHA-256 and SHA-1 accelerated using SEC hardware in Freescale SoC's
> The driver for SEC (CAAM) IP is based on linux drivers/crypto/caam.
>
> Signed-off-by: Ruchika Gupta <ruchika.gupta@freescale.com>
> CC: York Sun <yorksun@freescale.com>
> ---
> The patch series is dependent on
> https://patchwork.ozlabs.org/patch/387174/
> https://patchwork.ozlabs.org/patch/387175/
Ruchika,
This patch increases the image size and causes a problem for these boards,
kmcoge4 kmlion1 P1010RDB-PB_36BIT_SPIFLASH_SECBOOT
Please check.
York
prev parent reply other threads:[~2014-09-25 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 3:58 [U-Boot] [PATCH 1/2] fsl_sec : Add hardware accelerated SHA256 and SHA1 Ruchika Gupta
2014-09-11 3:58 ` [U-Boot] [PATCH 2/2] mpc85xx: configs - Add hash command in freescale platforms Ruchika Gupta
2014-09-25 15:30 ` York Sun
2014-09-29 5:49 ` Ruchika Gupta
2014-09-25 15:30 ` York Sun [this message]
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=54243522.5070708@freescale.com \
--to=yorksun@freescale.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