summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine/j721e-evm.conf
diff options
context:
space:
mode:
authorAndrew Davis <afd@ti.com>2022-03-25 13:41:48 -0500
committerRyan Eatmon <reatmon@ti.com>2022-03-29 07:33:57 -0500
commit8cc837d2384d441e56b5006acf9b60503a0a5c8c (patch)
tree29de60889b65d8e511b583e5feb8be0a1ed9c1bc /meta-ti-bsp/conf/machine/j721e-evm.conf
parentf1b6ff15039c9f0b8e93d70856fb566a16cb099b (diff)
downloadmeta-ti-8cc837d2384d441e56b5006acf9b60503a0a5c8c.tar.gz
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. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Diffstat (limited to 'meta-ti-bsp/conf/machine/j721e-evm.conf')
-rw-r--r--meta-ti-bsp/conf/machine/j721e-evm.conf18
1 files changed, 18 insertions, 0 deletions
diff --git a/meta-ti-bsp/conf/machine/j721e-evm.conf b/meta-ti-bsp/conf/machine/j721e-evm.conf
new file mode 100644
index 00000000..12d4fecb
--- /dev/null
+++ b/meta-ti-bsp/conf/machine/j721e-evm.conf
@@ -0,0 +1,18 @@
1#@TYPE: Machine
2#@NAME: J721e EVM
3#@DESCRIPTION: Machine configuration for the TI J721e EVM
4
5require conf/machine/include/j7.inc
6
7MACHINE_FEATURES += "gpu"
8
9SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS3"
10SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
11
12KERNEL_DEVICETREE = " \
13 ti/k3-j721e-common-proc-board.dtb \
14 ti/k3-j721e-common-proc-board-infotainment.dtbo \
15 ti/k3-j721e-sk.dtb \
16"
17
18UBOOT_MACHINE = "j721e_evm_a72_config"