From 73223f0e1bd0e37925ae1b7f21b51733145571dc Mon Sep 17 00:00:00 2001 From: Simon Glass Date: Mon, 22 Feb 2016 22:55:43 -0700 Subject: Kconfig: Move CONFIG_FIT and related options to Kconfig There are already two FIT options in Kconfig but the CONFIG options are still in the header files. We need to do a proper move to fix this. Move these options to Kconfig and tidy up board configuration: CONFIG_FIT CONFIG_OF_BOARD_SETUP CONFIG_OF_SYSTEM_SETUP CONFIG_FIT_SIGNATURE CONFIG_FIT_BEST_MATCH CONFIG_FIT_VERBOSE CONFIG_OF_STDOUT_VIA_ALIAS CONFIG_RSA Unfortunately the first one is a little complicated. We need to make sure this option is not enabled in SPL by this change. Also this option is enabled automatically in the host builds by defining CONFIG_FIT in the image.h file. To solve this, add a new IMAGE_USE_FIT #define which can be used in files that are built on the host but must also build for U-Boot and SPL. Note: Masahiro's moveconfig.py script is amazing. Signed-off-by: Simon Glass [trini: Add microblaze change, various configs/ re-applies] Signed-off-by: Tom Rini --- README | 39 +++------------------------------------ 1 file changed, 3 insertions(+), 36 deletions(-) (limited to 'README') diff --git a/README b/README index b2eee19773..523941f804 100644 --- a/README +++ b/README @@ -3093,20 +3093,6 @@ CBFS (Coreboot Filesystem) support will set it back to normal. This command currently supports i.MX53 and i.MX6. -- Signing support: - CONFIG_RSA - - This enables the RSA algorithm used for FIT image verification - in U-Boot. See doc/uImage.FIT/signature.txt for more information. - - The Modular Exponentiation algorithm in RSA is implemented using - driver model. So CONFIG_DM needs to be enabled by default for this - library to function. - - The signing part is build into mkimage regardless of this - option. The software based modular exponentiation is built into - mkimage irrespective of this option. - - bootcount support: CONFIG_BOOTCOUNT_LIMIT @@ -3306,33 +3292,14 @@ FIT uImage format: enabled per default for backward compatibility. - FIT image support: - CONFIG_FIT - Enable support for the FIT uImage format. - - CONFIG_FIT_BEST_MATCH - When no configuration is explicitly selected, default to the - one whose fdt's compatibility field best matches that of - U-Boot itself. A match is considered "best" if it matches the - most specific compatibility entry of U-Boot's fdt's root node. - The order of entries in the configuration's fdt is ignored. - - CONFIG_FIT_SIGNATURE - This option enables signature verification of FIT uImages, - using a hash signed and verified using RSA. If - CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive - hashing is available using hardware, RSA library will use it. - See doc/uImage.FIT/signature.txt for more details. - - WARNING: When relying on signed FIT images with required - signature check the legacy image format is default - disabled. If a board need legacy image format support - enable this through CONFIG_IMAGE_FORMAT_LEGACY - CONFIG_FIT_DISABLE_SHA256 Supporting SHA256 hashes has quite an impact on binary size. For constrained systems sha256 hash support can be disabled with this option. + TODO(sjg@chromium.org): Adjust this option to be positive, + and move it to Kconfig + - Standalone program support: CONFIG_STANDALONE_LOAD_ADDR -- cgit v1.2.3