Re: [PATCH v2] tools: binman: pass KEYDIR to FIT entries

Simon Glass <[email protected]>
Newsgroups gmane.comp.boot-loaders.u-boot
Message-ID <CAFLszTgoOWc-5_pNdPRwjzqdqF3Ga5NyEtKY9cibgMoA9NSEbQ@mail.gmail.com>
On 2026-07-09T02:29:00, James Hilliard <[email protected]> wrote:
> tools: binman: pass KEYDIR to FIT entries
>
> U-Boot's Makefile passes KEYDIR to direct mkimage invocations, but
> internal binman FIT builds only receive the generic BINMAN_INDIRS search
> path. Adding KEYDIR to BINMAN_INDIRS treats it as one more input-file
> search path: FIT entries still auto-detect a key directory from all
> include directories, so an explicit KEYDIR may not be the directory that
> gets passed to mkimage. It also makes a key-only directory part of the
> generic blob lookup path.
>
> Forward KEYDIR as a binman entry argument named keydir, matching the
> existing entry-argument mechanism used for BL31, TEE, of-list and other
> U-Boot build inputs. FIT entries use that directory directly for
> mkimage -k when fit,sign or fit,encrypt is enabled, falling back to the
> include-directory autodetection when keydir is not provided.
>
> Signed-off-by: James Hilliard <[email protected]>
>
> Makefile                  |  1 +
>  tools/binman/binman.rst   |  5 +++++
>  tools/binman/etype/fit.py | 28 ++++++++++++++++------------
>  tools/binman/ftest.py     | 40 ++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 62 insertions(+), 12 deletions(-)

Reviewed-by: Simon Glass <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.