* [meta-ti][dunfell][PATCH 01/11] machine: Add am62xx evm configuration
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 02/11] recipes-ti: ti-rtos-bin: Add AM62x binaries Ryan Eatmon
` (10 subsequent siblings)
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nishanth Menon <nm@ti.com>
Lets add the basic AM62xx-evm configuration.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
conf/machine/am62xx-evm-k3r5.conf | 11 +++++++++++
conf/machine/am62xx-evm.conf | 13 +++++++++++++
conf/machine/include/am62xx.inc | 17 +++++++++++++++++
recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 18 ++++++++++++++++++
recipes-bsp/u-boot/u-boot-ti.inc | 6 ++++++
5 files changed, 65 insertions(+)
create mode 100644 conf/machine/am62xx-evm-k3r5.conf
create mode 100644 conf/machine/am62xx-evm.conf
create mode 100644 conf/machine/include/am62xx.inc
diff --git a/conf/machine/am62xx-evm-k3r5.conf b/conf/machine/am62xx-evm-k3r5.conf
new file mode 100644
index 00000000..724a8d4a
--- /dev/null
+++ b/conf/machine/am62xx-evm-k3r5.conf
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: AM62XX EVM (R5F)
+#@DESCRIPTION: Machine configuration for the TI AM62xx EVM (R5F core)
+
+require conf/machine/include/k3r5.inc
+
+SYSFW_SOC = "am62x"
+SYSFW_CONFIG = "evm"
+SYSFW_SUFFIX = "gp"
+
+UBOOT_MACHINE = "am62x_evm_r5_defconfig"
diff --git a/conf/machine/am62xx-evm.conf b/conf/machine/am62xx-evm.conf
new file mode 100644
index 00000000..600abb58
--- /dev/null
+++ b/conf/machine/am62xx-evm.conf
@@ -0,0 +1,13 @@
+#@TYPE: Machine
+#@NAME: AM62XX EVM
+#@DESCRIPTION: Machine configuration for the TI AM62XX EVM
+
+require conf/machine/include/am62xx.inc
+
+KERNEL_DEVICETREE = " \
+ ti/k3-am625-sk.dtb \
+ ti/k3-am625-sk-lpmdemo.dtb \
+ ti/k3-am625-minimal.dtb \
+"
+
+UBOOT_MACHINE = "am62x_evm_a53_defconfig"
diff --git a/conf/machine/include/am62xx.inc b/conf/machine/include/am62xx.inc
new file mode 100644
index 00000000..06bac922
--- /dev/null
+++ b/conf/machine/include/am62xx.inc
@@ -0,0 +1,17 @@
+require conf/machine/include/k3.inc
+SOC_FAMILY_append = ":am62xx"
+
+MACHINE_FEATURES += "screen touchscreen"
+
+SERIAL_CONSOLES = "115200;ttyS2"
+SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
+
+# AM64 supports multi-certificate images, use the same
+IMAGE_BOOT_FILES = "${IMAGE_BOOT_FILES_MULTI_CERT}"
+
+do_image_wic[mcdepends] = "mc::k3r5:ti-sci-fw:do_deploy"
+do_image_tar[mcdepends] = "mc::k3r5:ti-sci-fw:do_deploy"
+
+TFA_BOARD = "lite"
+OPTEEMACHINE = "k3-am65x"
+OPTEEOUTPUTMACHINE = "k3"
diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
index 646833a7..099473b4 100644
--- a/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
+++ b/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb
@@ -6,6 +6,7 @@ DEPENDS_append_j7200-hs-evm-k3r5 = " virtual/bootloader"
DEPENDS_append_j721s2-evm-k3r5 = " virtual/bootloader"
DEPENDS_append_am64xx-evm-k3r5 = " virtual/bootloader"
DEPENDS_append_am64xx-hs-evm-k3r5 = " virtual/bootloader"
+DEPENDS_append_am62xx-evm-k3r5 = " virtual/bootloader"
CLEANBROKEN = "1"
PR = "${INC_PR}.2"
@@ -29,6 +30,7 @@ SYSFW_PREFIX_j7-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"
+SYSFW_PREFIX_am62xx-evm-k3r5 = "ti-fs-firmware"
SYSFW_SUFFIX ?= "unknown"
@@ -63,6 +65,7 @@ EXTRA_OEMAKE_append_j7200-hs-evm-k3r5 = " SBL="${STAGING_DIR_HOST}/boot/u-boot-s
EXTRA_OEMAKE_append_j721s2-evm-k3r5 = " SBL="${STAGING_DIR_HOST}/boot/u-boot-spl.bin""
EXTRA_OEMAKE_append_am64xx-evm-k3r5 = " SBL="${STAGING_DIR_HOST}/boot/u-boot-spl.bin""
EXTRA_OEMAKE_append_am64xx-hs-evm-k3r5 = " SBL="${STAGING_DIR_HOST}/boot/u-boot-spl.bin""
+EXTRA_OEMAKE_append_am62xx-evm-k3r5 = " SBL="${STAGING_DIR_HOST}/boot/u-boot-spl.bin""
do_compile() {
cd ${WORKDIR}/imggen/
@@ -170,4 +173,19 @@ do_deploy_am64xx-hs-evm-k3r5() {
install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/
}
+do_install_am62xx-evm-k3r5() {
+ install -d ${D}/boot
+ install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${D}/boot/${UBOOT_IMAGE}
+ ln -sf ${UBOOT_IMAGE} ${D}/boot/${UBOOT_SYMLINK}
+ ln -sf ${UBOOT_IMAGE} ${D}/boot/${UBOOT_BINARY}
+}
+
+do_deploy_am62xx-evm-k3r5() {
+ install -d ${DEPLOYDIR}
+ install -m 644 ${WORKDIR}/imggen/${UBOOT_BINARY} ${DEPLOYDIR}/${UBOOT_IMAGE}
+ ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_SYMLINK}
+ ln -sf ${UBOOT_IMAGE} ${DEPLOYDIR}/${UBOOT_BINARY}
+ install -m 644 ${SYSFW_TISCI} ${DEPLOYDIR}/
+}
+
addtask deploy before do_build after do_compile
diff --git a/recipes-bsp/u-boot/u-boot-ti.inc b/recipes-bsp/u-boot/u-boot-ti.inc
index 7ed6c5b4..6098f989 100644
--- a/recipes-bsp/u-boot/u-boot-ti.inc
+++ b/recipes-bsp/u-boot/u-boot-ti.inc
@@ -69,6 +69,7 @@ SPL_UART_BINARY_j7200-hs-evm-k3r5 = "u-boot-spl.bin"
SPL_UART_BINARY_j721s2-evm-k3r5 = "u-boot-spl.bin"
SPL_UART_BINARY_am64xx-evm-k3r5 = "u-boot-spl.bin"
SPL_UART_BINARY_am64xx-hs-evm-k3r5 = "u-boot-spl.bin"
+SPL_UART_BINARY_am62xx-evm-k3r5 = "u-boot-spl.bin"
SPL_UART_IMAGE ?= "${SPL_UART_BINARY}-${MACHINE}-${PV}-${PR}"
SPL_UART_SYMLINK ?= "${SPL_UART_BINARY}-${MACHINE}"
@@ -419,4 +420,9 @@ do_deploy_append_am64xx-hs-evm-k3r5 () {
mv ${DEPLOYDIR}/u-boot-spl.bin ${DEPLOYDIR}/u-boot-spl-r5spl.bin || true
}
+do_deploy_append_am62xx-evm-k3r5 () {
+ mv ${DEPLOYDIR}/tiboot3.bin ${DEPLOYDIR}/tiboot3-r5spl.bin || true
+ mv ${DEPLOYDIR}/u-boot-spl.bin ${DEPLOYDIR}/u-boot-spl-r5spl.bin || true
+}
+
TOOLCHAIN = "gcc"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 02/11] recipes-ti: ti-rtos-bin: Add AM62x binaries
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 01/11] machine: Add am62xx evm configuration Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 03/11] recipes: Pick up correct image and build DM to boot images Ryan Eatmon
` (9 subsequent siblings)
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nishanth Menon <nm@ti.com>
Add binaries for AM62x
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index c5852dbd..431c13da 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -19,6 +19,7 @@ PLAT_SFX_j7200-hs-evm = "j7200"
PLAT_SFX_j721s2-evm = "j721s2"
PLAT_SFX_am65xx = "am65xx"
PLAT_SFX_am64xx = "am64xx"
+PLAT_SFX_am62xx-evm = "am62xx"
FILESEXTRAPATHS_prepend := "${METATIBASE}/recipes-bsp/ti-sci-fw/files/:"
require recipes-bsp/ti-linux-fw/ti-linux-fw.inc
@@ -154,6 +155,13 @@ do_install_am64xx() {
install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
}
+do_install_am62xx-evm() {
+ install -d ${LEGACY_IPC_FW_DIR}
+ # No specific firmware to install till M4F comes online
+ # DM Firmware
+ install -m 0644 ${RTOS_DM_FW_DIR}/ipc_echo_testb_mcu1_0_release_strip.xer5f ${LEGACY_DM_FW_DIR}
+}
+
# Set up names for the firmwares
ALTERNATIVE_${PN}_am65xx = "\
am65x-mcu-r5f0_0-fw \
@@ -205,6 +213,10 @@ ALTERNATIVE_${PN}_j721s2-evm = "\
j721s2-c71_1-fw \
"
+ALTERNATIVE_${PN}_am62xx-evm = "\
+ am62xx-main-r5f0_0-fw \
+ "
+
# Set up link names for the firmwares
TARGET_MCU_R5FSS0_0_am65xx = "am65x-mcu-r5f0_0-fw"
@@ -245,6 +257,8 @@ TARGET_MAIN_R5FSS1_1_j721s2-evm = "j721s2-main-r5f1_1-fw"
TARGET_C7X_0_j721s2-evm = "j721s2-c71_0-fw"
TARGET_C7X_1_j721s2-evm = "j721s2-c71_1-fw"
+TARGET_MAIN_R5FSS0_0_am62xx-evm = "am62xx-main-r5f0_0-fw"
+
ALTERNATIVE_LINK_NAME[am65x-mcu-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
ALTERNATIVE_LINK_NAME[am65x-mcu-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
@@ -278,6 +292,8 @@ ALTERNATIVE_LINK_NAME[j721s2-main-r5f1_1-fw] = "${base_libdir}/firmware/${TARGET
ALTERNATIVE_LINK_NAME[j721s2-c71_0-fw] = "${base_libdir}/firmware/${TARGET_C7X_0}"
ALTERNATIVE_LINK_NAME[j721s2-c71_1-fw] = "${base_libdir}/firmware/${TARGET_C7X_1}"
+ALTERNATIVE_LINK_NAME[am62xx-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
+
# Create the firmware alternatives
ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release_strip.xer5f"
@@ -313,6 +329,8 @@ ALTERNATIVE_TARGET[j721s2-main-r5f1_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc
ALTERNATIVE_TARGET[j721s2-c71_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c7x_1_release_strip.xe71"
ALTERNATIVE_TARGET[j721s2-c71_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c7x_2_release_strip.xe71"
+ALTERNATIVE_TARGET[am62xx-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
+
ALTERNATIVE_PRIORITY = "10"
# make sure that lib/firmware, and all its contents are part of the package
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 03/11] recipes: Pick up correct image and build DM to boot images
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 01/11] machine: Add am62xx evm configuration Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 02/11] recipes-ti: ti-rtos-bin: Add AM62x binaries Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 04/11] HACK: recipes-ti: ti-rtos-metadata: Make am62x point to am64x Ryan Eatmon
` (8 subsequent siblings)
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nishanth Menon <nm@ti.com>
Make sure we have bootable wic images.
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-bsp/u-boot/u-boot-ti.inc | 1 +
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/recipes-bsp/u-boot/u-boot-ti.inc b/recipes-bsp/u-boot/u-boot-ti.inc
index 6098f989..231b7647 100644
--- a/recipes-bsp/u-boot/u-boot-ti.inc
+++ b/recipes-bsp/u-boot/u-boot-ti.inc
@@ -41,6 +41,7 @@ PACKAGECONFIG[dm] = "DM=${STAGING_DIR_HOST}${nonarch_base_libdir}/firmware/pdk-i
PACKAGECONFIG_append_aarch64 = " atf optee"
PACKAGECONFIG_append_j7 = " dm"
+PACKAGECONFIG_append_am62xx = " dm"
COMPATIBLE_MACHINE = "(ti-soc)"
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 431c13da..4cd08a36 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -19,7 +19,7 @@ PLAT_SFX_j7200-hs-evm = "j7200"
PLAT_SFX_j721s2-evm = "j721s2"
PLAT_SFX_am65xx = "am65xx"
PLAT_SFX_am64xx = "am64xx"
-PLAT_SFX_am62xx-evm = "am62xx"
+PLAT_SFX_am62xx-evm = "am62x"
FILESEXTRAPATHS_prepend := "${METATIBASE}/recipes-bsp/ti-sci-fw/files/:"
require recipes-bsp/ti-linux-fw/ti-linux-fw.inc
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 04/11] HACK: recipes-ti: ti-rtos-metadata: Make am62x point to am64x
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (2 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 03/11] recipes: Pick up correct image and build DM to boot images Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 20:42 ` Nishanth Menon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 05/11] ti-graphics: Add AM62x GPU (AXE1-16M) support v4 Ryan Eatmon
` (7 subsequent siblings)
11 siblings, 1 reply; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nishanth Menon <nm@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
index e435676f..4f320e4c 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
@@ -14,6 +14,7 @@ PLAT_SFX_j7 = "/j721e"
PLAT_SFX_j7200-evm = "/j7200"
PLAT_SFX_am65xx = "/am65xx"
PLAT_SFX_am64xx = "/am64x"
+PLAT_SFX_am62xx = "/am64x"
# Use weak assignment to set defaults to TI_RTOS_METADATA_* variables
TI_RTOS_METADATA_URI ?= "git://git.ti.com/processor-sdk/coresdk_rtos_releases.git"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* Re: [meta-ti][dunfell][PATCH 04/11] HACK: recipes-ti: ti-rtos-metadata: Make am62x point to am64x
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 04/11] HACK: recipes-ti: ti-rtos-metadata: Make am62x point to am64x Ryan Eatmon
@ 2022-03-22 20:42 ` Nishanth Menon
0 siblings, 0 replies; 17+ messages in thread
From: Nishanth Menon @ 2022-03-22 20:42 UTC (permalink / raw)
To: reatmon; +Cc: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
On 11:25-20220322, Ryan Eatmon via lists.yoctoproject.org wrote:
> From: Nishanth Menon <nm@ti.com>
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
> index e435676f..4f320e4c 100644
> --- a/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
> +++ b/recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb
> @@ -14,6 +14,7 @@ PLAT_SFX_j7 = "/j721e"
> PLAT_SFX_j7200-evm = "/j7200"
> PLAT_SFX_am65xx = "/am65xx"
> PLAT_SFX_am64xx = "/am64x"
> +PLAT_SFX_am62xx = "/am64x"
NAK -> I know I authored these initial patches during silicon bringup,
but please do squash and cleanup the patches prior to posting
upstream.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply [flat|nested] 17+ messages in thread
* [meta-ti][dunfell][PATCH 05/11] ti-graphics: Add AM62x GPU (AXE1-16M) support v4
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (3 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 04/11] HACK: recipes-ti: ti-rtos-metadata: Make am62x point to am64x Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:38 ` Etheridge, Darren
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 06/11] recipes-bsp: lpm-demo: Introduce low power mode demo package Ryan Eatmon
` (6 subsequent siblings)
11 siblings, 1 reply; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Krunal Bhargav <k-bhargav@ti.com>
Signed-off-by: Krunal Bhargav <k-bhargav@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
conf/machine/am62xx-evm.conf | 2 +
.../ti-img-rogue-driver_1.13.5776728.bb | 40 ------------------
.../ti-img-rogue-driver_1.15.6133109.bb | 42 +++++++++++++++++++
...bb => ti-img-rogue-umlibs_1.15.6133109.bb} | 17 ++++----
4 files changed, 53 insertions(+), 48 deletions(-)
delete mode 100644 recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
create mode 100644 recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
rename recipes-graphics/libgles/{ti-img-rogue-umlibs_1.13.5776728.bb => ti-img-rogue-umlibs_1.15.6133109.bb} (77%)
diff --git a/conf/machine/am62xx-evm.conf b/conf/machine/am62xx-evm.conf
index 600abb58..086e40e4 100644
--- a/conf/machine/am62xx-evm.conf
+++ b/conf/machine/am62xx-evm.conf
@@ -4,6 +4,8 @@
require conf/machine/include/am62xx.inc
+MACHINE_FEATURES += "gpu"
+
KERNEL_DEVICETREE = " \
ti/k3-am625-sk.dtb \
ti/k3-am625-sk-lpmdemo.dtb \
diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
deleted file mode 100644
index a05de0f2..00000000
--- a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
+++ /dev/null
@@ -1,40 +0,0 @@
-DESCRIPTION = "Kernel drivers for the PowerVR Rogue GPU found in the TI SoCs"
-HOMEPAGE = "http://git.ti.com/graphics/ti-img-rogue-driver"
-LICENSE = "MIT | GPLv2"
-LIC_FILES_CHKSUM = "file://README;beginline=14;endline=19;md5=0403c7dea01a2b8232261e805325fac2"
-
-inherit module features_check
-
-REQUIRED_MACHINE_FEATURES = "gpu"
-
-MACHINE_KERNEL_PR_append = "b"
-PR = "${MACHINE_KERNEL_PR}"
-
-PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "j7"
-
-DEPENDS = "virtual/kernel"
-
-PROVIDES = "virtual/gpudriver"
-
-BRANCH = "1.13-5776728/linux-k5.10"
-
-SRC_URI = " \
- git://git.ti.com/graphics/ti-img-rogue-driver.git;branch=${BRANCH} \
- file://0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch \
-"
-
-S = "${WORKDIR}/git"
-
-SRCREV = "35a25875ae8738f82c7cabc6b077ef992b0cca84"
-
-PVR_SOC = "j721e_linux"
-PVR_BVNC = "22.104.208.318"
-PVR_BUILD = "release"
-PVR_WS = "wayland"
-
-EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${PVR_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${PVR_SOC} WINDOW_SYSTEM=${PVR_WS}'
-
-do_install() {
- make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D}${root_prefix} PREFIX=${STAGING_DIR_HOST} modules_install
-}
diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
new file mode 100644
index 00000000..0dfc50ec
--- /dev/null
+++ b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
@@ -0,0 +1,42 @@
+DESCRIPTION = "Kernel drivers for the PowerVR Rogue GPU found in the TI SoCs"
+HOMEPAGE = "https://bitbucket.itg.ti.com/scm/lcpd-priv-sdk/rogue_km"
+LICENSE = "MIT | GPLv2"
+LIC_FILES_CHKSUM = "file://README;beginline=14;endline=19;md5=0403c7dea01a2b8232261e805325fac2"
+
+inherit module features_check
+
+REQUIRED_MACHINE_FEATURES = "gpu"
+
+MACHINE_KERNEL_PR_append = "a"
+PR = "${MACHINE_KERNEL_PR}"
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_MACHINE = "j7|am62xx"
+
+DEPENDS = "virtual/kernel"
+
+PROVIDES = "virtual/gpudriver"
+
+BRANCH = "am62xx-wakeup"
+
+SRC_URI = " \
+ git://git@bitbucket.itg.ti.com/lcpd-priv-sdk/rogue_km.git;protocol=ssh;branch=${BRANCH} \
+ file://0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch \
+"
+
+S = "${WORKDIR}/git"
+
+SRCREV = "438ff717ff6d46754fce1e10c6d3a3828cff77c9"
+
+TARGET_PRODUCT_j7 = "j721e_linux"
+TARGET_PRODUCT_am62xx = "am62_linux"
+TARGET_BVNC_j7 = "22.104.208.318"
+TARGET_BVNC_am62xx = "33.15.11.3"
+PVR_BUILD = "release"
+PVR_WS = "wayland"
+
+EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${TARGET_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${TARGET_PRODUCT} WINDOW_SYSTEM=${PVR_WS}'
+
+do_install() {
+ make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${TARGET_PRODUCT}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D}${root_prefix} PREFIX=${STAGING_DIR_HOST} modules_install
+}
diff --git a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.15.6133109.bb
similarity index 77%
rename from recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb
rename to recipes-graphics/libgles/ti-img-rogue-umlibs_1.15.6133109.bb
index 5194015e..611cbabe 100644
--- a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb
+++ b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.15.6133109.bb
@@ -1,5 +1,5 @@
DESCRIPTION = "Userspace libraries for PowerVR Rogue GPU on TI SoCs"
-HOMEPAGE = "http://git.ti.com/graphics/ti-img-rogue-umlibs"
+HOMEPAGE = "https://bitbucket.itg.ti.com/scm/lcpd-priv-sdk/rogue_umlibs.git"
LICENSE = "TI-TFL"
LIC_FILES_CHKSUM = "file://LICENSE;md5=7232b98c1c58f99e3baa03de5207e76f"
@@ -8,17 +8,18 @@ inherit features_check
REQUIRED_MACHINE_FEATURES = "gpu"
PACKAGE_ARCH = "${MACHINE_ARCH}"
-COMPATIBLE_MACHINE = "j7"
+COMPATIBLE_MACHINE = "j7|am62xx"
-PR = "r3"
+PR = "r1"
-BRANCH = "linuxws/dunfell/k5.10/${PV}"
+BRANCH = "am62xx-wakeup"
-SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-umlibs.git;branch=${BRANCH}"
+SRC_URI = "git://git@bitbucket.itg.ti.com/lcpd-priv-sdk/rogue_umlibs.git;protocol=ssh;branch=${BRANCH}"
-SRCREV = "5ef38353c38d921a65ea6df75c7b6ce710b66034"
+SRCREV = "4de3317c83c9f5a3681bf3660527673f3226e401"
-PVR_SOC ?= "j721e_linux"
+TARGET_PRODUCT_j7 = "j721e_linux"
+TARGET_PRODUCT_am62xx = "am62_linux"
PVR_BUILD ?= "release"
PVR_WS = "wayland"
@@ -50,7 +51,7 @@ RRECOMMENDS_${PN} += "ti-img-rogue-driver"
S = "${WORKDIR}/git"
do_install () {
- oe_runmake install DESTDIR=${D} TARGET_PRODUCT=${PVR_SOC} BUILD=${PVR_BUILD} WINDOW_SYSTEM=${PVR_WS}
+ oe_runmake install DESTDIR=${D} TARGET_PRODUCT=${TARGET_PRODUCT} BUILD=${PVR_BUILD} WINDOW_SYSTEM=${PVR_WS}
chown -R root:root ${D}
}
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* Re: [meta-ti][dunfell][PATCH 05/11] ti-graphics: Add AM62x GPU (AXE1-16M) support v4
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 05/11] ti-graphics: Add AM62x GPU (AXE1-16M) support v4 Ryan Eatmon
@ 2022-03-22 16:38 ` Etheridge, Darren
0 siblings, 0 replies; 17+ messages in thread
From: Etheridge, Darren @ 2022-03-22 16:38 UTC (permalink / raw)
To: reatmon, Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko,
meta-ti
Ryan,
On 3/22/2022 11:25 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
> From: Krunal Bhargav <k-bhargav@ti.com>
>
> Signed-off-by: Krunal Bhargav <k-bhargav@ti.com>
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> conf/machine/am62xx-evm.conf | 2 +
> .../ti-img-rogue-driver_1.13.5776728.bb | 40 ------------------
> .../ti-img-rogue-driver_1.15.6133109.bb | 42 +++++++++++++++++++
> ...bb => ti-img-rogue-umlibs_1.15.6133109.bb} | 17 ++++----
> 4 files changed, 53 insertions(+), 48 deletions(-)
> delete mode 100644 recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
> create mode 100644 recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> rename recipes-graphics/libgles/{ti-img-rogue-umlibs_1.13.5776728.bb => ti-img-rogue-umlibs_1.15.6133109.bb} (77%)
>
This will break GPU on j721e, Drop this patch completely and I'll send
a patch that will enable ddk 1.15 on all k3 platforms in a little while.
> diff --git a/conf/machine/am62xx-evm.conf b/conf/machine/am62xx-evm.conf
> index 600abb58..086e40e4 100644
> --- a/conf/machine/am62xx-evm.conf
> +++ b/conf/machine/am62xx-evm.conf
> @@ -4,6 +4,8 @@
>
> require conf/machine/include/am62xx.inc
>
> +MACHINE_FEATURES += "gpu"
> +
> KERNEL_DEVICETREE = " \
> ti/k3-am625-sk.dtb \
> ti/k3-am625-sk-lpmdemo.dtb \
> diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
> deleted file mode 100644
> index a05de0f2..00000000
> --- a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
> +++ /dev/null
> @@ -1,40 +0,0 @@
> -DESCRIPTION = "Kernel drivers for the PowerVR Rogue GPU found in the TI SoCs"
> -HOMEPAGE = "http://git.ti.com/graphics/ti-img-rogue-driver"
> -LICENSE = "MIT | GPLv2"
> -LIC_FILES_CHKSUM = "file://README;beginline=14;endline=19;md5=0403c7dea01a2b8232261e805325fac2"
> -
> -inherit module features_check
> -
> -REQUIRED_MACHINE_FEATURES = "gpu"
> -
> -MACHINE_KERNEL_PR_append = "b"
> -PR = "${MACHINE_KERNEL_PR}"
> -
> -PACKAGE_ARCH = "${MACHINE_ARCH}"
> -COMPATIBLE_MACHINE = "j7"
> -
> -DEPENDS = "virtual/kernel"
> -
> -PROVIDES = "virtual/gpudriver"
> -
> -BRANCH = "1.13-5776728/linux-k5.10"
> -
> -SRC_URI = " \
> - git://git.ti.com/graphics/ti-img-rogue-driver.git;branch=${BRANCH} \
> - file://0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch \
> -"
> -
> -S = "${WORKDIR}/git"
> -
> -SRCREV = "35a25875ae8738f82c7cabc6b077ef992b0cca84"
> -
> -PVR_SOC = "j721e_linux"
> -PVR_BVNC = "22.104.208.318"
> -PVR_BUILD = "release"
> -PVR_WS = "wayland"
> -
> -EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${PVR_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${PVR_SOC} WINDOW_SYSTEM=${PVR_WS}'
> -
> -do_install() {
> - make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${PVR_SOC}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D}${root_prefix} PREFIX=${STAGING_DIR_HOST} modules_install
> -}
> diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> new file mode 100644
> index 00000000..0dfc50ec
> --- /dev/null
> +++ b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> @@ -0,0 +1,42 @@
> +DESCRIPTION = "Kernel drivers for the PowerVR Rogue GPU found in the TI SoCs"
> +HOMEPAGE = "https://bitbucket.itg.ti.com/scm/lcpd-priv-sdk/rogue_km"
> +LICENSE = "MIT | GPLv2"
> +LIC_FILES_CHKSUM = "file://README;beginline=14;endline=19;md5=0403c7dea01a2b8232261e805325fac2"
> +
> +inherit module features_check
> +
> +REQUIRED_MACHINE_FEATURES = "gpu"
> +
> +MACHINE_KERNEL_PR_append = "a"
> +PR = "${MACHINE_KERNEL_PR}"
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +COMPATIBLE_MACHINE = "j7|am62xx"
> +
> +DEPENDS = "virtual/kernel"
> +
> +PROVIDES = "virtual/gpudriver"
> +
> +BRANCH = "am62xx-wakeup"
> +
> +SRC_URI = " \
> + git://git@bitbucket.itg.ti.com/lcpd-priv-sdk/rogue_km.git;protocol=ssh;branch=${BRANCH} \
> + file://0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch \
> +"
> +
> +S = "${WORKDIR}/git"
> +
> +SRCREV = "438ff717ff6d46754fce1e10c6d3a3828cff77c9"
> +
> +TARGET_PRODUCT_j7 = "j721e_linux"
> +TARGET_PRODUCT_am62xx = "am62_linux"
> +TARGET_BVNC_j7 = "22.104.208.318"
> +TARGET_BVNC_am62xx = "33.15.11.3"
> +PVR_BUILD = "release"
> +PVR_WS = "wayland"
> +
> +EXTRA_OEMAKE += 'KERNELDIR="${STAGING_KERNEL_DIR}" RGX_BVNC=${TARGET_BVNC} BUILD=${PVR_BUILD} PVR_BUILD_DIR=${TARGET_PRODUCT} WINDOW_SYSTEM=${PVR_WS}'
> +
> +do_install() {
> + make -C ${STAGING_KERNEL_DIR} M=${B}/binary_${TARGET_PRODUCT}_${PVR_WS}_${PVR_BUILD}/target_aarch64/kbuild INSTALL_MOD_PATH=${D}${root_prefix} PREFIX=${STAGING_DIR_HOST} modules_install
> +}
> diff --git a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.15.6133109.bb
> similarity index 77%
> rename from recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb
> rename to recipes-graphics/libgles/ti-img-rogue-umlibs_1.15.6133109.bb
> index 5194015e..611cbabe 100644
> --- a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.13.5776728.bb
> +++ b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.15.6133109.bb
> @@ -1,5 +1,5 @@
> DESCRIPTION = "Userspace libraries for PowerVR Rogue GPU on TI SoCs"
> -HOMEPAGE = "http://git.ti.com/graphics/ti-img-rogue-umlibs"
> +HOMEPAGE = "https://bitbucket.itg.ti.com/scm/lcpd-priv-sdk/rogue_umlibs.git"
> LICENSE = "TI-TFL"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=7232b98c1c58f99e3baa03de5207e76f"
>
> @@ -8,17 +8,18 @@ inherit features_check
> REQUIRED_MACHINE_FEATURES = "gpu"
>
> PACKAGE_ARCH = "${MACHINE_ARCH}"
> -COMPATIBLE_MACHINE = "j7"
> +COMPATIBLE_MACHINE = "j7|am62xx"
>
> -PR = "r3"
> +PR = "r1"
>
> -BRANCH = "linuxws/dunfell/k5.10/${PV}"
> +BRANCH = "am62xx-wakeup"
>
> -SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-umlibs.git;branch=${BRANCH}"
> +SRC_URI = "git://git@bitbucket.itg.ti.com/lcpd-priv-sdk/rogue_umlibs.git;protocol=ssh;branch=${BRANCH}"
>
> -SRCREV = "5ef38353c38d921a65ea6df75c7b6ce710b66034"
> +SRCREV = "4de3317c83c9f5a3681bf3660527673f3226e401"
>
> -PVR_SOC ?= "j721e_linux"
> +TARGET_PRODUCT_j7 = "j721e_linux"
> +TARGET_PRODUCT_am62xx = "am62_linux"
> PVR_BUILD ?= "release"
> PVR_WS = "wayland"
>
> @@ -50,7 +51,7 @@ RRECOMMENDS_${PN} += "ti-img-rogue-driver"
> S = "${WORKDIR}/git"
>
> do_install () {
> - oe_runmake install DESTDIR=${D} TARGET_PRODUCT=${PVR_SOC} BUILD=${PVR_BUILD} WINDOW_SYSTEM=${PVR_WS}
> + oe_runmake install DESTDIR=${D} TARGET_PRODUCT=${TARGET_PRODUCT} BUILD=${PVR_BUILD} WINDOW_SYSTEM=${PVR_WS}
> chown -R root:root ${D}
> }
>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#14520): https://lists.yoctoproject.org/g/meta-ti/message/14520
> Mute This Topic: https://lists.yoctoproject.org/mt/89956122/6759696
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [detheridge@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* [meta-ti][dunfell][PATCH 06/11] recipes-bsp: lpm-demo: Introduce low power mode demo package
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (4 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 05/11] ti-graphics: Add AM62x GPU (AXE1-16M) support v4 Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 17:59 ` Denys Dmytriyenko
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 07/11] recipes-bsp: tifs-lpm-stub: Introduce new recipe Ryan Eatmon
` (5 subsequent siblings)
11 siblings, 1 reply; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nikhil Devshatwar <nikhil.nd@ti.com>
On am62xx-evm, for low power validation, the system boot using
an initramfs.
Package the tisdk-tiny-image.cpio file in the /boot of the
default filesystem to enable the demo.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-bsp/lpm-demo/files/GPL-2 | 340 +++++++++++++++++++++++++++
recipes-bsp/lpm-demo/lpm-demo_1.0.bb | 28 +++
2 files changed, 368 insertions(+)
create mode 100644 recipes-bsp/lpm-demo/files/GPL-2
create mode 100644 recipes-bsp/lpm-demo/lpm-demo_1.0.bb
diff --git a/recipes-bsp/lpm-demo/files/GPL-2 b/recipes-bsp/lpm-demo/files/GPL-2
new file mode 100644
index 00000000..d60c31a9
--- /dev/null
+++ b/recipes-bsp/lpm-demo/files/GPL-2
@@ -0,0 +1,340 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users. This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it. (Some other Free Software Foundation software is covered by
+the GNU Library General Public License instead.) You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+ To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have. You must make sure that they, too, receive or can get the
+source code. And you must show them these terms so they know their
+rights.
+
+ We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+ Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software. If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+ Finally, any free program is threatened constantly by software
+patents. We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary. To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+\f
+ GNU GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License. The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language. (Hereinafter, translation is included without limitation in
+the term "modification".) Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+ 1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+ 2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) You must cause the modified files to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ b) You must cause any work that you distribute or publish, that in
+ whole or in part contains or is derived from the Program or any
+ part thereof, to be licensed as a whole at no charge to all third
+ parties under the terms of this License.
+
+ c) If the modified program normally reads commands interactively
+ when run, you must cause it, when started running for such
+ interactive use in the most ordinary way, to print or display an
+ announcement including an appropriate copyright notice and a
+ notice that there is no warranty (or else, saying that you provide
+ a warranty) and that users may redistribute the program under
+ these conditions, and telling the user how to view a copy of this
+ License. (Exception: if the Program itself is interactive but
+ does not normally print such an announcement, your work based on
+ the Program is not required to print an announcement.)
+\f
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+ a) Accompany it with the complete corresponding machine-readable
+ source code, which must be distributed under the terms of Sections
+ 1 and 2 above on a medium customarily used for software interchange; or,
+
+ b) Accompany it with a written offer, valid for at least three
+ years, to give any third party, for a charge no more than your
+ cost of physically performing source distribution, a complete
+ machine-readable copy of the corresponding source code, to be
+ distributed under the terms of Sections 1 and 2 above on a medium
+ customarily used for software interchange; or,
+
+ c) Accompany it with the information you received as to the offer
+ to distribute corresponding source code. (This alternative is
+ allowed only for noncommercial distribution and only if you
+ received the program in object code or executable form with such
+ an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it. For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable. However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+\f
+ 4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License. Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+ 5. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Program or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+ 6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+ 7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all. For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+\f
+ 8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded. In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+ 9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation. If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+ 10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission. For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this. Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+ NO WARRANTY
+
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+\f
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+ Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary. Here is a sample; alter the names:
+
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+ <signature of Ty Coon>, 1 April 1989
+ Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Library General
+Public License instead of this License.
diff --git a/recipes-bsp/lpm-demo/lpm-demo_1.0.bb b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
new file mode 100644
index 00000000..56b04d56
--- /dev/null
+++ b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
@@ -0,0 +1,28 @@
+SUMMARY = "Low power mode demo"
+LICENSE = "GPLv2"
+LIC_FILES_CHKSUM = "file://GPL-2;md5=94d55d512a9ba36caa9b7df079bae19f"
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_MACHINE = "am62xx-evm"
+
+FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
+S = "${WORKDIR}"
+
+# We need to have the license file from some source. In this case, there
+# is no source. Hence pointing to the license file only
+SRC_URI = "file://GPL-2"
+
+LPM_RAMFS_IMAGE ?= "tisdk-tiny-image"
+
+do_install() {
+ install -d ${D}/boot
+ if [ -f ${DEPLOY_DIR_IMAGE}/${LPM_RAMFS_IMAGE}-${MACHINE}.cpio ]; then
+ install -m 0644 ${DEPLOY_DIR_IMAGE}/${LPM_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
+ else
+ bberror "Could not find LPM ramfs image (${LPM_RAMFS_IMAGE}-${MACHINE}.cpio) in deploy dir!"
+ fi
+}
+
+do_install[depends] = "${LPM_RAMFS_IMAGE}:do_image_complete"
+
+FILES_${PN} = "/boot"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* Re: [meta-ti][dunfell][PATCH 06/11] recipes-bsp: lpm-demo: Introduce low power mode demo package
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 06/11] recipes-bsp: lpm-demo: Introduce low power mode demo package Ryan Eatmon
@ 2022-03-22 17:59 ` Denys Dmytriyenko
2022-03-22 18:04 ` Ryan Eatmon
0 siblings, 1 reply; 17+ messages in thread
From: Denys Dmytriyenko @ 2022-03-22 17:59 UTC (permalink / raw)
To: reatmon; +Cc: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
On Tue, Mar 22, 2022 at 11:25:23AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
> From: Nikhil Devshatwar <nikhil.nd@ti.com>
>
> On am62xx-evm, for low power validation, the system boot using
> an initramfs.
>
> Package the tisdk-tiny-image.cpio file in the /boot of the
> default filesystem to enable the demo.
>
> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> recipes-bsp/lpm-demo/files/GPL-2 | 340 +++++++++++++++++++++++++++
> recipes-bsp/lpm-demo/lpm-demo_1.0.bb | 28 +++
> 2 files changed, 368 insertions(+)
> create mode 100644 recipes-bsp/lpm-demo/files/GPL-2
> create mode 100644 recipes-bsp/lpm-demo/lpm-demo_1.0.bb
>
> diff --git a/recipes-bsp/lpm-demo/files/GPL-2 b/recipes-bsp/lpm-demo/files/GPL-2
> new file mode 100644
> index 00000000..d60c31a9
> --- /dev/null
> +++ b/recipes-bsp/lpm-demo/files/GPL-2
<snip>
> diff --git a/recipes-bsp/lpm-demo/lpm-demo_1.0.bb b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
> new file mode 100644
> index 00000000..56b04d56
> --- /dev/null
> +++ b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
> @@ -0,0 +1,28 @@
> +SUMMARY = "Low power mode demo"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://GPL-2;md5=94d55d512a9ba36caa9b7df079bae19f"
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +COMPATIBLE_MACHINE = "am62xx-evm"
> +
> +FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
> +S = "${WORKDIR}"
> +
> +# We need to have the license file from some source. In this case, there
> +# is no source. Hence pointing to the license file only
> +SRC_URI = "file://GPL-2"
That's an incorrect way of doing it.
https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/busybox/busybox-inittab_1.35.0.bb#n3
Also, default license for OpenEmbedded metadata is MIT, not GPLv2. Any
specific reason for the change?
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-tisdk/tisdk-readme/tisdk-readme.bb#n3
> +LPM_RAMFS_IMAGE ?= "tisdk-tiny-image"
> +
> +do_install() {
> + install -d ${D}/boot
> + if [ -f ${DEPLOY_DIR_IMAGE}/${LPM_RAMFS_IMAGE}-${MACHINE}.cpio ]; then
> + install -m 0644 ${DEPLOY_DIR_IMAGE}/${LPM_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> + else
> + bberror "Could not find LPM ramfs image (${LPM_RAMFS_IMAGE}-${MACHINE}.cpio) in deploy dir!"
> + fi
> +}
> +
> +do_install[depends] = "${LPM_RAMFS_IMAGE}:do_image_complete"
> +
> +FILES_${PN} = "/boot"
> --
> 2.17.1
>
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [meta-ti][dunfell][PATCH 06/11] recipes-bsp: lpm-demo: Introduce low power mode demo package
2022-03-22 17:59 ` Denys Dmytriyenko
@ 2022-03-22 18:04 ` Ryan Eatmon
0 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 18:04 UTC (permalink / raw)
To: Denys Dmytriyenko, nikhil.nd
Cc: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
On 3/22/2022 12:59, Denys Dmytriyenko wrote:
> On Tue, Mar 22, 2022 at 11:25:23AM -0500, Ryan Eatmon via lists.yoctoproject.org wrote:
>> From: Nikhil Devshatwar <nikhil.nd@ti.com>
>>
>> On am62xx-evm, for low power validation, the system boot using
>> an initramfs.
>>
>> Package the tisdk-tiny-image.cpio file in the /boot of the
>> default filesystem to enable the demo.
>>
>> Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
>> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
>> ---
>> recipes-bsp/lpm-demo/files/GPL-2 | 340 +++++++++++++++++++++++++++
>> recipes-bsp/lpm-demo/lpm-demo_1.0.bb | 28 +++
>> 2 files changed, 368 insertions(+)
>> create mode 100644 recipes-bsp/lpm-demo/files/GPL-2
>> create mode 100644 recipes-bsp/lpm-demo/lpm-demo_1.0.bb
>>
>> diff --git a/recipes-bsp/lpm-demo/files/GPL-2 b/recipes-bsp/lpm-demo/files/GPL-2
>> new file mode 100644
>> index 00000000..d60c31a9
>> --- /dev/null
>> +++ b/recipes-bsp/lpm-demo/files/GPL-2
>
> <snip>
>
>> diff --git a/recipes-bsp/lpm-demo/lpm-demo_1.0.bb b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
>> new file mode 100644
>> index 00000000..56b04d56
>> --- /dev/null
>> +++ b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
>> @@ -0,0 +1,28 @@
>> +SUMMARY = "Low power mode demo"
>> +LICENSE = "GPLv2"
>> +LIC_FILES_CHKSUM = "file://GPL-2;md5=94d55d512a9ba36caa9b7df079bae19f"
>> +
>> +PACKAGE_ARCH = "${MACHINE_ARCH}"
>> +COMPATIBLE_MACHINE = "am62xx-evm"
>> +
>> +FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
>> +S = "${WORKDIR}"
>> +
>> +# We need to have the license file from some source. In this case, there
>> +# is no source. Hence pointing to the license file only
>> +SRC_URI = "file://GPL-2"
>
> That's an incorrect way of doing it.
> https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/busybox/busybox-inittab_1.35.0.bb#n3
>
> Also, default license for OpenEmbedded metadata is MIT, not GPLv2. Any
> specific reason for the change?
> https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-tisdk/tisdk-readme/tisdk-readme.bb#n3
Copying Nikhil, the original author to answer those questions.
>
>> +LPM_RAMFS_IMAGE ?= "tisdk-tiny-image"
>> +
>> +do_install() {
>> + install -d ${D}/boot
>> + if [ -f ${DEPLOY_DIR_IMAGE}/${LPM_RAMFS_IMAGE}-${MACHINE}.cpio ]; then
>> + install -m 0644 ${DEPLOY_DIR_IMAGE}/${LPM_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
>> + else
>> + bberror "Could not find LPM ramfs image (${LPM_RAMFS_IMAGE}-${MACHINE}.cpio) in deploy dir!"
>> + fi
>> +}
>> +
>> +do_install[depends] = "${LPM_RAMFS_IMAGE}:do_image_complete"
>> +
>> +FILES_${PN} = "/boot"
>> --
>> 2.17.1
>>
>
--
Ryan Eatmon
reatmon@ti.com
^ permalink raw reply [flat|nested] 17+ messages in thread
* [meta-ti][dunfell][PATCH 07/11] recipes-bsp: tifs-lpm-stub: Introduce new recipe
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (5 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 06/11] recipes-bsp: lpm-demo: Introduce low power mode demo package Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 08/11] ti-rtos: Add support for AM62x M4F Ryan Eatmon
` (4 subsequent siblings)
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nikhil Devshatwar <nikhil.nd@ti.com>
This firmware stub is required by the TI foundational security
software while transitioning to low power mode.
Add a recipe for this compatible with am62xx-evm
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
.../tifs-lpm-stub/tifs-lpm-stub_git.bb | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
create mode 100644 recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
diff --git a/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb b/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
new file mode 100644
index 00000000..bc341035
--- /dev/null
+++ b/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
@@ -0,0 +1,21 @@
+SUMMARY = "TI Foundational security Low Power Management Stub"
+
+require recipes-bsp/ti-linux-fw/ti-linux-fw.inc
+
+LICENSE = "TI-TFL"
+LIC_FILES_CHKSUM = "file://LICENCE.ti-keystone;md5=3a86335d32864b0bef996bee26cc0f2c"
+
+PV = "v2021.09a"
+
+COMPATIBLE_MACHINE = "am62xx-evm"
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+S = "${WORKDIR}/git"
+TARGET = "ti-fs-stub-firmware-am62x-gp.signed.bin"
+
+do_install() {
+ install -d ${D}${base_libdir}/firmware/ti-sysfw/
+ install -m 0644 ${S}/ti-sysfw/${TARGET} ${D}${base_libdir}/firmware/ti-sysfw/${TARGET}
+}
+
+FILES_${PN} = "${base_libdir}/firmware"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 08/11] ti-rtos: Add support for AM62x M4F
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (6 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 07/11] recipes-bsp: tifs-lpm-stub: Introduce new recipe Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 09/11] ti-rtos: Fix AM62x R5F DM FW paths Ryan Eatmon
` (3 subsequent siblings)
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Hari Nagalla <hnagalla@ti.com>
Add M4F FW support for AM62x SoC.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 23 +++++++++++++++++-----
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 4cd08a36..43119f03 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -19,7 +19,7 @@ PLAT_SFX_j7200-hs-evm = "j7200"
PLAT_SFX_j721s2-evm = "j721s2"
PLAT_SFX_am65xx = "am65xx"
PLAT_SFX_am64xx = "am64xx"
-PLAT_SFX_am62xx-evm = "am62x"
+PLAT_SFX_am62xx = "am62xx"
FILESEXTRAPATHS_prepend := "${METATIBASE}/recipes-bsp/ti-sci-fw/files/:"
require recipes-bsp/ti-linux-fw/ti-linux-fw.inc
@@ -78,6 +78,13 @@ do_install_prepend_am64xx() {
)
}
+# Update the am62xx ipc binaries to be consistent with other platforms
+do_install_prepend_am62xx() {
+ ( cd ${RTOS_IPC_FW_DIR}; \
+ mv am62-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f; \
+ )
+}
+
#Install all R5 & DSP ipc echo test binaries in lib/firmware/pdk-ipc, with softlinks up a level
do_install() {
@@ -155,11 +162,9 @@ do_install_am64xx() {
install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
}
-do_install_am62xx-evm() {
+do_install_am62xx() {
install -d ${LEGACY_IPC_FW_DIR}
- # No specific firmware to install till M4F comes online
- # DM Firmware
- install -m 0644 ${RTOS_DM_FW_DIR}/ipc_echo_testb_mcu1_0_release_strip.xer5f ${LEGACY_DM_FW_DIR}
+ install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
}
# Set up names for the firmwares
@@ -175,6 +180,9 @@ ALTERNATIVE_${PN}_am64xx = "\
am64-main-r5f1_1-fw \
am64-mcu-m4f0_0-fw \
"
+ALTERNATIVE_${PN}_am62xx = "\
+ am62-mcu-m4f0_0-fw \
+ "
ALTERNATIVE_${PN}_j7 = "\
j7-mcu-r5f0_0-fw \
@@ -227,6 +235,7 @@ TARGET_MAIN_R5FSS0_1_am64xx = "am64-main-r5f0_1-fw"
TARGET_MAIN_R5FSS1_0_am64xx = "am64-main-r5f1_0-fw"
TARGET_MAIN_R5FSS1_1_am64xx = "am64-main-r5f1_1-fw"
TARGET_MCU_M4FSS0_0_am64xx = "am64-mcu-m4f0_0-fw"
+TARGET_MCU_M4FSS0_0_am62xx = "am62-mcu-m4f0_0-fw"
TARGET_MCU_R5FSS0_0_j7 = "j7-mcu-r5f0_0-fw"
TARGET_MCU_R5FSS0_1_j7 = "j7-mcu-r5f0_1-fw"
@@ -268,6 +277,8 @@ ALTERNATIVE_LINK_NAME[am64-main-r5f1_0-fw] = "${base_libdir}/firmware/${TARGET_M
ALTERNATIVE_LINK_NAME[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS1_1}"
ALTERNATIVE_LINK_NAME[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_M4FSS0_0}"
+ALTERNATIVE_LINK_NAME[am62-mcu-m4f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_M4FSS0_0}"
+
ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
@@ -305,6 +316,8 @@ ALTERNATIVE_TARGET[am64-main-r5f1_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
ALTERNATIVE_TARGET[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f"
ALTERNATIVE_TARGET[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[am62-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f"
+
ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
ALTERNATIVE_TARGET[j7-mcu-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = "${base_libdir}/firmware/ethfw/app_remoteswitchcfg_server_strip.xer5f"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 09/11] ti-rtos: Fix AM62x R5F DM FW paths
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (7 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 08/11] ti-rtos: Add support for AM62x M4F Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 10/11] ti-rtos: Fix AM62x Fix MCU core numbers Ryan Eatmon
` (2 subsequent siblings)
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index 43119f03..ecf54123 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -165,6 +165,8 @@ do_install_am64xx() {
do_install_am62xx() {
install -d ${LEGACY_IPC_FW_DIR}
install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
+ # DM Firmware
+ install -m 0644 ${RTOS_DM_FW_DIR}/ipc_echo_testb_mcu1_0_release_strip.xer5f ${LEGACY_DM_FW_DIR}
}
# Set up names for the firmwares
@@ -182,6 +184,7 @@ ALTERNATIVE_${PN}_am64xx = "\
"
ALTERNATIVE_${PN}_am62xx = "\
am62-mcu-m4f0_0-fw \
+ am62xx-main-r5f0_0-fw \
"
ALTERNATIVE_${PN}_j7 = "\
@@ -236,6 +239,7 @@ TARGET_MAIN_R5FSS1_0_am64xx = "am64-main-r5f1_0-fw"
TARGET_MAIN_R5FSS1_1_am64xx = "am64-main-r5f1_1-fw"
TARGET_MCU_M4FSS0_0_am64xx = "am64-mcu-m4f0_0-fw"
TARGET_MCU_M4FSS0_0_am62xx = "am62-mcu-m4f0_0-fw"
+TARGET_MAIN_R5FSS0_0_am62xx = "am62xx-main-r5f0_0-fw"
TARGET_MCU_R5FSS0_0_j7 = "j7-mcu-r5f0_0-fw"
TARGET_MCU_R5FSS0_1_j7 = "j7-mcu-r5f0_1-fw"
@@ -278,6 +282,7 @@ ALTERNATIVE_LINK_NAME[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/${TARGET_M
ALTERNATIVE_LINK_NAME[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_M4FSS0_0}"
ALTERNATIVE_LINK_NAME[am62-mcu-m4f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_M4FSS0_0}"
+ALTERNATIVE_LINK_NAME[am62xx-main-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_0}"
ALTERNATIVE_LINK_NAME[j7-mcu-r5f0_1-fw] = "${base_libdir}/firmware/${TARGET_MCU_R5FSS0_1}"
@@ -317,6 +322,7 @@ ALTERNATIVE_TARGET[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
ALTERNATIVE_TARGET[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f"
ALTERNATIVE_TARGET[am62-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[am62xx-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
ALTERNATIVE_TARGET[j7-mcu-r5f0_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 10/11] ti-rtos: Fix AM62x Fix MCU core numbers
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (8 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 09/11] ti-rtos: Fix AM62x R5F DM FW paths Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 11/11] recipes-bsp: lpm-demo: Fix build errors with clean task Ryan Eatmon
2022-03-22 20:43 ` [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Nishanth Menon
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
index ecf54123..fd2b08ae 100644
--- a/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
+++ b/recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb
@@ -81,7 +81,7 @@ do_install_prepend_am64xx() {
# Update the am62xx ipc binaries to be consistent with other platforms
do_install_prepend_am62xx() {
( cd ${RTOS_IPC_FW_DIR}; \
- mv am62-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f; \
+ mv am62-mcu-m4f0_0-fw ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f; \
)
}
@@ -164,7 +164,7 @@ do_install_am64xx() {
do_install_am62xx() {
install -d ${LEGACY_IPC_FW_DIR}
- install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
+ install -m 0644 ${RTOS_IPC_FW_DIR}/ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f ${LEGACY_IPC_FW_DIR}
# DM Firmware
install -m 0644 ${RTOS_DM_FW_DIR}/ipc_echo_testb_mcu1_0_release_strip.xer5f ${LEGACY_DM_FW_DIR}
}
@@ -321,7 +321,7 @@ ALTERNATIVE_TARGET[am64-main-r5f1_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_e
ALTERNATIVE_TARGET[am64-main-r5f1_1-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_1_release_strip.xer5f"
ALTERNATIVE_TARGET[am64-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu3_0_release_strip.xer5f"
-ALTERNATIVE_TARGET[am62-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu1_0_release_strip.xer5f"
+ALTERNATIVE_TARGET[am62-mcu-m4f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_baremetal_test_mcu2_0_release_strip.xer5f"
ALTERNATIVE_TARGET[am62xx-main-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_strip.xer5f"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* [meta-ti][dunfell][PATCH 11/11] recipes-bsp: lpm-demo: Fix build errors with clean task
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (9 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 10/11] ti-rtos: Fix AM62x Fix MCU core numbers Ryan Eatmon
@ 2022-03-22 16:25 ` Ryan Eatmon
2022-03-22 20:43 ` [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Nishanth Menon
11 siblings, 0 replies; 17+ messages in thread
From: Ryan Eatmon @ 2022-03-22 16:25 UTC (permalink / raw)
To: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
From: Nikhil Devshatwar <nikhil.nd@ti.com>
lpm-demo and tifs-lpm-demo packages only install certain files.
The build breaks when rebuilding incrementally.
It fails the do_configure task.
Fix this by adding CLEANBROKEN in those recipes.
Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
recipes-bsp/lpm-demo/lpm-demo_1.0.bb | 2 ++
recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb | 1 +
2 files changed, 3 insertions(+)
diff --git a/recipes-bsp/lpm-demo/lpm-demo_1.0.bb b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
index 56b04d56..244d7a55 100644
--- a/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
+++ b/recipes-bsp/lpm-demo/lpm-demo_1.0.bb
@@ -8,6 +8,8 @@ COMPATIBLE_MACHINE = "am62xx-evm"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
S = "${WORKDIR}"
+CLEANBROKEN = "1"
+
# We need to have the license file from some source. In this case, there
# is no source. Hence pointing to the license file only
SRC_URI = "file://GPL-2"
diff --git a/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb b/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
index bc341035..e3ba67be 100644
--- a/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
+++ b/recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
@@ -9,6 +9,7 @@ PV = "v2021.09a"
COMPATIBLE_MACHINE = "am62xx-evm"
PACKAGE_ARCH = "${MACHINE_ARCH}"
+CLEANBROKEN = "1"
S = "${WORKDIR}/git"
TARGET = "ti-fs-stub-firmware-am62x-gp.signed.bin"
--
2.17.1
^ permalink raw reply related [flat|nested] 17+ messages in thread* Re: [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx
2022-03-22 16:25 [meta-ti][dunfell][PATCH 00/11] Adding support for am62xx Ryan Eatmon
` (10 preceding siblings ...)
2022-03-22 16:25 ` [meta-ti][dunfell][PATCH 11/11] recipes-bsp: lpm-demo: Fix build errors with clean task Ryan Eatmon
@ 2022-03-22 20:43 ` Nishanth Menon
11 siblings, 0 replies; 17+ messages in thread
From: Nishanth Menon @ 2022-03-22 20:43 UTC (permalink / raw)
To: reatmon; +Cc: Yogesh Siraswar, Praneeth Bajjuri, Denys Dmytriyenko, meta-ti
On 11:25-20220322, Ryan Eatmon via lists.yoctoproject.org wrote:
> These patches add initial recipe support for am62xx.
>
> Hari Nagalla (3):
> ti-rtos: Add support for AM62x M4F
> ti-rtos: Fix AM62x R5F DM FW paths
> ti-rtos: Fix AM62x Fix MCU core numbers
>
> Krunal Bhargav (1):
> ti-graphics: Add AM62x GPU (AXE1-16M) support v4
>
> Nikhil Devshatwar (3):
> recipes-bsp: lpm-demo: Introduce low power mode demo package
> recipes-bsp: tifs-lpm-stub: Introduce new recipe
> recipes-bsp: lpm-demo: Fix build errors with clean task
>
> Nishanth Menon (4):
> machine: Add am62xx evm configuration
> recipes-ti: ti-rtos-bin: Add AM62x binaries
> recipes: Pick up correct image and build DM to boot images
> HACK: recipes-ti: ti-rtos-metadata: Make am62x point to am64x
>
> conf/machine/am62xx-evm-k3r5.conf | 11 +
> conf/machine/am62xx-evm.conf | 15 +
> conf/machine/include/am62xx.inc | 17 +
> recipes-bsp/lpm-demo/files/GPL-2 | 340 ++++++++++++++++++
> recipes-bsp/lpm-demo/lpm-demo_1.0.bb | 30 ++
> .../ti-img-rogue-driver_1.13.5776728.bb | 40 ---
> .../ti-img-rogue-driver_1.15.6133109.bb | 42 +++
> recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb | 18 +
> .../tifs-lpm-stub/tifs-lpm-stub_git.bb | 22 ++
> recipes-bsp/u-boot/u-boot-ti.inc | 7 +
> ...bb => ti-img-rogue-umlibs_1.15.6133109.bb} | 17 +-
> recipes-ti/ti-rtos-bin/ti-rtos-firmware.bb | 37 ++
> recipes-ti/ti-rtos-bin/ti-rtos-metadata.bb | 1 +
> 13 files changed, 549 insertions(+), 48 deletions(-)
> create mode 100644 conf/machine/am62xx-evm-k3r5.conf
> create mode 100644 conf/machine/am62xx-evm.conf
> create mode 100644 conf/machine/include/am62xx.inc
> create mode 100644 recipes-bsp/lpm-demo/files/GPL-2
> create mode 100644 recipes-bsp/lpm-demo/lpm-demo_1.0.bb
> delete mode 100644 recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.13.5776728.bb
> create mode 100644 recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.15.6133109.bb
> create mode 100644 recipes-bsp/tifs-lpm-stub/tifs-lpm-stub_git.bb
> rename recipes-graphics/libgles/{ti-img-rogue-umlibs_1.13.5776728.bb => ti-img-rogue-umlibs_1.15.6133109.bb} (77%)
NAK to the series.
a) patches need to be cleaned up - squashed etc.
b) lpm-demo binary should probably belong to meta-arago instead
of meta-ti. meta-ti should be a bsp layer, not a distro.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
^ permalink raw reply [flat|nested] 17+ messages in thread