Skip to contentSkip to conversation

meta-ti: rename j7-evm to j721e-evm

PATCH In review Andrew Davis 3 participants 15 messages Mar 25, 2022 – Mar 29, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/4 meta-ti: rename j7-evm to j721e-evm

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC.

First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm.

Fix up this naming here.

---
 .../machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf}     | 4 ++--
 meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf}  | 4 ++--
 ...s-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} | 6 +++---
 .../{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf}       | 4 ++--
 .../conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf}    | 8 ++++----
 meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb        | 6 +++---
 .../trusted-firmware-a/trusted-firmware-a_%.bbappend      | 2 +-
 meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend    | 2 +-
 meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb    | 2 +-
 9 files changed, 19 insertions(+), 19 deletions(-)
 rename meta-ti-bsp/conf/machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} (63%)
 rename meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf} (82%)
 rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} (53%)
 rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} (67%)
 rename meta-ti-bsp/conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf} (79%)
meta-ti-bsp/conf/machine/j721e-evm-k3r5.conf renamed from meta-ti-bsp/conf/machine/j7-evm-k3r5.conf +2 -2
similarity index 63%
rename from meta-ti-bsp/conf/machine/j7-evm-k3r5.conf
rename to meta-ti-bsp/conf/machine/j721e-evm-k3r5.conf
index b9e8cc01..070bf7aa 100644
@@ -1,6 +1,6 @@
 #@TYPE: Machine
-#@NAME: J7 EVM (R5F)
-#@DESCRIPTION: Machine configuration for the TI J7 EVM (R5F core)
+#@NAME: J721e EVM (R5F)
+#@DESCRIPTION: Machine configuration for the TI J721e EVM (R5F core)
 
 require conf/machine/include/k3r5.inc
 
meta-ti-bsp/conf/machine/j721e-evm.conf renamed from meta-ti-bsp/conf/machine/j7-evm.conf +2 -2
similarity index 82%
rename from meta-ti-bsp/conf/machine/j7-evm.conf
rename to meta-ti-bsp/conf/machine/j721e-evm.conf
index 267a5e14..12d4fecb 100644
@@ -1,6 +1,6 @@
 #@TYPE: Machine
-#@NAME: J7 EVM
-#@DESCRIPTION: Machine configuration for the TI J7 EVM
+#@NAME: J721e EVM
+#@DESCRIPTION: Machine configuration for the TI J721e EVM
 
 require conf/machine/include/j7.inc
 
meta-ti-bsp/conf/machine/j721e-hs-evm-k3r5-sr1-1.conf renamed from meta-ti-bsp/conf/machine/j7-hs-evm-k3r5-sr1-1.conf +3 -3
similarity index 53%
rename from meta-ti-bsp/conf/machine/j7-hs-evm-k3r5-sr1-1.conf
rename to meta-ti-bsp/conf/machine/j721e-hs-evm-k3r5-sr1-1.conf
index 73f5afd6..6e809f46 100644
@@ -1,10 +1,10 @@
 #@TYPE: Machine
-#@NAME: J7 SR1.1 HS EVM (R5F)
-#@DESCRIPTION: Machine configuration for the TI J7 SR1.1 HS EVM (R5F core)
+#@NAME: J721e SR1.1 HS EVM (R5F)
+#@DESCRIPTION: Machine configuration for the TI J721e SR1.1 HS EVM (R5F core)
 
 # Booting SR1.1 requires different SYSFW, the rest is handled at runtime
 
-require conf/machine/j7-hs-evm-k3r5.conf
+require conf/machine/j721e-hs-evm-k3r5.conf
 SOC_FAMILY:append = ":k3r5-sr1-1"
 
 SYSFW_SOC = "j721e_sr1_1"
meta-ti-bsp/conf/machine/j721e-hs-evm-k3r5.conf renamed from meta-ti-bsp/conf/machine/j7-hs-evm-k3r5.conf +2 -2
similarity index 67%
rename from meta-ti-bsp/conf/machine/j7-hs-evm-k3r5.conf
rename to meta-ti-bsp/conf/machine/j721e-hs-evm-k3r5.conf
index 53a7016f..80f3b969 100644
@@ -1,6 +1,6 @@
 #@TYPE: Machine
