From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, 1/5] arch/powerpc/cpu/mpc8xxx: PAMU driver support
Date: Mon, 19 Aug 2013 16:07:50 -0700 [thread overview]
Message-ID: <5212A546.1010104@freescale.com> (raw)
In-Reply-To: <1364467595-15539-2-git-send-email-ruchika.gupta@freescale.com>
On 03/28/2013 03:46 AM, Ruchika Gupta wrote:
> PAMU driver basic support for usage in Secure Boot.
> In secure boot PAMU is not in bypass mode. Hence to use
> any peripheral (SEC Job ring in our case), PAMU has to be
> configured.
>
> The Header file fsl_pamu.h and few functions in driver have been derived
> from Freescale Libos.
>
> Signed-off-by: Kuldip Giroh <kuldip.giroh@freescale.com>
> Signed-off-by: Ruchika Gupta <ruchika.gupta@freescale.com>
>
>
Ruchika and Kuldip,
Please update your patches for this series. They were first sent on
March 28, 2013.
York
next prev parent reply other threads:[~2013-08-19 23:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 10:46 [U-Boot] [PATCH 0/5] FSL SECURE BOOT: Add support for next level image validation Ruchika Gupta
2013-03-28 10:46 ` [U-Boot] [PATCH 1/5] arch/powerpc/cpu/mpc8xxx: PAMU driver support Ruchika Gupta
2013-05-22 19:47 ` Andy Fleming
2013-08-19 23:07 ` York Sun [this message]
2013-03-28 10:46 ` [U-Boot] [PATCH 2/5] powerpc/pamu : PAMU configuration for accessing SEC block Ruchika Gupta
2013-03-28 10:46 ` [U-Boot] [PATCH 3/5] drivers/sec : Freescale SEC driver Ruchika Gupta
2013-03-28 10:46 ` [U-Boot] [PATCH 4/5] FSL SEC Driver : Add support for descriptor creation Ruchika Gupta
2013-03-28 10:46 ` [U-Boot] [PATCH 5/5] Added command for validation of images in case of secure boot Ruchika Gupta
2013-03-28 14:52 ` [U-Boot] [PATCH 0/5] FSL SECURE BOOT: Add support for next level image validation Otavio Salvador
2013-03-29 4:43 ` Gupta Ruchika-R66431
2013-03-29 22:37 ` Kim Phillips
2013-03-30 5:01 ` Gupta Ruchika-R66431
2013-04-09 10:11 ` Gupta Ruchika-R66431
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=5212A546.1010104@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.