Maintaining a secure and non-secure defconfig is a PITA. Having discussed
an observed bug with the non-secure boot-path with Fabio and undertaken to
ensure both upstream and NXP BSP kernels would work - this patchset does
two things.

1. Switches on CONFIG_ARMV7_BOOT_SEC_DEFAULT for warp7_defconfig
2. Removes warp7_secure_defconfig in its entirety

I have an upcoming set of patches that uses the secure defconfig which I've
already verified can simply be merged into mainline WaRP7 as-is so, in this
context there appears to be no justification for keeping separate
configuration files.

Fix the bug and zap the fat !

Bryan O'Donoghue (2):
  warp7: defconfig: Fix CAAM on boot with tip-of-tree
  warp7: secure_defconfig: Remove secure_defconfig

 configs/warp7_defconfig        |  1 +
 configs/warp7_secure_defconfig | 42 ------------------------------------------
 2 files changed, 1 insertion(+), 42 deletions(-)
 delete mode 100644 configs/warp7_secure_defconfig

-- 
2.7.4

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot

Reply via email to