-#@NAME: J7 HS EVM (R5F)
-#@DESCRIPTION: Machine configuration for the TI J7 HS EVM (R5F core)
+#@NAME: J721e HS EVM (R5F)
+#@DESCRIPTION: Machine configuration for the TI J721e HS EVM (R5F core)
 
 require conf/machine/include/k3r5.inc
 
meta-ti-bsp/conf/machine/j721e-hs-evm.conf renamed from meta-ti-bsp/conf/machine/j7-hs-evm.conf +4 -4
similarity index 79%
rename from meta-ti-bsp/conf/machine/j7-hs-evm.conf
rename to meta-ti-bsp/conf/machine/j721e-hs-evm.conf
index f2e3ccf5..433863dd 100644
@@ -1,8 +1,8 @@
 #@TYPE: Machine
-#@NAME: J7 HS EVM
-#@DESCRIPTION: Machine configuration for the TI J7 HS EVM
+#@NAME: J721e HS EVM
+#@DESCRIPTION: Machine configuration for the TI J721e HS EVM
 
-require conf/machine/j7-evm.conf
+require conf/machine/j721e-evm.conf
 
 UBOOT_MACHINE = "j721e_hs_evm_a72_defconfig"
 
@@ -22,7 +22,7 @@ IMAGE_BOOT_FILES = "${UBOOT_BINARY}"
 BBMULTICONFIG += "k3r5-sr1-1"
 
 # Use default IMAGE_BOOT_FILES_LEGACY files
-# Since default sysfw.itb on J7 is for SR1.1, add a version for SR1.0
+# Since default sysfw.itb on J721e is for SR1.1, add a version for SR1.0
 IMAGE_BOOT_FILES += "sysfw-j721e-evm.itb"
 do_image_wic[mcdepends] += "mc::k3r5-sr1-1:ti-sci-fw:do_deploy"
 do_image_tar[mcdepends] += "mc::k3r5-sr1-1:ti-sci-fw:do_deploy"
meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb +3 -3
index 3d50b112..33333e3c 100644
@@ -23,9 +23,9 @@ SYSFW_SOC ?= "unknown"
 SYSFW_CONFIG ?= "unknown"
 
 SYSFW_PREFIX = "ti-sci-firmware"
-SYSFW_PREFIX:j7-evm-k3r5 = "ti-fs-firmware"
-SYSFW_PREFIX:j7-hs-evm-k3r5 = "ti-fs-firmware"
-SYSFW_PREFIX:j7-hs-evm-k3r5-sr1-1 = "ti-fs-firmware"
+SYSFW_PREFIX:j721e-evm-k3r5 = "ti-fs-firmware"
+SYSFW_PREFIX:j721e-hs-evm-k3r5 = "ti-fs-firmware"
+SYSFW_PREFIX:j721e-hs-evm-k3r5-sr1-1 = "ti-fs-firmware"
 SYSFW_PREFIX:j7200-evm-k3r5 = "ti-fs-firmware"
 SYSFW_PREFIX:j7200-hs-evm-k3r5 = "ti-fs-firmware"
 SYSFW_PREFIX:j721s2-evm-k3r5 = "ti-fs-firmware"
meta-ti-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend +1 -1
index 581f7454..35cb9c95 100644
@@ -26,7 +26,7 @@ do_compile:append:am64xx-hs-evm() {
 	)
 }
 
