ti-crypto-examples: Remove ti-crypto-examples
PATCH 1/7 ti-crypto-examples: Remove ti-crypto-examples
These examples have not been updated in a long time and are not correct anymore. Remove this.
--- .../conf/distro/include/arago-source-ipk.inc | 3 -- .../packagegroup-arago-tisdk-crypto.bb | 1 - .../Makefile_ti-crypto-examples | 24 --------------- .../ti-tisdk-makefile_1.0.bb | 3 -- .../ti-crypto-examples_git.bb | 30 ------------------- 5 files changed, 61 deletions(-) delete mode 100644 meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_ti-crypto-examples delete mode 100644 meta-arago-extras/recipes-core/ti-crypto-examples/ti-crypto-examples_git.bb
meta-arago-distro/conf/distro/include/arago-source-ipk.inc +0 -3
@@ -46,9 +46,6 @@ SRCIPK_INSTALL_DIR:pn-ti-tisdk-licenses ?= "docs/licenses" CREATE_SRCIPK:pn-matrix-gui ?= "1" SRCIPK_INSTALL_DIR:pn-matrix-gui ?= "example-applications/${PN}-${PV}" -CREATE_SRCIPK:pn-ti-crypto-examples ?= "1" -SRCIPK_INSTALL_DIR:pn-ti-crypto-examples ?= "example-applications/${PN}-${PV}" - CREATE_SRCIPK:pn-qml-carinfo ?= "1" SRCIPK_INSTALL_DIR:pn-qml-carinfo ?= "example-applications/${PN}-${PV}"
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-crypto.bb +0 -1
@@ -13,7 +13,6 @@ CRYPTO_SUPPORT = "\ openssl-engines \ " -#ti-crypto-examples CRYPTO_SUPPORT:append:ti33x = " cryptodev-module cryptodev-tests" CRYPTO_SUPPORT:append:ti43x = " cryptodev-module cryptodev-tests" CRYPTO_SUPPORT:append:dra7xx = " cryptodev-module cryptodev-tests"
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_ti-crypto-examples deleted +0 -24
@@ -1,24 +0,0 @@ -# ti-crypto-examples build targets -ti-crypto-examples: - @echo ================================= - @echo Building TI Crypto Examples - @echo ================================= - @cd example-applications; cd `find . -maxdepth 1 -type d -name "*ti-crypto-examples*"`; make release - -ti-crypto-examples_clean: - @echo ================================= - @echo Cleaning TI Crypto Examples - @echo ================================= - @cd example-applications; cd `find . -maxdepth 1 -type d -name "*ti-crypto-examples*"`; make clean - -ti-crypto-examples_install: - @echo =================================================== - @echo Installing TI Crypto Examples - Release version - @echo =================================================== - @cd example-applications; cd `find . -maxdepth 1 -type d -name "*ti-crypto-examples*"`; make install - -ti-crypto-examples_install_debug: - @echo ================================================= - @echo Installing TI Crypto Examples - Debug Version - @echo ================================================= - @cd example-applications; cd `find . -maxdepth 1 -type d -name "*ti-crypto-examples*"`; make install_debug
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb +0 -3
@@ -18,7 +18,6 @@ SRC_URI = "\ file://Makefile_u-boot-legacy \ file://Makefile_matrix-gui \ file://Makefile_arm-benchmarks \ - file://Makefile_ti-crypto-examples \ file://Makefile_am-sysinfo \ file://Makefile_av-examples \ file://Makefile_u-boot-spl \
@@ -76,7 +75,6 @@ MAKEFILES = "" # Add device specific make targets MAKEFILES:append:ti33x = " u-boot-spl \ - ti-crypto-examples \ linux-dtbs \ cryptodev \ ti-sgx-ddk-km \
@@ -86,7 +84,6 @@ MAKEFILES:append:ti33x = " u-boot-spl \ pdm-anomaly-detection \ " MAKEFILES:append:ti43x = " u-boot-spl \ - ti-crypto-examples \ linux-dtbs \ cryptodev \ dual-camera-demo \
meta-arago-extras/recipes-core/ti-crypto-examples/ti-crypto-examples_git.bb deleted +0 -30
@@ -1,30 +0,0 @@ -DESCRIPTION = "TI Cryptography Example Applications" -HOMEPAGE = "https://git.ti.com/cgit/arago-project-org/crypto-example-apps/" -LICENSE = "BSD-3-Clause" -LIC_FILES_CHKSUM = "file://AES/aes_256.c;beginline=9;endline=35;md5=8edbb4dee965d2f2eb5ca2822addcae5" -SECTION = "console" -DEPENDS += "openssl" - -PR = "r7" - -BRANCH ?= "master" -SRCREV = "6f4b09fffe970bb6b448369875874e798ef282f6" - -SRC_URI = "git://git.ti.com/git/git/arago-project-org/crypto-example-apps.git;protocol=https;branch=${BRANCH}" - -S = "${WORKDIR}/git" - -do_compile() { - export CROSS_COMPILE=${TARGET_PREFIX} - export CFLAGS='${TARGET_CC_ARCH}' - # build the release version - oe_runmake release -} - -do_install() { - oe_runmake DESTDIR=${D} install -} - -python () { - raise bb.parse.SkipRecipe("skipping ti-crypto-examples") -}
Signature · 1 line
2.37.3
PATCH 2/7 big-data-ipc-demo: Merge include file and rename
The include might have been intended to be used by an TI RTOS build but without this in the roadmap lets merge the include and rename this recipe without the -linux postfix.
---
.../conf/distro/include/arago-source-ipk.inc | 4 +--
...ackagegroup-arago-tisdk-addons-sdk-host.bb | 2 +-
.../packagegroup-arago-tisdk-addons.bb | 2 +-
.../big-data-ipc-demo/big-data-ipc-demo.inc | 30 -------------------
...-linux_git.bb => big-data-ipc-demo_git.bb} | 30 ++++++++++++-------
5 files changed, 24 insertions(+), 44 deletions(-)
delete mode 100644 meta-arago-extras/recipes-apps/big-data-ipc-demo/big-data-ipc-demo.inc
rename meta-arago-extras/recipes-apps/big-data-ipc-demo/{big-data-ipc-demo-linux_git.bb => big-data-ipc-demo_git.bb} (54%)meta-arago-distro/conf/distro/include/arago-source-ipk.inc +2 -2
@@ -361,5 +361,5 @@ SRCIPK_INSTALL_DIR:pn-imglib-c66x ?= "component-sources/imglib_c66x_${PV}" CREATE_SRCIPK:pn-vlib-c66x ?= "1" SRCIPK_INSTALL_DIR:pn-vlib-c66x ?= "component-sources/vlib_c66x_${PV}" -CREATE_SRCIPK:pn-big-data-ipc-demo-linux ?= "1" -SRCIPK_INSTALL_DIR:pn-big-data-ipc-demo-linux ?= "example-applications/${PN}-${PV}" +CREATE_SRCIPK:pn-big-data-ipc-demo ?= "1" +SRCIPK_INSTALL_DIR:pn-big-data-ipc-demo ?= "example-applications/${PN}-${PV}"
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-host.bb +1 -1
@@ -58,7 +58,7 @@ EXTRA_LIBS = "" EXTRA_LIBS:append:omap-a15 = " \ cmem-mod-source \ uio-module-drv-source \ - big-data-ipc-demo-linux-source \ + big-data-ipc-demo-source \ " #EXTRA_LIBS:append:dra7xx = " \
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +1 -1
@@ -108,7 +108,7 @@ EXTRA_PACKAGES:append:omap-a15 = " ti-ipc-examples-linux" EXTRA_PACKAGES:append:omapl138 = " ti-ipc-examples-linux" EXTRA_PACKAGES:append:omap-a15 = " \ - ${@bb.utils.contains('MACHINE_FEATURES','dsp','big-data-ipc-demo-linux big-data-ipc-demo-linux-firmware','',d)} \ + ${@bb.utils.contains('MACHINE_FEATURES','dsp','big-data-ipc-demo big-data-ipc-demo-firmware','',d)} \ " # acontis-atemsys
meta-arago-extras/recipes-apps/big-data-ipc-demo/big-data-ipc-demo.inc deleted +0 -30
@@ -1,30 +0,0 @@ -LICENSE = "BSD-3-Clause" -LIC_FILES_CHKSUM = "file://makefile;beginline=1;endline=31;md5=2f2ea348b98d5cc7807ece7adcc2c43a" - -COMPATIBLE_MACHINE = "omap-a15" -PACKAGE_ARCH = "${MACHINE_ARCH}" - -BIG_DATA_IPC_GIT_URI = "git://git.ti.com/git/processor-sdk/big-data-ipc-examples.git" -BIG_DATA_IPC_GIT_PROTOCOL = "https" -BIG_DATA_IPC_GIT_BRANCH = "master" - -# Below commit ID corresponds to "DEV.BIG_DATA_IPC.01.03.00.00" -BIG_DATA_IPC_SRCREV = "984edb3c69c8a1f51da02e0abcd2201319650894" - -BRANCH = "${BIG_DATA_IPC_GIT_BRANCH}" -SRC_URI = "${BIG_DATA_IPC_GIT_URI};protocol=${BIG_DATA_IPC_GIT_PROTOCOL};branch=${BRANCH}" - -SRCREV = "${BIG_DATA_IPC_SRCREV}" -PV = "01.03.00.00" - -S = "${WORKDIR}/git" - -PLATFORM = "UNKNOWN" -PLATFORM:omap-a15 = "DRA7XX" - -IPC_TARGETS = "" -IPC_TARGETS:omap-a15 = "\ - gnu.targets.arm.A15F="${GCC_ARM_NONE_TOOLCHAIN}" \ - ti.targets.elf.C66="${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x" \ - ti.targets.arm.elf.M4="${M4_TOOLCHAIN_INSTALL_DIR}" \ -"
meta-arago-extras/recipes-apps/big-data-ipc-demo/big-data-ipc-demo_git.bb renamed from meta-arago-extras/recipes-apps/big-data-ipc-demo/big-data-ipc-demo-linux_git.bb +20 -10
@@ -1,7 +1,15 @@ SUMMARY = "TI Big data IPC: Host linux examples" +LICENSE = "BSD-3-Clause" +LIC_FILES_CHKSUM = "file://makefile;beginline=1;endline=31;md5=2f2ea348b98d5cc7807ece7adcc2c43a" -require recipes-ti/includes/ti-paths.inc -require big-data-ipc-demo.inc +SRC_URI = "git://git.ti.com/processor-sdk/big-data-ipc-examples.git;protocol=git;branch=master" +SRCREV = "984edb3c69c8a1f51da02e0abcd2201319650894" +PV = "01.03.00.00" + +S = "${WORKDIR}/git" + +COMPATIBLE_MACHINE = "omap-a15" +PACKAGE_ARCH = "${MACHINE_ARCH}" inherit features_check
@@ -15,30 +23,32 @@ DEPENDS = "ti-ipc \ ti-cgt6x-native \ " +PLATFORM = "UNKNOWN" +PLATFORM:omap-a15 = "DRA7XX" + +require recipes-ti/includes/ti-paths.inc + EXTRA_OEMAKE = "\ PLATFORM=${PLATFORM} \ XDC_INSTALL_DIR="${XDC_INSTALL_DIR}" \ BIOS_INSTALL_DIR="${SYSBIOS_INSTALL_DIR}" \ IPC_INSTALL_DIR="${IPC_INSTALL_DIR}" \ LINUX_SYSROOT_DIR="${STAGING_INCDIR}" \ - ${IPC_TARGETS} \ - JOBS="${PARALLEL_MAKE}" \ + gnu.targets.arm.A15F="${GCC_ARM_NONE_TOOLCHAIN}" \ + ti.targets.elf.C66="${STAGING_DIR_NATIVE}/usr/share/ti/cgt-c6x" \ + ti.targets.arm.elf.M4="${M4_TOOLCHAIN_INSTALL_DIR}" \ " do_create_srcipk:prepend() { - rm -rf host_bios + rm -rf host_bios } do_compile() { - if [ "${PLATFORM}" != "UNKNOWN" ]; then - oe_runmake host_linux - fi + oe_runmake host_linux } do_install() { - if [ "${PLATFORM}" != "UNKNOWN" ]; then oe_runmake EXEC_DIR="${D}${bindir}" install_linux_bin - fi } PACKAGES =+ "${PN}-firmware"
Signature · 1 line
2.37.3
PATCH 3/7 cmem: Remove Makefile_cmem-mod and cmem refrences
In reply to Andrew DavisThe cmem allocator has been deprecated for removal for some time now. Lets remove the kernel module first, then start removing projects that have not migrated to DMA-BUF Heaps yet.
--- .../conf/distro/include/arago-source-ipk.inc | 3 -- ...ackagegroup-arago-tisdk-addons-sdk-host.bb | 2 -- ...kagegroup-arago-tisdk-addons-sdk-target.bb | 5 --- .../packagegroup-arago-tisdk-addons.bb | 2 -- .../recipes-core/packagegroups/ti-test.bb | 2 -- .../ti-tisdk-makefile/Makefile_cmem-mod | 33 ------------------- .../ti-tisdk-makefile_1.0.bb | 3 -- 7 files changed, 50 deletions(-) delete mode 100644 meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_cmem-mod
meta-arago-distro/conf/distro/include/arago-source-ipk.inc +0 -3
@@ -169,9 +169,6 @@ CREATE_SRCIPK:pn-cryptodev-module ?= "1" SRCIPK_INSTALL_DIR:pn-cryptodev-module ?= "board-support/extra-drivers/cryptodev-module-${PV}" SRCIPK_PRESERVE_GIT:pn-cryptodev-module ?= "true" -CREATE_SRCIPK:pn-cmem-mod ?= "1" -SRCIPK_INSTALL_DIR:pn-cmem-mod ?= "board-support/extra-drivers/${PN}-${PV}" - CREATE_SRCIPK:pn-debugss-module-drv ?= "1" SRCIPK_INSTALL_DIR:pn-debugss-module-drv ?= "board-support/extra-drivers/${PN}-${PV}"
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-host.bb +0 -2
@@ -56,7 +56,6 @@ UTILS:append:am64xx = " \ EXTRA_LIBS = "" EXTRA_LIBS:append:omap-a15 = " \ - cmem-mod-source \ uio-module-drv-source \ big-data-ipc-demo-source \ "
@@ -71,7 +70,6 @@ EXTRA_LIBS:append:ti33x = " \ " EXTRA_LIBS:append:ti43x = " \ - cmem-mod-source \ uio-module-drv-source \ "
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +0 -5
@@ -26,11 +26,6 @@ UTILS:append:k3 = "\ " EXTRA_LIBS = "" -EXTRA_LIBS:append:ti43x = "\ - cmem-dev \ - cmem-staticdev \ -" -EXTRA_LIBS:append:omap-a15 = " cmem-dev" EXTRA_LIBS:append:dra7xx = " libulm-dev \ libulm-staticdev \ gdbserver-c6x-dev \
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +0 -2
@@ -80,12 +80,10 @@ UTILS:append:dra7xx = " \ EXTRA_LIBS = "" EXTRA_LIBS:append:omap-a15 = " \ - cmem \ uio-module-drv \ " EXTRA_LIBS:append:ti43x = " \ - cmem \ uio-module-drv \ "
meta-arago-distro/recipes-core/packagegroups/ti-test.bb +0 -2
@@ -62,7 +62,6 @@ ARAGO_TI_TEST:append:ti33x = " \ ARAGO_TI_TEST:append:ti43x = " \ omapconf \ - ${@oe.utils.conditional('ARAGO_BRAND', 'mainline', '', 'cmem-test', d)} \ " NOT_MAINLINE_MMIP_DEPS = "${@bb.utils.contains('MACHINE_FEATURES', 'mmip', 'omapdrmtest', '', d)}"
@@ -71,7 +70,6 @@ ARAGO_TI_TEST:append:omap-a15 = " \ omapconf \ ${@oe.utils.conditional('ARAGO_BRAND', 'mainline', '', " \ ti-ipc-test \ - cmem-test \ ${NOT_MAINLINE_MMIP_DEPS} \ ", d)} \ "
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_cmem-mod deleted +0 -33
@@ -1,33 +0,0 @@ -# CMEM module -cmem-mod: linux - @echo ================================ - @echo Building CMEM Module - @echo ================================ - @cd board-support/extra-drivers; \ - cd `find . -maxdepth 1 -type d -name "cmem-mod*"`; \ - . $(ENV_SETUP); \ - make -f lu.mak ARCH=__KERNEL_ARCH__ KERNEL_INSTALL_DIR=$(LINUXKERNEL_INSTALL_DIR) module - -cmem-mod_clean: - @echo ================================ - @echo Cleaning CMEM Module - @echo ================================ - @cd board-support/extra-drivers; \ - cd `find . -maxdepth 1 -type d -name "cmem-mod*"`; \ - . $(ENV_SETUP); \ - make -f lu.mak ARCH=__KERNEL_ARCH__ KERNEL_INSTALL_DIR=$(LINUXKERNEL_INSTALL_DIR) modules_clean - -cmem-mod_install: - @echo ================================ - @echo Installing CMEM Module - @echo ================================ - @if [ ! -d $(DESTDIR) ] ; then \ - echo "The extracted target filesystem directory doesn't exist."; \ - echo "Please run setup.sh in the SDK's root directory and then try again."; \ - exit 1; \ - fi - @cd board-support/extra-drivers; \ - cd `find . -maxdepth 1 -type d -name "cmem-mod*"`; \ - . $(ENV_SETUP); \ - make -C $(LINUXKERNEL_INSTALL_DIR) SUBDIRS=`pwd`/src/cmem/module INSTALL_MOD_PATH=$(DESTDIR) PREFIX=$(SDK_PATH_TARGET) INSTALL_MOD_STRIP=$(INSTALL_MOD_STRIP) modules_install -
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb +0 -3
@@ -31,7 +31,6 @@ SRC_URI = "\ file://Makefile_dual-camera-demo \ file://Makefile_image-gallery \ file://Makefile_cryptodev \ - file://Makefile_cmem-mod \ file://Makefile_debugss-module-drv \ file://Makefile_gdbserverproxy-module-drv \ file://Makefile_ti-sgx-ddk-km \
@@ -89,7 +88,6 @@ MAKEFILES:append:ti43x = " u-boot-spl \ dual-camera-demo \ image-gallery \ ti-sgx-ddk-km \ - cmem-mod \ pru-icss \ uio-module-drv \ mmwavegesture-hmi \
@@ -110,7 +108,6 @@ MAKEFILES:append:omap-a15 = " u-boot-spl \ omapconf \ linux-dtbs \ ti-sgx-ddk-km \ - cmem-mod \ pru-icss \ ti-gc320-driver \ barcode-roi \
Signature · 1 line
2.37.3
PATCH 4/7 meta-arago: Remove remaining bits of ti-ocf-crypto-module
In reply to Andrew DavisThis is not included in the SDK anymore, remove left over references.
--- .../conf/distro/include/arago-source-ipk.inc | 3 --- .../Makefile_ti-ocf-crypto-module | 18 ------------------ .../ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb | 1 - 3 files changed, 22 deletions(-) delete mode 100644 meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_ti-ocf-crypto-module
meta-arago-distro/conf/distro/include/arago-source-ipk.inc +0 -3
@@ -103,9 +103,6 @@ SRCIPK_INSTALL_DIR:pn-omapconf ?= "example-applications/${PN}-${PV}" CREATE_SRCIPK:pn-ti-pru-sw-examples ?= "1" SRCIPK_INSTALL_DIR:pn-ti-pru-sw-examples ?= "example-applications/pru-${PV}" -CREATE_SRCIPK:pn-ti-ocf-crypto-module ?= "1" -SRCIPK_INSTALL_DIR:pn-ti-ocf-crypto-module ?= "board-support/extra-drivers/${PN}-${PV}" - CREATE_SRCIPK:pn-ti-compat-wireless-wl18xx ?= "1" SRCIPK_INSTALL_DIR:pn-ti-compat-wireless-wl18xx ?= "board-support/extra-drivers/${PN}-${PV}"
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_ti-ocf-crypto-module deleted +0 -18
@@ -1,18 +0,0 @@ -# ti-ocf-crypto-module components -ti-ocf-crypto-module: linux - @echo =================================== - @echo Building TI OCF Crypto Module - @echo =================================== - @cd board-support/extra-drivers; cd `find . -maxdepth 1 -type d -name "*ti-ocf-crypto-module*"`; make - -ti-ocf-crypto-module_clean: - @echo =================================== - @echo Cleaning TI OCF Crypto Module - @echo =================================== - @cd board-support/extra-drivers; cd `find . -maxdepth 1 -type d -name "*ti-ocf-crypto-module*"`; make clean - -ti-ocf-crypto-module_install: - @echo ===================================== - @echo Installing TI OCF Crypto Module - @echo ===================================== - @cd board-support/extra-drivers; cd `find . -maxdepth 1 -type d -name "*ti-ocf-crypto-module*"`; make install
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb +0 -1
@@ -24,7 +24,6 @@ SRC_URI = "\ file://Makefile_matrix-gui-browser \ file://Makefile_refresh-screen \ file://Makefile_pru \ - file://Makefile_ti-ocf-crypto-module \ file://Makefile_qt-tstat \ file://Makefile_omapconf \ file://Makefile_oprofile-example \
Signature · 1 line
2.37.3
PATCH 5/7 ti-pru-sw: Remove old TI-PRU-SW examples and helpers
In reply to Andrew DavisThe source for these is long gone and they were not the correct way to use the PRUs these days anyway. Remove them.
--- .../conf/distro/include/arago-source-ipk.inc | 3 -- ...ackagegroup-arago-tisdk-addons-sdk-host.bb | 6 ---- .../ti-pru-sw-app-loader_1.00.00.bb | 26 ---------------- .../ti-pru-sw-edma-library_1.00.00.bb | 30 ------------------ .../ti-pru-sw-examples_1.00.00.bb | 31 ------------------- 5 files changed, 96 deletions(-) delete mode 100644 meta-arago-extras/recipes-core/ti-pru-sw-app-loader/ti-pru-sw-app-loader_1.00.00.bb delete mode 100644 meta-arago-extras/recipes-core/ti-pru-sw-edma-library/ti-pru-sw-edma-library_1.00.00.bb delete mode 100644 meta-arago-extras/recipes-core/ti-pru-sw-examples/ti-pru-sw-examples_1.00.00.bb
meta-arago-distro/conf/distro/include/arago-source-ipk.inc +0 -3
@@ -100,9 +100,6 @@ SRCIPK_INSTALL_DIR:pn-arm-benchmarks ?= "example-applications/${PN}-${PV}" CREATE_SRCIPK:pn-omapconf ?= "1" SRCIPK_INSTALL_DIR:pn-omapconf ?= "example-applications/${PN}-${PV}" -CREATE_SRCIPK:pn-ti-pru-sw-examples ?= "1" -SRCIPK_INSTALL_DIR:pn-ti-pru-sw-examples ?= "example-applications/pru-${PV}" - CREATE_SRCIPK:pn-ti-compat-wireless-wl18xx ?= "1" SRCIPK_INSTALL_DIR:pn-ti-compat-wireless-wl18xx ?= "board-support/extra-drivers/${PN}-${PV}"
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-host.bb +0 -6
@@ -12,12 +12,6 @@ UTILS = " \ oprofile-example-source \ " -# ti-pru-sw-edma-driver is currently broken -# Add pru and profibus sources for omapl138 devices -#UTILS:append:omapl138 = " \ -# ti-pru-sw-examples-source \ -#" - UTILS:append:omap-a15 = " \ omapconf-source \ pru-icss-source \
meta-arago-extras/recipes-core/ti-pru-sw-app-loader/ti-pru-sw-app-loader_1.00.00.bb deleted +0 -26
@@ -1,26 +0,0 @@ -DESCRIPTION = "PRU sw application loader" -HOMEPAGE = "https://gforge.ti.com/gf/project/pru_sw/" -LICENSE = "BSD-3-Clause" -LIC_FILES_CHKSUM = "file://interface/prussdrv.c;beginline=1;endline=47;md5=6012fea45c1fbced663277bc90d2163a" - -RRECOMMENDS:${PN} = "kernel-module-uio-pru" -PR = "r0" -PV:append = "+svn${SRCPV}" - -COMPATIBLE_MACHINE = "omapl138" - -SRC_URI = "svn://gforge.ti.com/svn/pru_sw/;module=trunk;protocol=https;user=anonymous;pswd=''" - -SRCREV = "33" -S = "${WORKDIR}/trunk/app_loader" - -do_compile () { - make -C ${S}/interface CCTOOL_PREFIX=${TOOLCHAIN_PATH}/bin/${TARGET_PREFIX} -} - -do_install () { - install -d ${D}${libdir} - install -d ${D}${includedir} - install -m 0644 ${S}/include/* ${D}${includedir} - install -m 0644 ${S}/lib/* ${D}${libdir} -}
meta-arago-extras/recipes-core/ti-pru-sw-edma-library/ti-pru-sw-edma-library_1.00.00.bb deleted +0 -30
@@ -1,30 +0,0 @@ -DESCRIPTION = "eDMA library for use by PRU sw example applications" -HOMEPAGE = "https://gforge.ti.com/gf/project/pru_sw/" -LICENSE = "BSD-3-Clause" -LIC_FILES_CHKSUM = "file://edma.c;beginline=1;endline=46;md5=f6bde95a8e2277050e36b257ca9214a6" - -DEPENDS += "virtual/kernel" - -RDEPENDS:${PN} += "ti-pru-sw-edma-driver" - -PACKAGE_ARCH = "${MACHINE_ARCH}" - -COMPATIBLE_MACHINE = "omapl138" - -MACHINE_KERNEL_PR:append = "a" -PR = "${MACHINE_KERNEL_PR}" -PV:append = "+svn${SRCPV}" - -SRC_URI = "svn://gforge.ti.com/svn/pru_sw/;module=trunk;protocol=https;user=anonymous;pswd=''" - -SRCREV = "33" -S = "${WORKDIR}/trunk/peripheral_lib/edma_driver/interface" - -do_compile () { - oe_runmake KERNEL_DIR="${STAGING_KERNEL_DIR}" CCTOOL_PREFIX=${TOOLCHAIN_PATH}/bin/${TARGET_PREFIX} -} - -do_install () { - install -d ${D}/${libdir} - install -m 0755 ${S}/../lib/libedmautils.a ${D}/${libdir}/ -}
meta-arago-extras/recipes-core/ti-pru-sw-examples/ti-pru-sw-examples_1.00.00.bb deleted +0 -31
@@ -1,31 +0,0 @@ -DESCRIPTION = "PRU sw example applications" -HOMEPAGE = "https://gforge.ti.com/gf/project/pru_sw/" -LICENSE = "BSD-3-Clause" -LIC_FILES_CHKSUM = "file://LICENCE.txt;md5=c4fd8ee7443c1b2b6238b4b5df796481" -DEPENDS = "ti-pru-sw-app-loader ti-pru-sw-edma-library" -RDEPENDS:${PN} = "ti-pru-sw-edma-driver" -PR = "r0" -PV:append = "+svn${SRCPV}" - -COMPATIBLE_MACHINE = "omapl138" - -SRC_URI = "svn://gforge.ti.com/svn/pru_sw/;module=trunk;protocol=https;user=anonymous;pswd=''" - -SRCREV = "33" -S = "${WORKDIR}/trunk" - -do_compile () { - make -C ${S}/example_apps \ - CCTOOLS="${TOOLCHAIN_PATH}/bin/${TARGET_PREFIX}gcc ${TOOLCHAIN_OPTIONS}"\ - BINDIR_APPLICATIONS="${S}/example_apps/bin" \ - BINDIR_FW="${S}/example_apps/bin" \ - UTILS_DIR="${S}/utils" -} - -do_install () { - install -d ${D}/usr/share/ti/ti-pru-eg/ - install -m 0755 ${S}/example_apps/bin/* ${D}/usr/share/ti/ti-pru-eg/ -} - -FILES:${PN} += "${datadir}/ti/ti-pru-eg/*" -FILES:${PN}-dbg += "${datadir}/ti/ti-pru-eg/.debug/*"
Signature · 1 line
2.37.3
PATCH 6/7 ti-tisdk: Remove uio-module-drv kernel module
In reply to Andrew DavisUIO drivers are generally frowned upon and were only used here for some K2 devices and PRUs before RPMSG. With these uses finally gone, lets remove this out-of-tree module.
--- .../conf/distro/include/arago-source-ipk.inc | 3 -- ...ackagegroup-arago-tisdk-addons-sdk-host.bb | 9 ------ .../packagegroup-arago-tisdk-addons.bb | 20 ------------- .../ti-tisdk-makefile/Makefile_uio-module-drv | 28 ------------------- .../ti-tisdk-makefile_1.0.bb | 4 --- 5 files changed, 64 deletions(-) delete mode 100644 meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_uio-module-drv
meta-arago-distro/conf/distro/include/arago-source-ipk.inc +0 -3
@@ -334,9 +334,6 @@ SRCIPK_INSTALL_DIR:pn-boot-monitor ?= "board-support/${PN}-${PV}" CREATE_SRCIPK:pn-hplib-mod ?= "1" SRCIPK_INSTALL_DIR:pn-hplib-mod ?= "board-support/extra-drivers/${PN}-${PV}" -CREATE_SRCIPK:pn-uio-module-drv ?= "1" -SRCIPK_INSTALL_DIR:pn-uio-module-drv ?= "board-support/extra-drivers/${PN}-${PV}" - CREATE_SRCIPK:pn-pru-icss ?= "1" SRCIPK_INSTALL_DIR:pn-pru-icss ?= "example-applications/${PN}-${PV}"
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-host.bb +0 -9
@@ -50,7 +50,6 @@ UTILS:append:am64xx = " \ EXTRA_LIBS = "" EXTRA_LIBS:append:omap-a15 = " \ - uio-module-drv-source \ big-data-ipc-demo-source \ "
@@ -59,14 +58,6 @@ EXTRA_LIBS:append:omap-a15 = " \ # gdbserverproxy-module-drv-source \ #" -EXTRA_LIBS:append:ti33x = " \ - uio-module-drv-source \ -" - -EXTRA_LIBS:append:ti43x = " \ - uio-module-drv-source \ -" - PDM_ANOMALY_PKG_SRC = "\ ${@bb.utils.contains('MACHINE_FEATURES', 'gpu', 'pdm-anomaly-detection-source', '', d)} \ "
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +0 -20
@@ -34,16 +34,12 @@ UTILS_DSP = " \ UTILS:append:ti33x = " mmc-utils \ switch-config \ pru-icss \ - uio-module-drv-test \ - uio-test-pruss \ " UTILS:append:ti43x = " mmc-utils \ switch-config \ libdrm-omap \ pru-icss \ - uio-module-drv-test \ - uio-test-pruss \ " UTILS:append:omap-a15 = " mmc-utils \
@@ -51,8 +47,6 @@ UTILS:append:omap-a15 = " mmc-utils \ libdrm-omap \ pru-icss \ ti-ipc-rtos-fw \ - uio-test-pruss \ - uio-module-drv-test \ " UTILS:append:k3 = " mmc-utils \
@@ -78,19 +72,6 @@ UTILS:append:dra7xx = " \ ${@bb.utils.contains('MACHINE_FEATURES','gpu','glsdk-example-apps','',d)} \ " -EXTRA_LIBS = "" -EXTRA_LIBS:append:omap-a15 = " \ - uio-module-drv \ -" - -EXTRA_LIBS:append:ti43x = " \ - uio-module-drv \ -" - -EXTRA_LIBS:append:ti33x = " \ - uio-module-drv \ -" - EXTRA_PACKAGES = " \ nodejs \ nodejs-npm \
@@ -118,7 +99,6 @@ EXTRA_PACKAGES:append:omap-a15 = " \ RDEPENDS:${PN} = "\ ${UTILS} \ ${UTILS_UBOOT_FW} \ - ${EXTRA_LIBS} \ " RDEPENDS:${PN}-extra = "\
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_uio-module-drv deleted +0 -28
@@ -1,28 +0,0 @@ -uio-module-drv: linux - @echo ================================ - @echo Building uio-module-drv - @echo ================================ - @cd board-support/extra-drivers; \ - cd `find . -maxdepth 1 -type d -name "uio-module-drv*"`; \ - make ARCH=__KERNEL_ARCH__ KERNEL_SRC=$(LINUXKERNEL_INSTALL_DIR) - -uio-module-drv_clean: - @echo ================================ - @echo Cleaning uio-module-drv - @echo ================================ - @cd board-support/extra-drivers; \ - cd `find . -maxdepth 1 -type d -name "uio-module-drv*"`; \ - make ARCH=__KERNEL_ARCH__ KERNEL_SRC=$(LINUXKERNEL_INSTALL_DIR) clean - -uio-module-drv_install: - @echo ================================ - @echo Installing uio-module-drv - @echo ================================ - @if [ ! -d $(DESTDIR) ] ; then \ - echo "The extracted target filesystem directory doesn't exist."; \ - echo "Please run setup.sh in the SDK's root directory and then try again."; \ - exit 1; \ - fi - @cd board-support/extra-drivers; \ - cd `find . -maxdepth 1 -type d -name "uio-module-drv*"`; \ - make ARCH=__KERNEL_ARCH__ KERNEL_SRC=$(LINUXKERNEL_INSTALL_DIR) INSTALL_MOD_PATH=$(DESTDIR) PREFIX=$(SDK_PATH_TARGET) INSTALL_MOD_STRIP=$(INSTALL_MOD_STRIP) modules_install
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb +0 -4
@@ -36,7 +36,6 @@ SRC_URI = "\ file://Makefile_opencl-examples \ file://Makefile_boot-monitor \ file://Makefile_hplib-mod \ - file://Makefile_uio-module-drv \ file://Makefile_pru-icss \ file://Makefile_qt-opencv-opencl-opengl-multithreaded \ file://Makefile_openmpacc-examples \
@@ -77,7 +76,6 @@ MAKEFILES:append:ti33x = " u-boot-spl \ cryptodev \ ti-sgx-ddk-km \ pru-icss \ - uio-module-drv \ mmwavegesture-hmi \ pdm-anomaly-detection \ "
@@ -88,7 +86,6 @@ MAKEFILES:append:ti43x = " u-boot-spl \ image-gallery \ ti-sgx-ddk-km \ pru-icss \ - uio-module-drv \ mmwavegesture-hmi \ pdm-anomaly-detection \ "
@@ -110,7 +107,6 @@ MAKEFILES:append:omap-a15 = " u-boot-spl \ pru-icss \ ti-gc320-driver \ barcode-roi \ - uio-module-drv \ mmwavegesture-hmi \ pdm-anomaly-detection \ ti-ipc \
Signature · 1 line
2.37.3
PATCH 7/7 meta-arago: Use new J7 SoC names over specific board names
In reply to Andrew DavisNow that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board.
One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added.
--- .../recipes-core/images/tisdk-core-bundle.bb | 3 +-- .../recipes-core/images/tisdk-core-bundle.inc | 4 +++- .../packagegroup-arago-tisdk-addons-sdk-host.bb | 6 +----- .../packagegroups/packagegroup-arago-tisdk-addons.bb | 6 +++--- .../recipes-core/packagegroups/ti-analytics.bb | 4 +++- .../recipes-core/packagegroups/ti-test.bb | 10 +++++++++- .../ti-tisdk-makefile/Makefile_sysfw-image | 6 ++---- .../gstreamer/gstreamer1.0-plugins-bad_1.16.%.bbappend | 6 +----- 8 files changed, 23 insertions(+), 22 deletions(-)
meta-arago-distro/recipes-core/images/tisdk-core-bundle.bb +1 -2
@@ -12,8 +12,7 @@ DEPLOY_SPL_NAME:k3 = "tispl.bin tiboot3.bin" DEPLOY_IMAGES_NAME:k3 = "bl31.bin bl32.bin" DEPLOY_IMAGES_NAME:append:am65xx = " sysfw.itb" -DEPLOY_IMAGES_NAME:append:j721e-evm = " sysfw.itb" -DEPLOY_IMAGES_NAME:append:j721e-hs-evm = " sysfw.itb" +DEPLOY_IMAGES_NAME:append:j721e = " sysfw.itb" DEPLOY_IMAGES_NAME:append:am65xx-evm = " sysfw-am65x-evm.itb sysfw-am65x_sr2-evm.itb" ARAGO_TISDK_IMAGE ?= "tisdk-core-bundle"
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc +3 -1
@@ -24,7 +24,9 @@ DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" DTB_FILTER:ti43x = "am43" DTB_FILTER:omapl138 = "da850" DTB_FILTER:am65xx = "am65" -DTB_FILTER:j7 = "j721e" +DTB_FILTER:j721e = "j721e" +DTB_FILTER:j7200 = "j7200" +DTB_FILTER:j721s2 = "j721s2" # List of target side images to build for the SDK TARGET_IMAGES = "tisdk-base-image tisdk-default-image tisdk-thinlinux-image tisdk-bootstrap-image"
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-host.bb +1 -5
@@ -31,11 +31,7 @@ UTILS:append:k3 = " \ trusted-firmware-a-source \ " -UTILS:append:j721e-evm = " \ - pru-icss-source \ -" - -UTILS:append:j721e-hs-evm = " \ +UTILS:append:j721e = " \ pru-icss-source \ "
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +3 -3
@@ -61,9 +61,9 @@ UTILS:append:am64xx = " ti-rtos-firmware pru-icss" UTILS:append:am62xx = " ti-rtos-firmware" #UTILS:append:am65xx = " ti-rtos-firmware pru-icss pru-pwm-fw" UTILS:append:am65xx = " ti-rtos-firmware pru-icss" -UTILS:append:j7 = " ti-rtos-firmware" -UTILS:append:j721e-evm = " pru-icss" -UTILS:append:j721e-hs-evm = " pru-icss" +UTILS:append:j721e = " ti-rtos-firmware pru-icss" +UTILS:append:j7200 = " ti-rtos-firmware" +UTILS:append:j721s2 = " ti-rtos-firmware" UTILS:append:omapl138 = " ti-ipc-rtos-fw"
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +3 -1
@@ -19,7 +19,9 @@ ANALYTICS = "" # ${@['','qt-opencv-opencl-opengl-multithreaded'][oe.utils.all_distro_features(d, 'opencv opencl opengl', True, False) and bb.utils.contains('MACHINE_FEATURES', 'gpu dsp', True, False, d)]} \ # ${@['','barcode-roi'][oe.utils.all_distro_features(d, 'opencv', True, False) and bb.utils.contains('MACHINE_FEATURES', 'dsp', True, False, d)]} \ #" -ANALYTICS:j7 = "" +ANALYTICS:j721e = "" +ANALYTICS:j7200 = "" +ANALYTICS:j721s2 = "" ANALYTICS:omapl138 = "" RDEPENDS:${PN} = "\
meta-arago-distro/recipes-core/packagegroups/ti-test.bb +9 -1
@@ -78,7 +78,15 @@ ARAGO_TI_TEST:append:k3 = " \ k3conf \ " -ARAGO_TI_TEST:append:j7 = " \ +ARAGO_TI_TEST:append:j721e = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j7200 = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j721s2 = " \ ufs-utils \ "
meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile/Makefile_sysfw-image +2 -4
@@ -7,10 +7,8 @@ PLATFORM_TYPE = $(PLATFORM_TYPE_$(PLATFORM)) SYSFW_CONFIG = evm SYSFW_SOC_$(PLATFORM) = NULL -SYSFW_SOC_am65xx-evm = am65x -SYSFW_SOC_am65xx-hs-evm = am65x -SYSFW_SOC_j721e-evm = j721e -SYSFW_SOC_j721e-hs-evm = j721e +SYSFW_SOC_am65xx = am65x +SYSFW_SOC_j721e = j721e SYSFW_SOC = $(SYSFW_SOC_$(PLATFORM)) SYSFW_PREFIX = ti-sci-firmware
meta-arago-extras/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad_1.16.%.bbappend +1 -5
@@ -28,11 +28,7 @@ SRC_URI:append:am65xx = " \ ${GSTDRM_WAYLANDSINK_PATCHES} \ " -SRC_URI:append:j721e-evm = " \ - ${GSTDRM_WAYLANDSINK_PATCHES} \ -" - -SRC_URI:append:j721e-hs-evm = " \ +SRC_URI:append:j721e = " \ ${GSTDRM_WAYLANDSINK_PATCHES} \ "
Signature · 1 line
2.37.3
Re: [meta-arago][master/kirkstone][PATCH 7/7] meta-arago: Use new J7 SoC names over specific board names
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
Now that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board.
One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added.
Hmm, this second part is rather backwards (IMO) in some places, see below.
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" · line 29
Quoted 12 lines
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc +3
-1@@ -24,7 +24,9 @@ DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" DTB_FILTER:ti43x = "am43" DTB_FILTER:omapl138 = "da850" DTB_FILTER:am65xx = "am65" -DTB_FILTER:j7 = "j721e" +DTB_FILTER:j721e = "j721e" +DTB_FILTER:j7200 = "j7200" +DTB_FILTER:j721s2 = "j721s2"
Yes, here it does make perfect sense.
Quoted 5 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +0
-0
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb UTILS:append:am64xx = " ti-rtos-firmware pru-icss" · line 66
Quoted 9 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +3
-3@@ -61,9 +61,9 @@ UTILS:append:am64xx = " ti-rtos-firmware pru-icss" UTILS:append:am62xx = " ti-rtos-firmware" #UTILS:append:am65xx = " ti-rtos-firmware pru-icss pru-pwm-fw" UTILS:append:am65xx = " ti-rtos-firmware pru-icss" -UTILS:append:j7 = " ti-rtos-firmware" -UTILS:append:j721e-evm = " pru-icss" -UTILS:append:j721e-hs-evm = " pru-icss" +UTILS:append:j721e = " ti-rtos-firmware pru-icss" +UTILS:append:j7200 = " ti-rtos-firmware" +UTILS:append:j721s2 = " ti-rtos-firmware"
Here - not so much. ti-rtos-firmware is applicable to all j7. So, I'd leave that line alone and only replace adding pru-icss to specific EVMs to adding it to j721e SoC family.
Or go even further - ti-rtos-firmware is common to all k3 platforms, so all the individual am65xx, am64xx and am62xx, along with j7, could be replaced with one line:
UTILS:append:k3 = " ti-rtos-firmware"
And then add pri-icss or other extra FW to specific SoC families only.
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb ANALYTICS = "" · line 24
Quoted 12 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +3
-1@@ -19,7 +19,9 @@ ANALYTICS = "" # ${@['','qt-opencv-opencl-opengl-multithreaded'][oe.utils.all_distro_features(d, 'opencv opencl opengl', True, False) and bb.utils.contains('MACHINE_FEATURES', 'gpu dsp', True, False, d)]} \ # ${@['','barcode-roi'][oe.utils.all_distro_features(d, 'opencv', True, False) and bb.utils.contains('MACHINE_FEATURES', 'dsp', True, False, d)]} \ #" -ANALYTICS:j7 = "" +ANALYTICS:j721e = "" +ANALYTICS:j7200 = "" +ANALYTICS:j721s2 = ""
Well, this is probably completely wrong by now, anyway.
Quoted 13 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +0
-0ANALYTICS:omapl138 = "" RDEPENDS:${PN} = "\meta-arago-distro/recipes-core/packagegroups/ti-test.bb +1
-1@@ -78,7 +78,15 @@ ARAGO_TI_TEST:append:k3 = " \ k3conf \ " -ARAGO_TI_TEST:append:j7 = " \ +ARAGO_TI_TEST:append:j721e = " \
meta-arago-distro/recipes-core/packagegroups/ti-test.bb ARAGO_TI_TEST:append:k3 = " \ · line 91
Quoted 10 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb +8
-0+ ufs-utils \ +" + +ARAGO_TI_TEST:append:j7200 = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j721s2 = " \ ufs-utils \ "
ufs-utils is quite generic and should probably be added to k3 or maybe even all platforms...
Signature · 1 line
Denys
Re: [meta-arago][master/kirkstone][PATCH 7/7] meta-arago: Use new J7 SoC names over specific board names
Quoted 50 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
Now that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board.
One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added.
Hmm, this second part is rather backwards (IMO) in some places, see below.
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" · line 29
Quoted 12 lines
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc +3
-1@@ -24,7 +24,9 @@ DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" DTB_FILTER:ti43x = "am43" DTB_FILTER:omapl138 = "da850" DTB_FILTER:am65xx = "am65" -DTB_FILTER:j7 = "j721e" +DTB_FILTER:j721e = "j721e" +DTB_FILTER:j7200 = "j7200" +DTB_FILTER:j721s2 = "j721s2"Yes, here it does make perfect sense.
Quoted 5 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +0
-0meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb UTILS:append:am64xx = " ti-rtos-firmware pru-icss" · line 66
Quoted 9 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +3
-3@@ -61,9 +61,9 @@ UTILS:append:am64xx = " ti-rtos-firmware pru-icss" UTILS:append:am62xx = " ti-rtos-firmware" #UTILS:append:am65xx = " ti-rtos-firmware pru-icss pru-pwm-fw" UTILS:append:am65xx = " ti-rtos-firmware pru-icss" -UTILS:append:j7 = " ti-rtos-firmware" -UTILS:append:j721e-evm = " pru-icss" -UTILS:append:j721e-hs-evm = " pru-icss" +UTILS:append:j721e = " ti-rtos-firmware pru-icss" +UTILS:append:j7200 = " ti-rtos-firmware" +UTILS:append:j721s2 = " ti-rtos-firmware"Here - not so much. ti-rtos-firmware is applicable to all j7. So, I'd leave that line alone and only replace adding pru-icss to specific EVMs to adding it to j721e SoC family.
Quoted 8 lines
Or go even further - ti-rtos-firmware is common to all k3 platforms, so all the individual am65xx, am64xx and am62xx, along with j7, could be replaced with one line:
UTILS:append:k3 = " ti-rtos-firmware"
And then add pri-icss or other extra FW to specific SoC families only.
If you want I can make this re-arrangement in a follow up patch.
Quoted 16 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb ANALYTICS = "" · line 24
Quoted 13 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +3
-1@@ -19,7 +19,9 @@ ANALYTICS = "" # ${@['','qt-opencv-opencl-opengl-multithreaded'][oe.utils.all_distro_features(d, 'opencv opencl opengl', True, False) and bb.utils.contains('MACHINE_FEATURES', 'gpu dsp', True, False, d)]} \ # ${@['','barcode-roi'][oe.utils.all_distro_features(d, 'opencv', True, False) and bb.utils.contains('MACHINE_FEATURES', 'dsp', True, False, d)]} \ #" -ANALYTICS:j7 = "" +ANALYTICS:j721e = "" +ANALYTICS:j7200 = "" +ANALYTICS:j721s2 = ""Well, this is probably completely wrong by now, anyway.
Yes it probably is, but then my point in this patch was to not make any changes to functionality (or as few as possible). So if it is broken now, it was broken just the same before.
Quoted 12 lines
Quoted 12 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +0
-0ANALYTICS:omapl138 = "" RDEPENDS:${PN} = "\meta-arago-distro/recipes-core/packagegroups/ti-test.bb +0
-0@@ -78,7 +78,15 @@ ARAGO_TI_TEST:append:k3 = " \ k3conf \ "
Quoted 16 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb ARAGO_TI_TEST:append:k3 = " \ · line 91
Quoted 12 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb +9
-1-ARAGO_TI_TEST:append:j7 = " \ +ARAGO_TI_TEST:append:j721e = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j7200 = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j721s2 = " \ ufs-utils \ "ufs-utils is quite generic and should probably be added to k3 or maybe even all platforms...
Same as above, would you like this done in a follow up patch? This patch only fans out the name keeping the same functionality as before. If that exposes existing issues or opportunities for cleanup, then I can make those next.
Andrew
Re: [meta-arago][master/kirkstone][PATCH 7/7] meta-arago: Use new J7 SoC names over specific board names
Quoted 110 lines · Andrew Davis
Quoted 50 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
Now that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board.
One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added.
Hmm, this second part is rather backwards (IMO) in some places, see below.
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" · line 29
Quoted 12 lines
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc +3
-1@@ -24,7 +24,9 @@ DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" DTB_FILTER:ti43x = "am43" DTB_FILTER:omapl138 = "da850" DTB_FILTER:am65xx = "am65" -DTB_FILTER:j7 = "j721e" +DTB_FILTER:j721e = "j721e" +DTB_FILTER:j7200 = "j7200" +DTB_FILTER:j721s2 = "j721s2"Yes, here it does make perfect sense.
Quoted 5 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +0
-0meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb UTILS:append:am64xx = " ti-rtos-firmware pru-icss" · line 66
Quoted 9 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +3
-3@@ -61,9 +61,9 @@ UTILS:append:am64xx = " ti-rtos-firmware pru-icss" UTILS:append:am62xx = " ti-rtos-firmware" #UTILS:append:am65xx = " ti-rtos-firmware pru-icss pru-pwm-fw" UTILS:append:am65xx = " ti-rtos-firmware pru-icss" -UTILS:append:j7 = " ti-rtos-firmware" -UTILS:append:j721e-evm = " pru-icss" -UTILS:append:j721e-hs-evm = " pru-icss" +UTILS:append:j721e = " ti-rtos-firmware pru-icss" +UTILS:append:j7200 = " ti-rtos-firmware" +UTILS:append:j721s2 = " ti-rtos-firmware"Here - not so much. ti-rtos-firmware is applicable to all j7. So, I'd leave that line alone and only replace adding pru-icss to specific EVMs to adding it to j721e SoC family.
Quoted 8 lines
Or go even further - ti-rtos-firmware is common to all k3 platforms, so all the individual am65xx, am64xx and am62xx, along with j7, could be replaced with one line:
UTILS:append:k3 = " ti-rtos-firmware"
And then add pri-icss or other extra FW to specific SoC families only.
If you want I can make this re-arrangement in a follow up patch.
Quoted 16 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb ANALYTICS = "" · line 24
Quoted 13 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +3
-1@@ -19,7 +19,9 @@ ANALYTICS = "" # ${@['','qt-opencv-opencl-opengl-multithreaded'][oe.utils.all_distro_features(d, 'opencv opencl opengl', True, False) and bb.utils.contains('MACHINE_FEATURES', 'gpu dsp', True, False, d)]} \ # ${@['','barcode-roi'][oe.utils.all_distro_features(d, 'opencv', True, False) and bb.utils.contains('MACHINE_FEATURES', 'dsp', True, False, d)]} \ #" -ANALYTICS:j7 = "" +ANALYTICS:j721e = "" +ANALYTICS:j7200 = "" +ANALYTICS:j721s2 = ""Well, this is probably completely wrong by now, anyway.
Yes it probably is, but then my point in this patch was to not make any changes to functionality (or as few as possible). So if it is broken now, it was broken just the same before.
Quoted 17 lines
Quoted 17 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +0
-0ANALYTICS:omapl138 = "" RDEPENDS:${PN} = "\meta-arago-distro/recipes-core/packagegroups/ti-test.bb +6
-1@@ -78,7 +78,15 @@ ARAGO_TI_TEST:append:k3 = " \ k3conf \ " -ARAGO_TI_TEST:append:j7 = " \ +ARAGO_TI_TEST:append:j721e = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j7200 = " \ + ufs-utils \Quoted 9 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb ARAGO_TI_TEST:append:k3 = " \ · line 91
Quoted 5 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb +3
-0+" + +ARAGO_TI_TEST:append:j721s2 = " \ ufs-utils \ "ufs-utils is quite generic and should probably be added to k3 or maybe even all platforms...
Quoted 3 lines
Same as above, would you like this done in a follow up patch? This patch only fans out the name keeping the same functionality as before. If that exposes existing issues or opportunities for cleanup, then I can make those next.
It would have been fine to do further cleanup/optimization/collapsing of the code in a followup patch, if you weren't first expanding it here...
In other words, it seems replacing "j7" override with more specific "j721e/j7200/j721s2" overrides only makes sense for DTB_FILTER case and should be left alone in other 3 places.
Signature · 1 line
Denys
Re: [meta-arago][master/kirkstone][PATCH 7/7] meta-arago: Use new J7 SoC names over specific board names
Quoted 102 lines · Denys Dmytriyenko
Quoted 101 lines · Andrew Davis
Quoted 50 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
Now that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board.
One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added.
Hmm, this second part is rather backwards (IMO) in some places, see below.
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" · line 29
Quoted 12 lines
meta-arago-distro/recipes-core/images/tisdk-core-bundle.inc +3
-1@@ -24,7 +24,9 @@ DTB_FILTER:am57xx-hs-evm = "${DTB_FILTER:am57xx-evm}" DTB_FILTER:ti43x = "am43" DTB_FILTER:omapl138 = "da850" DTB_FILTER:am65xx = "am65" -DTB_FILTER:j7 = "j721e" +DTB_FILTER:j721e = "j721e" +DTB_FILTER:j7200 = "j7200" +DTB_FILTER:j721s2 = "j721s2"Yes, here it does make perfect sense.
Quoted 5 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +0
-0meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb UTILS:append:am64xx = " ti-rtos-firmware pru-icss" · line 66
Quoted 9 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb +3
-3@@ -61,9 +61,9 @@ UTILS:append:am64xx = " ti-rtos-firmware pru-icss" UTILS:append:am62xx = " ti-rtos-firmware" #UTILS:append:am65xx = " ti-rtos-firmware pru-icss pru-pwm-fw" UTILS:append:am65xx = " ti-rtos-firmware pru-icss" -UTILS:append:j7 = " ti-rtos-firmware" -UTILS:append:j721e-evm = " pru-icss" -UTILS:append:j721e-hs-evm = " pru-icss" +UTILS:append:j721e = " ti-rtos-firmware pru-icss" +UTILS:append:j7200 = " ti-rtos-firmware" +UTILS:append:j721s2 = " ti-rtos-firmware"Here - not so much. ti-rtos-firmware is applicable to all j7. So, I'd leave that line alone and only replace adding pru-icss to specific EVMs to adding it to j721e SoC family.
Quoted 8 lines
Or go even further - ti-rtos-firmware is common to all k3 platforms, so all the individual am65xx, am64xx and am62xx, along with j7, could be replaced with one line:
UTILS:append:k3 = " ti-rtos-firmware"
And then add pri-icss or other extra FW to specific SoC families only.
If you want I can make this re-arrangement in a follow up patch.
Quoted 16 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb ANALYTICS = "" · line 24
Quoted 13 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +3
-1@@ -19,7 +19,9 @@ ANALYTICS = "" # ${@['','qt-opencv-opencl-opengl-multithreaded'][oe.utils.all_distro_features(d, 'opencv opencl opengl', True, False) and bb.utils.contains('MACHINE_FEATURES', 'gpu dsp', True, False, d)]} \ # ${@['','barcode-roi'][oe.utils.all_distro_features(d, 'opencv', True, False) and bb.utils.contains('MACHINE_FEATURES', 'dsp', True, False, d)]} \ #" -ANALYTICS:j7 = "" +ANALYTICS:j721e = "" +ANALYTICS:j7200 = "" +ANALYTICS:j721s2 = ""Well, this is probably completely wrong by now, anyway.
Yes it probably is, but then my point in this patch was to not make any changes to functionality (or as few as possible). So if it is broken now, it was broken just the same before.
Quoted 18 lines
Quoted 18 lines
meta-arago-distro/recipes-core/packagegroups/ti-analytics.bb +0
-0ANALYTICS:omapl138 = "" RDEPENDS:${PN} = "\meta-arago-distro/recipes-core/packagegroups/ti-test.bb +7
-1@@ -78,7 +78,15 @@ ARAGO_TI_TEST:append:k3 = " \ k3conf \ " -ARAGO_TI_TEST:append:j7 = " \ +ARAGO_TI_TEST:append:j721e = " \ + ufs-utils \ +" + +ARAGO_TI_TEST:append:j7200 = " \ + ufs-utils \ +"
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb ARAGO_TI_TEST:append:k3 = " \ · line 91
Quoted 4 lines
meta-arago-distro/recipes-core/packagegroups/ti-test.bb +2
-0+ +ARAGO_TI_TEST:append:j721s2 = " \ ufs-utils \ "ufs-utils is quite generic and should probably be added to k3 or maybe even all platforms...
Looks like UFS is only supported on J721e today, so when "j7" was used above, they only meant "j721e". Will fix.
Quoted 5 lines
Quoted 4 lines
Same as above, would you like this done in a follow up patch? This patch only fans out the name keeping the same functionality as before. If that exposes existing issues or opportunities for cleanup, then I can make those next.
Quoted 7 lines
It would have been fine to do further cleanup/optimization/collapsing of the code in a followup patch, if you weren't first expanding it here...
In other words, it seems replacing "j7" override with more specific "j721e/j7200/j721s2" overrides only makes sense for
DTB_FILTERcase and should be left alone in other 3 places.
I'll break the other ones out into patches fixing as suggested.
The goal is to remove the name "j7" everywhere, grouping for the "J7" family is not useful, there is nothing common today to all J7 devices that is not also common to all K3. It is an unneeded level of grouping that is now causing issues and mistakes when adding new platforms.
Andrew
Re: [meta-arago][master/kirkstone][PATCH 1/7] ti-crypto-examples: Remove
In reply to Andrew Davismeta-arago / na / 20221006150628.17044-1-afd
PRC Results: FAIL
=========================================================
check-yocto-patches: FAIL
=========================================================
Patches
----------------------------------------
FAIL - [meta-arago][master/kirkstone][PATCH 2/7] big-data-ipc-demo: Merge include file and rename
ERROR: Missing License-Update for change in LIC_FILES_CHKSUM. (LICENSE-UPDATE-1)
patch