X-Git-Url: http://review.tizen.org/git/?a=blobdiff_plain;f=Kconfig;fp=Kconfig;h=bb80adacf45f00c4ee525e5239edf376a141b0e6;hb=711391131c84398d1b8256ab5a8cfa2969ad57c7;hp=8e773b8a865e4018e54663d57b4bbd39382a89ea;hpb=80b51b5aa91b75d83323fd1fdd253d5f67621784;p=platform%2Fkernel%2Fu-boot.git

diff --git a/Kconfig b/Kconfig
index 8e773b8..bb80ada 100644
--- a/Kconfig
+++ b/Kconfig
@@ -145,6 +145,7 @@ menu "Boot images"
 config FIT
 	bool "Support Flattened Image Tree"
 	select MD5
+	select SHA1
 	help
 	  This option allows you to boot the new uImage structure,
 	  Flattened Image Tree.  FIT is formally a FDT, which can include
@@ -157,6 +158,20 @@ config FIT
 
 if FIT
 
+config FIT_ENABLE_SHA256_SUPPORT
+	bool "Support SHA256 checksum of FIT image contents"
+	select SHA256
+	default y
+	help
+	  Enable this to support SHA256 checksum of FIT image contents. A
+	  SHA256 checksum is a 256-bit (32-byte) hash value used to check that
+	  the image contents have not been corrupted. SHA256 is recommended
+	  for use in secure applications since (as at 2016) there is no known
+	  feasible attack that could produce a 'collision' with differing
+	  input data. Use this for the highest security. Note that only the
+	  SHA256 variant is supported: SHA512 and others are not currently
+	  supported in U-Boot.
+
 config FIT_SIGNATURE
 	bool "Enable signature verification of FIT uImages"
 	depends on DM
@@ -205,6 +220,8 @@ config FIT_IMAGE_POST_PROCESS
 	  injected into the FIT creation (i.e. the blobs would have been pre-
 	  processed before being added to the FIT image).
 
+if SPL
+
 config SPL_FIT
 	bool "Support Flattened Image Tree within SPL"
 	depends on SPL
@@ -259,6 +276,8 @@ config SPL_FIT_GENERATOR
 	  passed a list of supported device tree file stub names to
 	  include in the generated image.
 
+endif # SPL
+
 endif # FIT
 
 config OF_BOARD_SETUP