-do_compile:append:j7-hs-evm() {
+do_compile:append:j721e-hs-evm() {
 	export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
 	( cd ${BUILD_DIR}; \
 		mv bl31.bin bl31.bin.unsigned; \
meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend +1 -1
index f1d7fc9a..f9660bfe 100644
@@ -55,7 +55,7 @@ do_compile:append:am64xx-hs-evm() {
     optee_sign_k3hs
 }
 
-do_compile:append:j7-hs-evm() {
+do_compile:append:j721e-hs-evm() {
     optee_sign_k3hs
 }
 
meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb +1 -1
index 8aa823cc..03408528 100644
@@ -49,7 +49,7 @@ LEGACY_DM_FW_DIR  = "${D}${nonarch_base_libdir}/firmware/pdk-ipc/"
 DM_FIRMWARE = "ipc_echo_testb_mcu1_0_release_strip.xer5f"
 
 # J7 HS support
-do_install:prepend:j7-hs-evm() {
+do_install:prepend:j721e-hs-evm() {
 	export TI_SECURE_DEV_PKG=${TI_SECURE_DEV_PKG}
 	( cd ${RTOS_DM_FW_DIR}; \
 		mv ${DM_FIRMWARE} ${DM_FIRMWARE}.unsigned; \
Signature · 1 line
2.17.1
#1 lore raw

PATCH 2/4 meta-ti-bsp: add SoC families for the J7 SoCs

This allows us to be more specific around what SoCs we support and lets us add features based on the SoC family not just at the EVM or whole J7family level.

---
 meta-ti-bsp/conf/machine/include/j7200.inc  | 2 ++
 meta-ti-bsp/conf/machine/include/j721e.inc  | 4 ++++
 meta-ti-bsp/conf/machine/include/j721s2.inc | 2 ++
 meta-ti-bsp/conf/machine/j7200-evm.conf     | 2 +-
 meta-ti-bsp/conf/machine/j721e-evm.conf     | 4 +---
 meta-ti-bsp/conf/machine/j721s2-evm.conf    | 2 +-
 6 files changed, 11 insertions(+), 5 deletions(-)
 create mode 100644 meta-ti-bsp/conf/machine/include/j7200.inc
 create mode 100644 meta-ti-bsp/conf/machine/include/j721e.inc
 create mode 100644 meta-ti-bsp/conf/machine/include/j721s2.inc
meta-ti-bsp/conf/machine/include/j7200.inc new file +2 -0
new file mode 100644
index 00000000..ce88567c
@@ -0,0 +1,2 @@
+require conf/machine/include/j7.inc
+SOC_FAMILY:append = ":j7200"
meta-ti-bsp/conf/machine/include/j721e.inc new file +4 -0
new file mode 100644
index 00000000..d965327c
@@ -0,0 +1,4 @@
+require conf/machine/include/j7.inc
+SOC_FAMILY:append = ":j721e"
+
+MACHINE_FEATURES += "gpu"
meta-ti-bsp/conf/machine/include/j721s2.inc new file +2 -0
new file mode 100644
index 00000000..113f86c4
@@ -0,0 +1,2 @@
+require conf/machine/include/j7.inc
+SOC_FAMILY:append = ":j721s2"
meta-ti-bsp/conf/machine/j7200-evm.conf +1 -1
index 2565c90c..175d30f8 100644
@@ -2,7 +2,7 @@
 #@NAME: J7200 EVM
 #@DESCRIPTION: Machine configuration for the TI J7200 EVM
 
-require conf/machine/include/j7.inc
+require conf/machine/include/j7200.inc
 
 SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS3"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
meta-ti-bsp/conf/machine/j721e-evm.conf +1 -3
index 12d4fecb..fe28e6f5 100644
@@ -2,9 +2,7 @@
 #@NAME: J721e EVM
 #@DESCRIPTION: Machine configuration for the TI J721e EVM
 
-require conf/machine/include/j7.inc
-
-MACHINE_FEATURES += "gpu"
+require conf/machine/include/j721e.inc
 
 SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS3"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
meta-ti-bsp/conf/machine/j721s2-evm.conf +1 -1
index 82fd33da..a2c15f74 100644
@@ -2,7 +2,7 @@
 #@NAME: J721S2 EVM
 #@DESCRIPTION: Machine configuration for the TI J721S2 EVM
 
-require conf/machine/include/j7.inc
+require conf/machine/include/j721s2.inc
 
 SERIAL_CONSOLES = "115200;ttyS10"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
Signature · 1 line
2.17.1
#3 lore raw

Re: [meta-ti][master][PATCH 2/4] meta-ti-bsp: add SoC families for the J7 SoCs

Quoted 8 lines · Denys Dmytriyenko
Quoted 5 lines · Andrew F. Davis via lists.yoctoproject.org

This allows us to be more specific around what SoCs we support and lets us add features based on the SoC family not just at the EVM or whole J7family level.

Appled patch to master.

Signature · 3 lines
Ryan Eatmon                [email protected]
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS
#4 lore raw

PATCH 3/4 ti-img-rogue-umlibs: only the j721e SoC is currently supported

In reply to Andrew Davis

There are now three SoCs in the J7 family, but only the j721e variant is currently supported. Be specific here.

---
 .../libgles/ti-img-rogue-umlibs_1.13.5776728.bb                 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-ti-bsp/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb +1 -1
index f54c3ee9..18b36fbb 100644
@@ -8,7 +8,7 @@ inherit features_check
 REQUIRED_MACHINE_FEATURES = "gpu"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "j7"
+COMPATIBLE_MACHINE = "j721e"
 
 PR = "r3"
 
Signature · 1 line
2.17.1
#6 lore raw

Re: [meta-ti][master][PATCH 3/4] ti-img-rogue-umlibs: only the j721e SoC is currently supported

Quoted 7 lines · Denys Dmytriyenko
Quoted 4 lines · Andrew F. Davis via lists.yoctoproject.org

There are now three SoCs in the J7 family, but only the j721e variant is currently supported. Be specific here.

Appled patch to master.

Signature · 3 lines
Ryan Eatmon                [email protected]
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS
#7 lore raw

PATCH 4/4 ti-sgx-ddk-um: only the am65xx member of the k3 family is supported

In reply to Andrew Davis

The AM65xx is the only member of the K3 family with an SGX GPU. Be specific here to avoid confusion.

---
 .../recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
meta-ti-bsp/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb +2 -2
index d4b7a1a6..f4c71d25 100644
@@ -8,7 +8,7 @@ inherit features_check
 REQUIRED_MACHINE_FEATURES = "gpu"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
+COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|am65xx"
 
 PR = "r37"
 
@@ -20,7 +20,7 @@ SRCREV = "742cf38aba13e1ba1a910cf1f036a1a212c263b6"
 TARGET_PRODUCT:omap-a15 = "jacinto6evm"
 TARGET_PRODUCT:ti33x = "ti335x"
 TARGET_PRODUCT:ti43x = "ti437x"
-TARGET_PRODUCT:k3 = "ti654x"
+TARGET_PRODUCT:am65xx = "ti654x"
 
 INITSCRIPT_NAME = "rc.pvr"
 INITSCRIPT_PARAMS = "defaults 8"
Signature · 1 line
2.17.1
#9 lore raw

Re: [meta-ti][master][PATCH 4/4] ti-sgx-ddk-um: only the am65xx member of the k3 family is supported

Quoted 7 lines · Denys Dmytriyenko
Quoted 4 lines · Andrew F. Davis via lists.yoctoproject.org

The AM65xx is the only member of the K3 family with an SGX GPU. Be specific here to avoid confusion.

Appled patch to master.

Signature · 3 lines
Ryan Eatmon                [email protected]
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS
#10 lore raw
In reply to Andrew Davis
Quoted 9 lines · Andrew F. Davis via lists.yoctoproject.org

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC.

First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm.

Fix up this naming here.

Heh, I was actually thinking of finally making such change myself lately! :)

My main concern was about breaking downstream users of meta-ti who builds on top of j7-evm platform. But it is probably a good time to get it into master now, as recent layer restructuring already required downstream changes and adjustments.

Quoted 1 line

I looked over the changes in both patchsets and they seem fine. I'm going to do a quick test locally though.

Quoted 16 lines
---
 .../machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf}     | 4 ++--
 meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf}  | 4 ++--
 ...s-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} | 6 +++---
 .../{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf}       | 4 ++--
 .../conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf}    | 8 ++++----
 meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb        | 6 +++---
 .../trusted-firmware-a/trusted-firmware-a_%.bbappend      | 2 +-
 meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend    | 2 +-
 meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb    | 2 +-
 9 files changed, 19 insertions(+), 19 deletions(-)
 rename meta-ti-bsp/conf/machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} (63%)
 rename meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf} (82%)
 rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} (53%)
 rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} (67%)
 rename meta-ti-bsp/conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf} (79%)
