On 15 May 2017 at 10:17, Tom Rini trini@konsulko.com wrote:
We rename CONFIG_FIT_DISABLE_SHA256 to CONFIG_FIT_ENABLE_SHA256_SUPPORT which is enabled by default and now a positive option. Convert the handful of boards that were disabling it before to save space.
Cc: Dirk Eibach eibach@gdsys.de Cc: Lukasz Dalek luk0104@gmail.com Signed-off-by: Tom Rini trini@konsulko.com Reviewed-by: Simon Glass sjg@chromium.org
Changes in v4:
- Fix HOST_CC side of changes to include/image.h so that the host tools will continue to have SHA256 support.
Kconfig | 13 +++++++++++++ README | 9 --------- configs/dlvision-10g_defconfig | 1 + configs/dlvision_defconfig | 1 + configs/h2200_defconfig | 1 + configs/io_defconfig | 1 + configs/iocon_defconfig | 1 + configs/neo_defconfig | 1 + include/configs/dlvision-10g.h | 3 --- include/configs/dlvision.h | 3 --- include/configs/h2200.h | 1 - include/configs/io.h | 3 --- include/configs/iocon.h | 3 --- include/configs/neo.h | 3 --- include/image.h | 16 ++++++---------- scripts/config_whitelist.txt | 1 - 16 files changed, 25 insertions(+), 36 deletions(-)
Reviewed-by: Simon Glass sjg@chromium.org