U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 09/15] defconfig: Add a config for AM43xx secure part
Date: Mon, 30 May 2016 14:02:31 -0400	[thread overview]
Message-ID: <20160530180231.GE7419@bill-the-cat> (raw)
In-Reply-To: <1463703055-17484-10-git-send-email-d-allred@ti.com>

On Thu, May 19, 2016 at 07:10:49PM -0500, Daniel Allred wrote:

> From: Madan Srinivas <madans@ti.com>
> 
> Adds a new defconfig file for the AM43xx secure device.
> This is the same as for the non-secure part, except for:
> 	CONFIG_TI_SECURE_DEVICE option set to 'y'
> 	CONFIG_ISW_ENTRY_ADDR updated for secure images.
> 
> Signed-off-by: Daniel Allred <d-allred@ti.com>
> Signed-off-by: Madan Srinivas <madans@ti.com>
> 
> Reviewed-by: Tom Rini <trini@konsulko.com>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160530/9c7e8de4/attachment.sig>

  reply	other threads:[~2016-05-30 18:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20  0:10 [U-Boot] [PATCH v3 00/15] Support for boot image creation for TI secure devices Daniel Allred
2016-05-20  0:10 ` [U-Boot] [PATCH v3 01/15] doc: Add info on using secure devices from TI Daniel Allred
2016-05-30 18:07   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 02/15] arm: am33xx: Kconfig: Add secure device definitions Daniel Allred
2016-05-30 18:01   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 03/15] arm: Kconfig: Add support for AM43xx SoC specific Kconfig Daniel Allred
2016-05-30 18:01   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 04/15] ti: omap-common: Add Kconfig file for secure device support Daniel Allred
2016-05-30 18:01   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 05/15] ti: omap-common: Add commands for generating secure SPL images Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 06/15] ti: AM43xx: config.mk: Add support for generating secure boot images Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-30 18:02   ` Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 07/15] ti: AM43xx: Use CONFIG options from SOC Kconfig Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 08/15] ti: AM43xx: board: Detect AM43xx HS EVM Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 09/15] defconfig: Add a config for AM43xx secure part Daniel Allred
2016-05-30 18:02   ` Tom Rini [this message]
2016-05-20  0:10 ` [U-Boot] [PATCH v3 10/15] ti_omap5_common: Update SPL start address on secure parts Daniel Allred
2016-05-20 13:02   ` Tom Rini
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 11/15] spl: build: ti: add support for secure boot images Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 12/15] ARM: omap-common: Add device type to CPU string Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 13/15] ARM: omap5: add hooks for cpu/SoC fdt fixups Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 14/15] ARM: omap5: add ft_board_setup for dra7xx/am57xx Daniel Allred
2016-05-30 18:02   ` [U-Boot] [U-Boot, v3, " Tom Rini
2016-05-20  0:10 ` [U-Boot] [PATCH v3 15/15] defconfig: ti: Add configs for OMAP5-class secure parts Daniel Allred
2016-05-30 18:03   ` [U-Boot] [U-Boot, v3, " 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=20160530180231.GE7419@bill-the-cat \
    --to=trini@konsulko.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