Signature · 4 lines
Regards,
Denys Dmytriyenko <[email protected]>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964
#11 lore raw
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Andrew F. Davis via lists.yoctoproject.org

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC.

First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm.

Quoted 9 lines
Quoted 1 line

Fix up this naming here.

Heh, I was actually thinking of finally making such change myself lately! :)

My main concern was about breaking downstream users of meta-ti who builds on top of j7-evm platform. But it is probably a good time to get it into master now, as recent layer restructuring already required downstream changes and adjustments.

There are also some external docs on this that need updated but I can take a lead on that.

Quoted 6 lines
Quoted 2 lines

I looked over the changes in both patchsets and they seem fine. I'm going to do a quick test locally though.

Thanks, that would be good, I have to admit my setup is not all the way back together yet so my testing here was very limited..

Andrew

Quoted 18 lines
Quoted 17 lines
---
  .../machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf}     | 4 ++--
  meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf}  | 4 ++--
  ...s-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} | 6 +++---
  .../{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf}       | 4 ++--
  .../conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf}    | 8 ++++----
  meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb        | 6 +++---
  .../trusted-firmware-a/trusted-firmware-a_%.bbappend      | 2 +-
  meta-ti-bsp/recipes-security/optee/optee-os_%.bbappend    | 2 +-
  meta-ti-bsp/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb    | 2 +-
  9 files changed, 19 insertions(+), 19 deletions(-)

