From: Allred, Daniel <d-allred@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 09/16] defconfig: Add configs for AM43xx secure parts
Date: Thu, 21 Apr 2016 13:24:00 -0500 [thread overview]
Message-ID: <57191AC0.3080309@ti.com> (raw)
In-Reply-To: <20160421134012.GC3732@bill-the-cat>
On 4/21/2016 8:40 AM, Tom Rini wrote:
> On Fri, Apr 15, 2016 at 03:28:07PM +0530, Lokesh Vutla wrote:
>>
>>
>> On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote:
>>> From: Madan Srinivas <madans@ti.com>
>>>
>>> Adds new defconfig files for AM43xx secure devices.
>>> These are the same as the non-secure parts, 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>
>>> ---
>>> configs/am43xx_hs_evm_defconfig | 12 ++++++++++++
>>> configs/am43xx_hs_evm_ethboot_defconfig | 11 +++++++++++
>>> configs/am43xx_hs_evm_qspiboot_defconfig | 10 ++++++++++
>>> configs/am43xx_hs_evm_rtconly_defconfig | 12 ++++++++++++
>>
>> You do not need this defconfig. Also now only DT enabled configs are
>> accepted. Ill let Tom to comment here.
>
> Yes, just like was done for the dra7xa/am57xx HS parts, we need to be
> doing DM+DT here too.
>
So I understand to not create any new defconfigs that are not DM+DT, but
what happens to these old ones? Are they deprecated? Or does someone
need to patch/convert them?
I guess I'll just simplify this to make a single am437x_hs_evm_defconfig
that mirrors the am437x_gp_evm_defconfig.
Daniel
next prev parent reply other threads:[~2016-04-21 18:24 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 23:37 [U-Boot] [PATCH 00/16] Support for boot image creation for TI secure devices Daniel Allred
2016-04-11 23:37 ` [U-Boot] [PATCH 01/16] doc: Add info on using secure devices from TI Daniel Allred
2016-04-15 9:47 ` Lokesh Vutla
2016-04-19 15:21 ` Andreas Dannenberg
2016-04-21 13:38 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 02/16] arm: am33xx: Kconfig: Add secure device definitions Daniel Allred
2016-04-15 9:47 ` Lokesh Vutla
2016-04-19 15:13 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 03/16] arm: Kconfig: Add support for AM43xx SoC specific Kconfig Daniel Allred
2016-04-15 9:48 ` Lokesh Vutla
2016-04-15 10:57 ` Lokesh Vutla
2016-04-18 21:03 ` Andreas Dannenberg
2016-04-18 23:04 ` Andreas Dannenberg
2016-04-11 23:37 ` [U-Boot] [PATCH 04/16] ti: omap-common: Add Kconfig file for secure device support Daniel Allred
2016-04-15 9:48 ` Lokesh Vutla
2016-04-20 22:48 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 05/16] ti: omap-common: Add commands for generating secure SPL images Daniel Allred
2016-04-15 9:48 ` Lokesh Vutla
2016-04-20 22:47 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 06/16] ti: AM43xx: config.mk: Add support for generating secure boot images Daniel Allred
2016-04-15 9:49 ` Lokesh Vutla
2016-04-19 15:12 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 07/16] ti: AM43xx: Use CONFIG options from SOC Kconfig Daniel Allred
2016-04-15 9:54 ` Lokesh Vutla
2016-04-19 15:10 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 08/16] ti: AM43xx: board: Detect AM43xx HS EVM Daniel Allred
2016-04-15 9:55 ` Lokesh Vutla
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 09/16] defconfig: Add configs for AM43xx secure parts Daniel Allred
2016-04-15 9:58 ` Lokesh Vutla
2016-04-21 13:40 ` Tom Rini
2016-04-21 18:24 ` Allred, Daniel [this message]
2016-04-21 19:04 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 10/16] ti_omap5_common: Update SPL start address on " Daniel Allred
2016-04-15 9:58 ` Lokesh Vutla
2016-04-20 22:50 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 11/16] spl: build: ti: add support for secure boot images Daniel Allred
2016-04-15 9:59 ` Lokesh Vutla
2016-04-21 13:39 ` Tom Rini
2016-04-21 17:27 ` Andreas Dannenberg
2016-04-11 23:37 ` [U-Boot] [PATCH 12/16] ARM: omap4/5: Add device type to CPU string Daniel Allred
2016-04-15 9:59 ` Lokesh Vutla
2016-04-19 16:26 ` Andreas Dannenberg
2016-04-21 17:55 ` Andreas Dannenberg
2016-04-21 18:01 ` Allred, Daniel
2016-04-21 18:59 ` Andreas Dannenberg
2016-04-21 20:27 ` Tom Rini
2016-04-21 22:56 ` Andreas Dannenberg
2016-04-21 23:38 ` Tom Rini
2016-04-22 15:50 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 13/16] ARM: omap5: add hooks for cpu/SoC fdt fixups Daniel Allred
2016-04-15 10:03 ` Lokesh Vutla
2016-04-20 22:53 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 14/16] ARM: omap5: add ft_board_setup for dra7xx/am57xx Daniel Allred
2016-04-15 10:03 ` Lokesh Vutla
2016-04-20 22:55 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 15/16] ARM: omap5: Add config for board/cpu fdt fixups Daniel Allred
2016-04-15 10:05 ` Lokesh Vutla
2016-04-20 22:55 ` Andreas Dannenberg
2016-04-21 13:39 ` Tom Rini
2016-04-11 23:37 ` [U-Boot] [PATCH 16/16] defconfig: ti: Add configs for OMAP5-class secure parts Daniel Allred
2016-04-15 10:05 ` Lokesh Vutla
2016-04-20 22:57 ` Andreas Dannenberg
2016-04-21 13:40 ` 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=57191AC0.3080309@ti.com \
--to=d-allred@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