diff options
| author | Vignesh Raghavendra <vigneshr@ti.com> | 2023-02-20 11:54:40 +0530 |
|---|---|---|
| committer | Praneeth Bajjuri <praneeth@ti.com> | 2023-02-21 17:56:53 -0600 |
| commit | 4a2944651ece9a090ab0d1911db29cb06d3bc21b (patch) | |
| tree | 0031fa042d3220a42c9770c0d0384692a056010c | |
| parent | f4a78b7d370b0583b4ec165d482f17fc36fe5681 (diff) | |
arm: mach-k3: common: Don't default to fitImage for HS-FS
HS-FS is technically a GP device wrt development flow, kernel images can
be either signed and packaged as a fitImage or can be regular Image and
dtbs loaded separately.
Default to legacy booting mechanism for kernel ie Image and dtb are
individual files and not necessarily signed. This provides widest
compatibility and aligns with ease of use.
For HS-SE though, keep fitImage as default though as one expects to boot
signed images on secure devices.
Users can force fitImage boot by setting boot_fit 1 on HS-FS too.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
| -rw-r--r-- | arch/arm/mach-k3/common.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/mach-k3/common.c b/arch/arm/mach-k3/common.c index e4a825365c..bd4086bb04 100644 --- a/arch/arm/mach-k3/common.c +++ b/arch/arm/mach-k3/common.c @@ -627,8 +627,8 @@ int misc_init_r(void) printf("Failed to probe am65_cpsw_nuss driver\n"); } - /* Default FIT boot on non-GP devices */ - if (get_device_type() != K3_DEVICE_TYPE_GP) { + /* Default FIT boot on HS-SE devices */ + if (get_device_type() == K3_DEVICE_TYPE_HS_SE) { if (!env_get("boot_fit")) env_set("boot_fit", "1"); } |