public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nitin Garg <nitin.garg@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4] imx: Support i.MX6 High Assurance Boot authentication
Date: Mon, 22 Sep 2014 09:12:33 -0500	[thread overview]
Message-ID: <54202E51.2060102@freescale.com> (raw)
In-Reply-To: <54202D2E.3080404@denx.de>

Hi Stefano,

On 09/22/2014 09:07 AM, Stefano Babic wrote:
> Hi Nitin,
> 
> On 16/09/2014 20:33, Nitin Garg wrote:
>> When CONFIG_SECURE_BOOT is enabled, the signed images
>> like kernel and dtb can be authenticated using iMX6 CAAM.
>> The added command hab_auth_img can be used for HAB
>> authentication of images. The command takes the image
>> DDR location, IVT (Image Vector Table) offset inside
>> image as parameters. Detailed info about signing images
>> can be found in Freescale AppNote AN4581.
>>
>> Signed-off-by: Nitin Garg <nitin.garg@freescale.com>
>>
>> ---
>>
> 
> I wanted to apply it on current tree, but it seems it depends on
> "mx6: clock: Add api to enable pll3". Or better, it seems in your tree
> on top the the patch for pll3. It is not an issue and I solve it myself,
> but can you confim that or do you prefer that I apply this one only
> after the thermal series will be merged ?
> 
> Best regards,
> Stefano Babic
> 
> 

Yes you are correct, in my tree I did HAB patch on top of
temperature sensor patch. Pls resolve it or I can help if needed.
I do not have any preference with ordering of HAB and temperature patch.

Thanks,
Nitin Garg

  reply	other threads:[~2014-09-22 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 18:33 [U-Boot] [PATCH v4] imx: Support i.MX6 High Assurance Boot authentication Nitin Garg
2014-09-22 14:07 ` Stefano Babic
2014-09-22 14:12   ` Nitin Garg [this message]
2014-09-22 14:21 ` Stefano Babic
2014-09-30 13:44 ` Fabio Estevam
2014-09-30 14:46   ` Nitin Garg

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=54202E51.2060102@freescale.com \
    --to=nitin.garg@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