rename meta-ti-bsp/conf/machine/{j7-evm-k3r5.conf => j721e-evm-k3r5.conf} (63%) rename meta-ti-bsp/conf/machine/{j7-evm.conf => j721e-evm.conf} (82%)
rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5-sr1-1.conf => j721e-hs-evm-k3r5-sr1-1.conf} (53%) rename meta-ti-bsp/conf/machine/{j7-hs-evm-k3r5.conf => j721e-hs-evm-k3r5.conf} (67%) rename meta-ti-bsp/conf/machine/{j7-hs-evm.conf => j721e-hs-evm.conf} (79%)

#12 lore raw
Quoted 23 lines · Andrew F. Davis via lists.yoctoproject.org
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Andrew F. Davis via lists.yoctoproject.org

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC.

First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm.

Quoted 8 lines
Quoted 1 line

Fix up this naming here.

Heh, I was actually thinking of finally making such change myself lately! :)

My main concern was about breaking downstream users of meta-ti who builds on top of j7-evm platform. But it is probably a good time to get it into master now, as recent layer restructuring already required downstream changes and adjustments.

There are also some external docs on this that need updated but I can take a lead on that.

Quoted 7 lines
Quoted 4 lines
Quoted 1 line

I looked over the changes in both patchsets and they seem fine. I'm going to do a quick test locally though.

Thanks, that would be good, I have to admit my setup is not all the way back together yet so my testing here was very limited..

Ok, I was finally able to build all K3 platforms and couple legacy platforms with these patches aplied locally - everything seems fine!

Signature · 4 lines
Regards,
Denys Dmytriyenko <[email protected]>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964
Tested-by on v1 1/4
#13 lore raw
In reply to Andrew Davis
Quoted 11 lines · Andrew F. Davis via lists.yoctoproject.org

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC.

First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm.

Fix up this naming here.

#14 lore raw
Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Andrew F. Davis via lists.yoctoproject.org

In many places we use "j7" the family when we should be using a specific SoC or EVM and vice-versa. For instance when including graphics drivers we add for all "j7" family, but what we really want is only for some specific j7 SoC.

Quoted 8 lines
Quoted 6 lines

First step in untangling this is to make it clear that there is no SoC called j7. There is a SoC called j721e with a j721e-evm.

Fix up this naming here.

Appled patch to master.

Signature · 3 lines
Ryan Eatmon                [email protected]
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS