On Thu, Apr 21, 2016 at 01:24:00PM -0500, Allred, Daniel wrote:
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.
So, with Lokesh's series that lets us read FIT images in SPL from most media forms, we can migrate things like am43xx_evm from non-DM+DT to DM+DT and still support all of the various EVMs that includes and delete the single board configs. We should leverage this as much as possible also for the HS versions.