not sure if i'm misreading this, but in the top-level Kconfig file,
i can see how one selects support for FIT images:
config FIT
bool "Support Flattened Image Tree"
select MD5
help
This option allows you to boot the new uImage structure,
Flattened Image Tree. FIT is formally a FDT, which can include
images of various types (kernel, FDT blob, ramdisk, etc.)
in a single blob. To boot this new uImage structure,
pass the address of the blob to the "bootm" command.
FIT is very flexible, supporting compression, multiple images,
multiple configurations, verification through hashing and also
verified boot (secure boot using RSA).
if FIT
config FIT_SIGNATURE
bool "Enable signature verification of FIT uImages"
... etc etc ..., so far, so good.
but in the tools/ directory, there's this in the Makefile:
hostprogs-y += dumpimage mkimage
hostprogs-$(CONFIG_FIT_SIGNATURE) += fit_info fit_check_sign
that seems to make sense, the host progs dumpimage and mkimage will be
built regardless of whether or not FIT support is selected, but
further down:
# common objs for dumpimage and mkimage
dumpimage-mkimage-objs := aisimage.o \
atmelimage.o \
$(FIT_SIG_OBJS-y) \
common/bootm.o \
lib/crc32.o \
default_image.o \
lib/fdtdec_common.o \
lib/fdtdec.o \
fit_common.o \
fit_image.o \
common/image-fit.o \
... snip ...
isn't this adding at least a few FIT-related routines to those
hostprogs, regardless of whether FIT support is selected? can someone
clarify this?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
