From: Andrew Davis <afd@ti.com>
To: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
<u-boot@lists.denx.de>
Cc: Andrew Davis <afd@ti.com>
Subject: [PATCH 3/4] boot: Kconfig: Disable non-FIT loading for TI secure devices
Date: Wed, 4 May 2022 15:52:27 -0500 [thread overview]
Message-ID: <20220504205228.5153-3-afd@ti.com> (raw)
In-Reply-To: <20220504205228.5153-1-afd@ti.com>
Non-FIT image loading support should be disabled for TI secure
devices as the image handlers for those image types do not follow
our secure boot checks.
Signed-off-by: Andrew Davis <afd@ti.com>
---
boot/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/boot/Kconfig b/boot/Kconfig
index 4b0802b8c6..9780473190 100644
--- a/boot/Kconfig
+++ b/boot/Kconfig
@@ -405,7 +405,7 @@ endif
config LEGACY_IMAGE_FORMAT
bool "Enable support for the legacy image format"
- default y if !FIT_SIGNATURE
+ default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE
help
This option enables the legacy image format. It is enabled by
default for backward compatibility, unless FIT_SIGNATURE is
--
2.36.0
next prev parent reply other threads:[~2022-05-04 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 20:52 [PATCH 1/4] spl: Rename Kconfig SPL_LEGACY_IMAGE_SUPPORT to SPL_LEGACY_IMAGE_FORMAT Andrew Davis
2022-05-04 20:52 ` [PATCH 2/4] spl: Force disable non-FIT loading for TI secure devices Andrew Davis
2022-05-05 13:14 ` Tom Rini
2022-05-11 17:31 ` Tom Rini
2022-05-04 20:52 ` Andrew Davis [this message]
2022-05-05 13:14 ` [PATCH 3/4] boot: Kconfig: Disable " Tom Rini
2022-05-11 17:31 ` Tom Rini
2022-05-04 20:52 ` [PATCH 4/4] boot: Kconfig: Enable FIT processing by default on " Andrew Davis
2022-05-05 13:14 ` Tom Rini
2022-05-11 17:31 ` Tom Rini
2022-05-05 13:14 ` [PATCH 1/4] spl: Rename Kconfig SPL_LEGACY_IMAGE_SUPPORT to SPL_LEGACY_IMAGE_FORMAT Tom Rini
2022-05-11 17:31 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220504205228.5153-3-afd@ti.com \
--to=afd@ti.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.