[meta-ti] [thud/master][PATCH] am335x-evm: bump max_leb_cnt again

2019-11-20 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am335x-evm.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/am335x-evm.conf b/conf/machine/am335x-evm.conf
index ad245dd..92e6cf0 100644
--- a/conf/machine/am335x-evm.conf
+++ b/conf/machine/am335x-evm.conf
@@ -24,7 +24,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 # UBI: logical eraseblock size:126976 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 1988 LEBs
-MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 9800"
+MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 9900"
 
 # do ubiattach /dev/ubi_ctrl -m 7 -O 2048
 # from dmesg:
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] Equivalence to shipped BBB

2019-11-19 Thread Denys Dmytriyenko
On Sun, Nov 17, 2019 at 08:56:00AM -0600, Colin Bester wrote:
> Can one create BBB image as is currently shipped today using yocto and 
> meta-ti or is additional building/installation required after creation of 
> image via yocto?

And by "shipped BBB" do you mean Debian images? If so, it should be possible 
to reproduce them in Yocto, but currently there are no ready-made recipes 
available for those images.

-- 
Denys
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] Backport request for thud

2019-11-19 Thread Denys Dmytriyenko
On Sat, Nov 16, 2019 at 11:43:19AM +, Paul Barker wrote:
> I'm currently seeing build failures on the thud branch with meta-ti under 
> Centos 7 and Centos 8. As /lib and /lib64 are links to /usr/lib and 
> /usr/lib64 respectively, the logic in ti-unpack.inc is looking for the 
> 32-bit C library under /lib32 which doesn't exist.
> 
> Could you backport 6f80b1e5595a13eec465581cfb352efcb0286bc8 from master to 
> thud to fix this?

Paul,

I will backport this fix to thud, but currently it's frozen due to a pending 
release. Please give it a week or so. Thanks.

-- 
Denys
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [RFC][PATCH] vis: mark as compatible with dra7xx family

2019-11-13 Thread Denys Dmytriyenko
From: Denys Dmytriyenko 

Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/vis-fw/vis_01.50.07.15.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/vis-fw/vis_01.50.07.15.bb 
b/recipes-bsp/vis-fw/vis_01.50.07.15.bb
index 5b9834c..6eaf8de 100644
--- a/recipes-bsp/vis-fw/vis_01.50.07.15.bb
+++ b/recipes-bsp/vis-fw/vis_01.50.07.15.bb
@@ -2,12 +2,12 @@ DESCRIPTION = "Radio Application Firmware"
 LICENSE = "TI-TSPA"
 LIC_FILES_CHKSUM = 
"file://${S}/J6_VIS_DEMO_LINUX_BINARY_01.50.07.15-Manifest.html;md5=a59aa54b9470f555cf086b91dca0afa3"
 
-COMPATIBLE_MACHINE = "dra7xx-evm"
+COMPATIBLE_MACHINE = "dra7xx"
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 PR = "r1"
 
-SRC_URI = 
"http://downloads.ti.com/dsps/dsps_public_sw/glsdk/vis/01_50_07_15/exports/vis-${MACHINE}-01.50.07.15.tar.gz;protocol=http";
+SRC_URI = 
"http://downloads.ti.com/dsps/dsps_public_sw/glsdk/vis/01_50_07_15/exports/vis-dra7xx-evm-01.50.07.15.tar.gz;protocol=http";
 
 SRC_URI[md5sum] = "fe8b00e398fb3b7ada0c15b601867acb"
 SRC_URI[sha256sum] = 
"6e2aa47ae892910616ebdc96646af778af9a59ca0657716ab4fa4b24a9afae69"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] am65xx-evm: add k3-am654-evm-prupwm.dtbo

2019-11-11 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am65xx-evm.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
index cc15d73..82959ce 100644
--- a/conf/machine/am65xx-evm.conf
+++ b/conf/machine/am65xx-evm.conf
@@ -18,6 +18,7 @@ KERNEL_DEVICETREE = " \
 ti/k3-am654-evm-oldi-lcd1evm.dtbo ti/k3-am654-evm-tc358876.dtbo \
 ti/k3-am654-pcie-usb2.dtbo ti/k3-am654-pcie-usb3.dtbo \
 ti/k3-am654-base-board-jailhouse.dtbo \
+ti/k3-am654-evm-prupwm.dtbo \
 "
 
 UBOOT_MACHINE = "am65x_evm_a53_defconfig"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][RFC 00/42] Unify PDK sources

2019-11-08 Thread Denys Dmytriyenko
On Thu, Nov 07, 2019 at 12:49:55PM -0500, Jacob Stiffler wrote:
> The PDK sources have been unified in a single git repository. To
> simplify maintenance, a bbclass is added to specify the source
> information. This class also extends the unpack task so that each
> recipe is only presented with its component sources. This leaves
> subsequent tasks (do_compile, etc) identical to previous sources.
> 
> The source repo is not yet available, so submit as an RFC for now.

Overall seems fine, but not clear about the version strategy - most recipes 
drop PV and bump PE, but not all. How would that be handled? Also, not clear 
about the licensing - will it be the same for entire PDK? I noticed at least 
one recipe changed LIC_FILES_CHKSUM w/o details...

-- 
Denys
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [RFC][PATCH] omap-a15: add gc320 machine feature

2019-11-06 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/include/omap-a15.inc  | 2 +-
 recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/conf/machine/include/omap-a15.inc 
b/conf/machine/include/omap-a15.inc
index cc05536..a220828 100644
--- a/conf/machine/include/omap-a15.inc
+++ b/conf/machine/include/omap-a15.inc
@@ -36,4 +36,4 @@ MACHINE_GUI_CLASS = "smallscreen"
 UBI_VOLNAME = "rootfs"
 
 # List common SoC features, may need to add touchscreen for specific machines
-MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2 screen alsa 
ethernet gpu mmip dsp"
+MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2 screen alsa 
ethernet gpu mmip dsp gc320"
diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb 
b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
index e8c2f01..0221e39 100644
--- a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
+++ b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://git.ti.com/graphics/ti-gc320-libs";
 LICENSE = "TI-TSPA"
 LIC_FILES_CHKSUM = "file://Manifest.html;md5=a9121e8936ace09820d23f7626daaca5"
 
-COMPATIBLE_MACHINE = "dra7xx"
+COMPATIBLE_MACHINE = "omap-a15"
 
 CLEANBROKEN = "1"
 
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [RFC][PATCH] sgx-um, rogue-umlibs, gc320-libs: RRECOMMENDS on corresponding drivers

2019-11-06 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb   | 2 ++
 recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb | 4 +++-
 recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb   | 2 ++
 3 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb 
b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
index 0221e39..9487e72 100644
--- a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
+++ b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
@@ -12,6 +12,8 @@ BRANCH = "ti-${PV}"
 SRC_URI = 
"git://git.ti.com/graphics/ti-gc320-libs.git;protocol=git;branch=${BRANCH}"
 SRCREV = "c0afab259de59909cfe74c01f3f7fbaa147f94b5"
 
+RRECOMMENDS_${PN} = "ti-gc320-driver"
+
 # There's only hardfp version available
 python __anonymous() {
 tunes = d.getVar("TUNE_FEATURES")
diff --git a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb 
b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb
index 9cb863a..6729075 100644
--- a/recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb
+++ b/recipes-graphics/libgles/ti-img-rogue-umlibs_1.10.5371573.bb
@@ -27,7 +27,7 @@ PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2 
virtual/libgbm"
 DEPENDS += "libdrm wayland expat"
 RDEPENDS_${PN} += "bash"
 RDEPENDS_${PN} += "python-core"
-RDEPENDS_${PN} += "ti-img-rogue-driver wayland expat"
+RDEPENDS_${PN} += "wayland expat"
 
 RPROVIDES_${PN} = "libegl libgles1 libgles2 libgbm"
 RPROVIDES_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev"
@@ -41,6 +41,8 @@ RCONFLICTS_${PN} = "libegl libgles1 libgles2 libgbm"
 RCONFLICTS_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev"
 RCONFLICTS_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg"
 
+RRECOMMENDS_${PN} += "ti-img-rogue-driver"
+
 S = "${WORKDIR}/git"
 
 do_install () {
diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb 
b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
index ecf3ffc..8b0b305 100644
--- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
+++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
@@ -43,6 +43,8 @@ RCONFLICTS_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg 
libgbm-dbg"
 # The actual SONAME is libGLESv2.so.2, so need to explicitly specify RPROVIDES 
for .so.1 here
 RPROVIDES_${PN} += "libGLESv2.so.1"
 
+RRECOMMENDS_${PN} += "ti-sgx-ddk-km"
+
 S = "${WORKDIR}/git"
 
 do_install () {
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] am335x, am437x: bump max_leb_cnt again

2019-11-05 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am335x-evm.conf | 2 +-
 conf/machine/am437x-evm.conf | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/conf/machine/am335x-evm.conf b/conf/machine/am335x-evm.conf
index be3ed67..ad245dd 100644
--- a/conf/machine/am335x-evm.conf
+++ b/conf/machine/am335x-evm.conf
@@ -24,7 +24,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 # UBI: logical eraseblock size:126976 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 1988 LEBs
-MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 9300"
+MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 9800"
 
 # do ubiattach /dev/ubi_ctrl -m 7 -O 2048
 # from dmesg:
diff --git a/conf/machine/am437x-evm.conf b/conf/machine/am437x-evm.conf
index fd6b379..e7d3a98 100644
--- a/conf/machine/am437x-evm.conf
+++ b/conf/machine/am437x-evm.conf
@@ -22,7 +22,7 @@ SERIAL_CONSOLES = "115200;ttyS0"
 # UBI: logical eraseblock size:253952 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 994 LEBs
-MKUBIFS_ARGS = "-F -m 4096 -e 253952 -c 4500"
+MKUBIFS_ARGS = "-F -m 4096 -e 253952 -c 4800"
 
 # do ubiattach /dev/ubi_ctrl -m 11 -O 4096
 # from dmesg:
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] am335x-evm: bump max_leb_cnt

2019-11-01 Thread Denys Dmytriyenko
From: Denys Dmytriyenko 

Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am335x-evm.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/am335x-evm.conf b/conf/machine/am335x-evm.conf
index d1e1603..be3ed67 100644
--- a/conf/machine/am335x-evm.conf
+++ b/conf/machine/am335x-evm.conf
@@ -24,7 +24,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 # UBI: logical eraseblock size:126976 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 1988 LEBs
-MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 9200"
+MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 9300"
 
 # do ubiattach /dev/ubi_ctrl -m 7 -O 2048
 # from dmesg:
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 5] ipc-lld: inherit update-alternatives for softlink

2019-10-31 Thread Denys Dmytriyenko
This breaks am65xx:

| make -C 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/drv/ipc/examples/echo_test
  xdc_configuro
| make[1]: Entering directory 
'/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/drv/ipc/examples/echo_test'
| # Invoking configuro...
| /bin/mkdir -p 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/git/examples/yocto_bin
| 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot-native/usr/share/ti/ti-xdctools-tree/xs
 xdc.tools.configuro --generationOnly -o 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/git/examples/yocto_bin/ipc_echo_test/obj/am65xx_evm/mpu1_0/release/configuro
 -t gnu.targets.arm.A53F -p "ti.platforms.cortexA:AM65X" \
|-r release -b  --ol 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/git/examples/yocto_bin/ipc_echo_test/obj/am65xx_evm/mpu1_0/release/configuro/linker_mod.cmd
 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/build/am65xx/sysbios_a53.cfg
| xdc.tools.configuro: extraneous arguments ignored: 
'/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/build/am65xx/sysbios_a53.cfg
 ...'
| Usage: xs xdc.tools.configuro [--help]
|   [-v | -q]
|   [-@ optionsfile]
|   [-o outdir]
|   [-b config_bld | -c codegen_dir | --cb]
|   [-t target] [-p platform[:instance]] [-r profile]
|   [-Dname=value]
|   [-w | -x regexp]
|   [--rtsName pkg_name]
|   [--cfgArgs args_string]
|   [--linkTemplate linker_template]
|   [--pkg] [--generationOnly]
|   [--compileOptions compile_options_string]
|   [--linkOptions linker_options_string]
|   [--oc compiler.opt] [--ol linker.cmd]
|   infile.cfg
| js: 
"/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot-native/usr/share/ti/ti-xdctools-tree/packages/xdc/tools/Cmdr.xs",
 line 52: Error: xdc.tools.configuro: Error: can't open input file 
'/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/git/examples/yocto_bin/ipc_echo_test/obj/am65xx_evm/mpu1_0/release/configuro/linker_mod.cmd'
| 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/build/makerules/rules_a53.mk:268:
 recipe for target 
'/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/git/examples/yocto_bin/ipc_echo_test/obj/am65xx_evm/mpu1_0/release/configuro/package/cfg/sysbios_a53_pa53fg.c'
 failed
| make[1]: *** 
[/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/git/examples/yocto_bin/ipc_echo_test/obj/am65xx_evm/mpu1_0/release/configuro/package/cfg/sysbios_a53_pa53fg.c]
 Error 1
| make[1]: Leaving directory 
'/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/drv/ipc/examples/echo_test'
| 
/OE/arago-thud-next/build/arago-tmp-external-arm-toolchain/work/am65xx_evm-linux/ipc-lld-examples-rtos/01.00.00.00-r2/recipe-sysroot/usr/share/ti/ti-pdk-tree/packages/ti/build/comp_top.mk:380:
 recipe for target 'ipc_echo_test' failed
| make: *** [ipc_echo_test] Error 2
| ERROR: oe_runmake failed



On Thu, Oct 31, 2019 at 04:07:40PM -0400, Denys Dmytriyenko wrote:
> Thanks, I'll merge it to next along with packagegroup update.
> 
> 
> On Thu, Oct 31, 2019 at 02:53:09PM -0500, Santosh Jha wrote:
> > - Fixed softlink  - inherit update-alternatives
> > - Added all-bios binaries in install
> > 
> > Signed-off-by: Santosh Jha 
> > 
> > ---
> > Changes:
> >  - Removed 'inherit deploy'
> >  - Updated Commit message
> >  - Removed deploy appends
> >  - Fixed typo in commit message
> >  - Modified the script to use stripped image for
> >symbolic link
> >  - removed {PN}-src, renamed allrtos to rtos
> > ---
> > ---
> >  .../ipc-lld/ipc-l

[meta-ti] [thud/master][PATCH] arm-trusted-firmware: update to 2.2

2019-10-31 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 .../{arm-trusted-firmware_2.1.bb => arm-trusted-firmware_2.2.bb}  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename recipes-bsp/arm-trusted-firmware/{arm-trusted-firmware_2.1.bb => 
arm-trusted-firmware_2.2.bb} (93%)

diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb 
b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
similarity index 93%
rename from recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb
rename to recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
index a065cd8..f15570c 100644
--- a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.bb
+++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
@@ -7,7 +7,7 @@ Power State Coordination Interface (PSCI), Trusted Board Boot 
Requirements \
 HOMEPAGE = 
"http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html";
 
 LICENSE = "BSD"
-LIC_FILES_CHKSUM = "file://license.rst;md5=90153916317c204fade8b8df15739cde"
+LIC_FILES_CHKSUM = 
"file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89"
 
 inherit deploy
 
@@ -22,7 +22,7 @@ PV_append = "+git${SRCPV}"
 BRANCH = "ti-atf"
 SRC_URI = "git://git.ti.com/atf/arm-trusted-firmware.git;branch=${BRANCH}"
 
-SRCREV ?= "ce3f1512bfc3f346900178c5ef870fbef3ab205e"
+SRCREV ?= "e516a389ac12fbe1597f61fea80ed3f230b9c5fd"
 
 # Make ATF "aware" of OPTEE, no build dependency
 PACKAGECONFIG[optee] = "SPD=opteed"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] am437x-evm: bump max_leb_cnt

2019-10-31 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am437x-evm.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/am437x-evm.conf b/conf/machine/am437x-evm.conf
index b1db8b5..fd6b379 100644
--- a/conf/machine/am437x-evm.conf
+++ b/conf/machine/am437x-evm.conf
@@ -22,7 +22,7 @@ SERIAL_CONSOLES = "115200;ttyS0"
 # UBI: logical eraseblock size:253952 bytes
 # from ubiattach stdout:
 # UBI device number 0, total 994 LEBs
-MKUBIFS_ARGS = "-F -m 4096 -e 253952 -c 4400"
+MKUBIFS_ARGS = "-F -m 4096 -e 253952 -c 4500"
 
 # do ubiattach /dev/ubi_ctrl -m 11 -O 4096
 # from dmesg:
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 5] ipc-lld: inherit update-alternatives for softlink

2019-10-31 Thread Denys Dmytriyenko
Thanks, I'll merge it to next along with packagegroup update.


On Thu, Oct 31, 2019 at 02:53:09PM -0500, Santosh Jha wrote:
> - Fixed softlink  - inherit update-alternatives
> - Added all-bios binaries in install
> 
> Signed-off-by: Santosh Jha 
> 
> ---
> Changes:
>  - Removed 'inherit deploy'
>  - Updated Commit message
>  - Removed deploy appends
>  - Fixed typo in commit message
>  - Modified the script to use stripped image for
>symbolic link
>  - removed {PN}-src, renamed allrtos to rtos
> ---
> ---
>  .../ipc-lld/ipc-lld-examples-rtos_git.bb  | 78 +--
>  recipes-bsp/ipc-lld/ipc-lld.inc   |  2 +-
>  2 files changed, 38 insertions(+), 42 deletions(-)
> 
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> index 75db2162..6a3e233f 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> +++ b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> @@ -2,11 +2,16 @@ SUMMARY = "echo_test for IPC-LLD"
>  
>  require ipc-lld.inc
>  
> +inherit update-alternatives
> +
>  DEPENDS += " ipc-lld-rtos common-csl-ip-rtos sciclient-rtos board-rtos"
>  
> -REMOTE_FW_DIR = "${S}/examples/echo_test/yocto_bin"
> +REMOTE_FW_DIR = "${S}/examples/yocto_bin"
>  REMOTE_FW_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_test/bin"
>  REMOTE_FWB_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_testb/bin"
> +RTOS_ALL_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex02_bios_multicore_echo_test/bin"
> +RTOS_2_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex01_bios_2core_echo_test/bin"
> +LINUX_2_CORES_BIN_DIR = 
> "${REMOTE_FW_DIR}/ex03_linux_bios_2core_echo_test/bin"
>  
>  DST_BIN_PATH = "${base_libdir}/firmware/pdk-ipc"
>  
> @@ -25,13 +30,18 @@ do_compile() {
>  }
>  
>  do_install() {
> +CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
>  install -d ${D}${DST_BIN_PATH}
>  
> +cp ${CP_ARGS} ${REMOTE_FW_DIR}/ex02_bios_multicore_echo_test/bin -d 
> ${D}/ex02_bios_multicore_echo_test
> +cp ${CP_ARGS} ${REMOTE_FW_DIR}/ex01_bios_2core_echo_test/bin -d 
> ${D}/ex01_bios_2core_echo_test
> +cp ${CP_ARGS} ${REMOTE_FW_DIR}/ex03_linux_bios_2core_echo_test/bin -d 
> ${D}/ex03_linux_bios_2core_echo_test
> +
>  for board in ${TI_PDK_LIMIT_BOARDS}
>  do
>  for core in ${TI_PDK_LIMIT_CORES}
>  do
> -install -m 0644 
> ${REMOTE_FW_BIN_DIR}/$board/ipc_echo_test_${core}_release.x* 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FW_BIN_DIR}/$board/ipc_echo_test_${core}_release* ${D}${DST_BIN_PATH}
>  
>  #removing map files copied in previous line
>  rm ${D}${DST_BIN_PATH}/*.map
> @@ -51,6 +61,13 @@ do_install_append_j7-evm() {
>  install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu2_1_release.xer5f 
> ${D}${DST_BIN_PATH}
>  install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_0_release.xer5f 
> ${D}${DST_BIN_PATH}
>  install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_1_release.xer5f 
> ${D}${DST_BIN_PATH}
> +
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu1_0_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu1_1_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu2_0_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu2_1_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_0_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_1_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
>  }
>  
>  
> @@ -101,53 +118,32 @@ ALTERNATIVE_LINK_NAME[j7-c71_0-fw] = 
> "${base_libdir}/firmware/${TARGET_C7X}"
>  
>  # Create the firmware alternatives
>  
> -ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release.xer5f"
> -ALTERNATIVE_TARGET[am65x-mcu-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release.xer5f"
> +ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release_strip.xer5f"
> +ALTERNATIVE_TARGET[am65x-mcu-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
>  
> -ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release.xer5f"
> -ALTERNATIVE_TARGET[j7-mcu-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_0_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_1_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f1_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_0_release.xer5f"
> 

[meta-ti] [thud/master][PATCHv2] ti-sgx-ddk-um: update SRCREV to pick up Mesa-based EGL/GLES libraries

2019-10-31 Thread Denys Dmytriyenko
From: "e-ru...@ti.com" 

This is the initial step toward Mesa-based EGL/GLES libraries which
support all the required EGL 1.5 extensions. We plan to provide a
Mesa-pvr recipe to build Mesa from source and SGX/DDK patches where
ti-sgx-ddk-um shall provide the EGL/GLES plugins only at the next step.

Signed-off-by: Eric Ruei 
Signed-off-by: Denys Dmytriyenko 
---
v2 - re-enable stripping

 recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb | 11 +--
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb 
b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
index 7a6f013..ecf3ffc 100644
--- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
+++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
@@ -11,7 +11,7 @@ PR = "r34"
 BRANCH = "ti-img-sgx/thud/${PV}"
 
 SRC_URI = 
"git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git;protocol=git;branch=${BRANCH}"
-SRCREV = "87d7e5c1e4db1bab048939c9719059d549c1e8dd"
+SRCREV = "2a2e5bb090ced870d73ed4edbc54793e952cc6d8"
 
 TARGET_PRODUCT_omap-a15 = "jacinto6evm"
 TARGET_PRODUCT_ti33x = "ti335x"
@@ -47,7 +47,9 @@ S = "${WORKDIR}/git"
 
 do_install () {
 oe_runmake install DESTDIR=${D} TARGET_PRODUCT=${TARGET_PRODUCT}
-ln -sf libGLESv2.so.${PV} ${D}${libdir}/libGLESv2.so.1
+ln -sf libGLESv2.so ${D}${libdir}/libGLESv2.so.1
+
+rm -rf ${D}${includedir}/GL
 
 chown -R root:root ${D}
 }
@@ -58,14 +60,11 @@ FILES_${PN} +=  "${includedir}/*"
 FILES_${PN} +=  "${sysconfdir}/*"
 
 PACKAGES =+ "${PN}-plugins"
-FILES_${PN}-plugins = "${libdir}/libsrv_init.so ${libdir}/libsrv_um.so 
${libdir}/libglslcompiler.so ${libdir}/libPVRScopeServices.so 
${libdir}/libGLESv2.so ${libdir}/libEGL.so ${libdir}/libGLES_CM.so 
${libdir}/libpvrDRMWSEGL.so  ${libdir}/libpvrGBMWSEGL.so  
${libdir}/libpvrws_WAYLAND.so"
+FILES_${PN}-plugins = "${libdir}/libsrv_init.so ${libdir}/libsrv_um.so 
${libdir}/libglslcompiler.so ${libdir}/libPVRScopeServices.so 
${libdir}/libGLESv2.so ${libdir}/libEGL.so ${libdir}/libGLESv1_CM.so 
${libdir}/libGLES_CM.so ${libdir}/libGLESv1_PVR_MESA.so 
${libdir}/libGLESv2_PVR_MESA.so"
 RDEPENDS_${PN} += "${PN}-plugins"
 
 ALLOW_EMPTY_${PN}-plugins = "1"
 
-INHIBIT_PACKAGE_STRIP = "1"
-INHIBIT_SYSROOT_STRIP = "1"
-
 INSANE_SKIP_${PN} += "dev-so ldflags useless-rpaths"
 INSANE_SKIP_${PN}-plugins = "dev-so"
 INSANE_SKIP_${PN} += "already-stripped"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 4] ipc-lld: inherit update-alternatives for softlink

2019-10-31 Thread Denys Dmytriyenko
Any updates on the other questions regarding ${PN}-allrtos and ${PN}-src 
pacakges?


On Wed, Oct 30, 2019 at 04:59:54PM -0500, Santosh Jha wrote:
> - Fixed softlink  - inherit update-alternatives
> - Added all-bios binaries in install
> 
> Signed-off-by: Santosh Jha 
> 
> ---
> Changes:
>  - Removed 'inherit deploy'
>  - Updated Commit message
>  - Removed deploy appends
>  - Fixed typo in commit message
>  - Modified the script to use stripped image for
>symbolic link
> ---
> ---
>  .../ipc-lld/ipc-lld-examples-rtos_git.bb  | 76 +--
>  recipes-bsp/ipc-lld/ipc-lld.inc   |  2 +-
>  2 files changed, 36 insertions(+), 42 deletions(-)
> 
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> index 75db2162..d20f871a 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> +++ b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> @@ -2,11 +2,16 @@ SUMMARY = "echo_test for IPC-LLD"
>  
>  require ipc-lld.inc
>  
> +inherit update-alternatives
> +
>  DEPENDS += " ipc-lld-rtos common-csl-ip-rtos sciclient-rtos board-rtos"
>  
> -REMOTE_FW_DIR = "${S}/examples/echo_test/yocto_bin"
> +REMOTE_FW_DIR = "${S}/examples/yocto_bin"
>  REMOTE_FW_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_test/bin"
>  REMOTE_FWB_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_testb/bin"
> +RTOS_ALL_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex02_bios_multicore_echo_test/bin"
> +RTOS_2_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex01_bios_2core_echo_test/bin"
> +LINUX_2_CORES_BIN_DIR = 
> "${REMOTE_FW_DIR}/ex03_linux_bios_2core_echo_test/bin"
>  
>  DST_BIN_PATH = "${base_libdir}/firmware/pdk-ipc"
>  
> @@ -31,7 +36,7 @@ do_install() {
>  do
>  for core in ${TI_PDK_LIMIT_CORES}
>  do
> -install -m 0644 
> ${REMOTE_FW_BIN_DIR}/$board/ipc_echo_test_${core}_release.x* 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FW_BIN_DIR}/$board/ipc_echo_test_${core}_release* ${D}${DST_BIN_PATH}
>  
>  #removing map files copied in previous line
>  rm ${D}${DST_BIN_PATH}/*.map
> @@ -51,6 +56,13 @@ do_install_append_j7-evm() {
>  install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu2_1_release.xer5f 
> ${D}${DST_BIN_PATH}
>  install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_0_release.xer5f 
> ${D}${DST_BIN_PATH}
>  install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_1_release.xer5f 
> ${D}${DST_BIN_PATH}
> +
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu1_0_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu1_1_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu2_0_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu2_1_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_0_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
> +install -m 0644 
> ${REMOTE_FWB_BIN_DIR}/$board/ipc_echo_testb_mcu3_1_release_strip.xer5f 
> ${D}${DST_BIN_PATH}
>  }
>  
>  
> @@ -101,52 +113,34 @@ ALTERNATIVE_LINK_NAME[j7-c71_0-fw] = 
> "${base_libdir}/firmware/${TARGET_C7X}"
>  
>  # Create the firmware alternatives
>  
> -ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release.xer5f"
> -ALTERNATIVE_TARGET[am65x-mcu-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release.xer5f"
> +ALTERNATIVE_TARGET[am65x-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_0_release_strip.xer5f"
> +ALTERNATIVE_TARGET[am65x-mcu-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release_strip.xer5f"
>  
> -ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release.xer5f"
> -ALTERNATIVE_TARGET[j7-mcu-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu1_1_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_0_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f0_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu2_1_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f1_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_0_release.xer5f"
> -ALTERNATIVE_TARGET[j7-main-r5f1_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_mcu3_1_release.xer5f"
> -ALTERNATIVE_TARGET[j7-c66_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c66xdsp_1_release.xe66"
> -ALTERNATIVE_TARGET[j7-c66_1-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c66xdsp_2_release.xe66"
> -ALTERNATIVE_TARGET[j7-c71_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test_c7x_1_release.xe71"
> +ALTERNATIVE_TARGET[j7-mcu-r5f0_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_testb_mcu1_0_release_s

Re: [meta-ti] [EXTERNAL] Re: [PATCH] ti-sgx-ddk-um: update SRCREV to pick up Mesa-based EGL/GLES libraries

2019-10-30 Thread Denys Dmytriyenko
On Wed, Oct 30, 2019 at 11:14:34AM -0400, Ruei, Eric wrote:
> Hi, guys:
> 
> Is there anything that we do regarding the large package size (1M to 8M)?

All the standard libs in /usr/lib get stripped properly.
But there's a new /usr/lib/dri/pvr_dri.so that is 28 MB even stripped. Is it 
supposed to be this large?

-- 
Denys


> Best regards,
> 
> Eric
> 
> On 10/30/2019 11:06 AM, Denys Dmytriyenko wrote:
> >On Wed, Oct 30, 2019 at 10:58:31AM -0400, Andrew F. Davis wrote:
> >>On 10/30/19 10:53 AM, Ruei, Eric wrote:
> >>>On 10/30/2019 9:53 AM, Tammana, Gowtham wrote:
> >>>>
> >>>>
> >>>>>-Original Message-
> >>>>>From: meta-ti-boun...@yoctoproject.org [mailto:meta-ti-
> >>>>>boun...@yoctoproject.org] On Behalf Of Davis, Andrew
> >>>>>Sent: Wednesday, October 30, 2019 8:36 AM
> >>>>>To: Ruei, Eric; Ruei, Eric; meta-ti@yoctoproject.org
> >>>>>Subject: [EXTERNAL] Re: [meta-ti] [PATCH] ti-sgx-ddk-um: update
> >>>>>SRCREV to pick
> >>>>>up Mesa-based EGL/GLES libraries
> >>>>>
> >>>>>On 10/30/19 9:31 AM, Ruei, Eric wrote:
> >>>>>>On 10/30/2019 9:22 AM, Andrew F. Davis wrote:
> >>>>>>>On 10/29/19 9:20 AM, Eric Ruei wrote:
> >>>>>>>>This is the initial step toward Mesa-based EGL/GLES libraries which
> >>>>>>>>support all the required EGL 1.5 extensions. We plan to provide a
> >>>>>>>>Mesa-pvr recipe to build Mesa from source and SGX/DDK patches where
> >>>>>>>>ti-sgx-ddk-um shall provide the EGL/GLES plugins only at the next
> >>>>>>>>step.
> >>>>>>>>
> >>>>>>>>Signed-off-by: Eric Ruei 
> >>>>>>>>---
> >>>>>>>>    recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb | 8
> >>>>>>>>+---
> >>>>>>>>    1 file changed, 5 insertions(+), 3 deletions(-)
> >>>>>>>>
> >>>>>>>>diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >>>>>>>>b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >>>>>>>>index 7a6f013e..3991d917 100644
> >>>>>>>>--- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >>>>>>>>+++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >>>>>>>>@@ -11,7 +11,7 @@ PR = "r34"
> >>>>>>>>    BRANCH = "ti-img-sgx/thud/${PV}"
> >>>>>>>>      SRC_URI =
> >>>>>>>>"git://git.ti.com/graphics/omap5-sgx-ddk-um-
> >>>>>linux.git;protocol=git;branch=${BRANCH}"
> >>>>>>>>
> >>>>>>>>-SRCREV = "87d7e5c1e4db1bab048939c9719059d549c1e8dd"
> >>>>>>>>+SRCREV = "2a2e5bb090ced870d73ed4edbc54793e952cc6d8"
> >>>>>>>>      TARGET_PRODUCT_omap-a15 = "jacinto6evm"
> >>>>>>>>    TARGET_PRODUCT_ti33x = "ti335x"
> >>>>>>>>@@ -47,7 +47,9 @@ S = "${WORKDIR}/git"
> >>>>>>>>      do_install () {
> >>>>>>>>    oe_runmake install DESTDIR=${D}
> >>>>>>>>TARGET_PRODUCT=${TARGET_PRODUCT}
> >>>>>>>>-    ln -sf libGLESv2.so.${PV} ${D}${libdir}/libGLESv2.so.1
> >>>>>>>>+    ln -sf libGLESv2.so ${D}${libdir}/libGLESv2.so.1
> >>>>>>>>+
> >>>>>>>>+    rm -rf ${D}${includedir}/GL
> >>>>>>>
> >>>>>>>
> >>>>>>>Why remove this?
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>There is another component provides GL header files.
> >>>>>>Denys: how do we resolve this conflict?
> >>>>>>
> >>>>>
> >>>>>
> >>>>>The DSP OpenCL implementation? That package needs fixed, not this one,
> >>>>>the OpenGL implementation (this driver) should provide the GL headers.
> >>>>
> >>>>We don't support desktop GL, they shouldn't come from this package.
> >>>>
> >>>>Gowtham
> >>>>
> >>>
> >>>Andrew:
> >>>
> >>>Do you agree? I can keep the line here tentatively until GL is removed
> >>>from the package itself.
> >>>
> >>
> >>
> >>I still believe we should be shipping the GL headers in this package.
> >>But I won't object to removing the headers temporarily using this recipe
> >>until the conflicting ones can be removed from the OpenCL package.
> >
> >Previously DDK only provided headers in these dirs: EGL, GLES, GLES2, KHR, 
> >gbm.
> >
> >And OpenCL required GL headers, hence there was a "hacky" package created
> >specifically for that:
> >http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-extras/recipes-ti/ocl/ocl-gl-headers_git.bb;hb=HEAD
> >
> >If DDK now properly provides GL headers, the other package can be dropped.
> >
> >But the question remains - should DDK actually provide GL headers, even 
> >though
> >it doesn't provide full support for it?
> >
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 2] ipc-lld: inherit update-alternatives for softlink

2019-10-30 Thread Denys Dmytriyenko
On Tue, Oct 15, 2019 at 07:20:42AM -0500, Santosh Jha wrote:
> - Fixed softlink  - inherit update-alternatives
> - Added all-bios binaries in install
> 
> ---
> Changes:
>  - Removed 'inherit deploy'
>  - Updated Commit message
>  - Removed deploy appends
>  - Fixed typo in commit message
> ---
> 
> Signed-off-by: Santosh Jha 
> 
> Signed-off-by: Santosh Jha 

The Signed-off-by will not get into the commit (why there are 2?), because it 
is after --- line that lists the revision changes.


> ---
>  .../ipc-lld/ipc-lld-examples-rtos_git.bb  | 45 +++
>  recipes-bsp/ipc-lld/ipc-lld.inc   |  2 +-
>  2 files changed, 17 insertions(+), 30 deletions(-)
> 
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> index 75db2162..e4e8f09f 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> +++ b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> @@ -2,11 +2,16 @@ SUMMARY = "echo_test for IPC-LLD"
>  
>  require ipc-lld.inc
>  
> +inherit update-alternatives
> +
>  DEPENDS += " ipc-lld-rtos common-csl-ip-rtos sciclient-rtos board-rtos"
>  
> -REMOTE_FW_DIR = "${S}/examples/echo_test/yocto_bin"
> +REMOTE_FW_DIR = "${S}/examples/yocto_bin"
>  REMOTE_FW_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_test/bin"
>  REMOTE_FWB_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_testb/bin"
> +RTOS_ALL_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex02_bios_multicore_echo_test/bin"
> +RTOS_2_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex01_bios_2core_echo_test/bin"
> +LINUX_2_CORES_BIN_DIR = 
> "${REMOTE_FW_DIR}/ex03_linux_bios_2core_echo_test/bin"

Do we need to package all the FW images? Usually we have additional 
-rtos recipes and packages if those are not used in Linux.


>  DST_BIN_PATH = "${base_libdir}/firmware/pdk-ipc"
>  
> @@ -116,37 +121,19 @@ ALTERNATIVE_TARGET[j7-c71_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test
>  
>  ALTERNATIVE_PRIORITY = "10"
>  
> -# copy the executables into the deploy directory
> -
> -do_deploy() {
> -:
> -}
> -
> -do_deploy_am65xx() {
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_1_release.xer5f 
> ${DEPLOYDIR}/
> -}
> +#add source and all rtos binaries package
> +PACKAGES =+ "${PN}-src"

Why is this needed? You should either use sourceipk in meta-arago, or create a 
different package than ${PN}-src.


> +PACKAGES =+ "${PN}-allrtos"

What's the purpose of this package? Should it be ${PN}-rtos?


> -do_deploy_j7-evm() {
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu1_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu1_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu2_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu2_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu2_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu2_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu3_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu3_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu3_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu3_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_c66xdsp_1_release.xe66 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_c66xdsp_2_release.xe66 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_c7x_1_release.xe71 
> ${DEPLOYDIR}/
> -}
>  # make sure that lib/firmware, and all its contents are part of the package
>  FILES_${PN} += "${base_libdir}/firmware"
> -FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +FILES_${PN}-src += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +FILES_${PN}-allrtos_append_am65xx += "${RTOS_ALL_CORES_BIN_DIR}/am65xx_evm"
> +FILES_${PN}-allrtos_append_j7-evm += "${RTOS_ALL_CORES_BIN_DIR}/j721e_evm"
> +FILES_${PN}-allrtos_append_am65xx += "${RTOS_2_CORES_BIN_DIR}/am65xx_evm"
> +FILES_${PN}-allrtos_append_j7-evm += "${RTOS_2_CORES_BIN_DIR}/j721e_evm"
> +FILES_${PN}-allrtos_append_am65xx += "${LINUX_2_CORES_BIN_DIR}/am65xx_evm"
> +FILES_${PN}-allrtos_append_j7-evm += "${LINUX_2_CORES_BIN_DIR}/j721e_evm"
>  
>  INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
>  
> diff --git a/recipes-bsp/ipc-lld/ipc-lld.inc b/recipes-bsp/ipc-lld/ipc-lld.inc
> index 06683a06..243678f4 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld.inc
> +++ b/recipes-bsp/ipc-lld/ipc-lld.inc
> @@ -18,7 +18,7 @@ SRC_URI = 
> "${IPCLLD_GIT_URI};protocol=${IPCLLD_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${IPCLLD_SRCREV}"
>  PV = "01.00

Re: [meta-ti] [EXTERNAL] Re: [PATCH] ti-sgx-ddk-um: update SRCREV to pick up Mesa-based EGL/GLES libraries

2019-10-30 Thread Denys Dmytriyenko
On Wed, Oct 30, 2019 at 10:58:31AM -0400, Andrew F. Davis wrote:
> On 10/30/19 10:53 AM, Ruei, Eric wrote:
> > On 10/30/2019 9:53 AM, Tammana, Gowtham wrote:
> >>
> >>
> >>> -Original Message-
> >>> From: meta-ti-boun...@yoctoproject.org [mailto:meta-ti-
> >>> boun...@yoctoproject.org] On Behalf Of Davis, Andrew
> >>> Sent: Wednesday, October 30, 2019 8:36 AM
> >>> To: Ruei, Eric; Ruei, Eric; meta-ti@yoctoproject.org
> >>> Subject: [EXTERNAL] Re: [meta-ti] [PATCH] ti-sgx-ddk-um: update
> >>> SRCREV to pick
> >>> up Mesa-based EGL/GLES libraries
> >>>
> >>> On 10/30/19 9:31 AM, Ruei, Eric wrote:
>  On 10/30/2019 9:22 AM, Andrew F. Davis wrote:
> > On 10/29/19 9:20 AM, Eric Ruei wrote:
> >> This is the initial step toward Mesa-based EGL/GLES libraries which
> >> support all the required EGL 1.5 extensions. We plan to provide a
> >> Mesa-pvr recipe to build Mesa from source and SGX/DDK patches where
> >> ti-sgx-ddk-um shall provide the EGL/GLES plugins only at the next
> >> step.
> >>
> >> Signed-off-by: Eric Ruei 
> >> ---
> >>    recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb | 8
> >> +---
> >>    1 file changed, 5 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >> b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >> index 7a6f013e..3991d917 100644
> >> --- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >> +++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> >> @@ -11,7 +11,7 @@ PR = "r34"
> >>    BRANCH = "ti-img-sgx/thud/${PV}"
> >>      SRC_URI =
> >> "git://git.ti.com/graphics/omap5-sgx-ddk-um-
> >>> linux.git;protocol=git;branch=${BRANCH}"
> >>
> >> -SRCREV = "87d7e5c1e4db1bab048939c9719059d549c1e8dd"
> >> +SRCREV = "2a2e5bb090ced870d73ed4edbc54793e952cc6d8"
> >>      TARGET_PRODUCT_omap-a15 = "jacinto6evm"
> >>    TARGET_PRODUCT_ti33x = "ti335x"
> >> @@ -47,7 +47,9 @@ S = "${WORKDIR}/git"
> >>      do_install () {
> >>    oe_runmake install DESTDIR=${D}
> >> TARGET_PRODUCT=${TARGET_PRODUCT}
> >> -    ln -sf libGLESv2.so.${PV} ${D}${libdir}/libGLESv2.so.1
> >> +    ln -sf libGLESv2.so ${D}${libdir}/libGLESv2.so.1
> >> +
> >> +    rm -rf ${D}${includedir}/GL
> >
> >
> > Why remove this?
> >
> >
> 
>  There is another component provides GL header files.
>  Denys: how do we resolve this conflict?
> 
> >>>
> >>>
> >>> The DSP OpenCL implementation? That package needs fixed, not this one,
> >>> the OpenGL implementation (this driver) should provide the GL headers.
> >>
> >> We don't support desktop GL, they shouldn't come from this package.
> >>
> >> Gowtham
> >>
> > 
> > Andrew:
> > 
> > Do you agree? I can keep the line here tentatively until GL is removed
> > from the package itself.
> > 
> 
> 
> I still believe we should be shipping the GL headers in this package.
> But I won't object to removing the headers temporarily using this recipe
> until the conflicting ones can be removed from the OpenCL package.

Previously DDK only provided headers in these dirs: EGL, GLES, GLES2, KHR, gbm.

And OpenCL required GL headers, hence there was a "hacky" package created 
specifically for that:
http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-extras/recipes-ti/ocl/ocl-gl-headers_git.bb;hb=HEAD

If DDK now properly provides GL headers, the other package can be dropped.

But the question remains - should DDK actually provide GL headers, even though 
it doesn't provide full support for it?

-- 
Denys


> 
> 
> >>      chown -R root:root ${D}
> >>    }
> >> @@ -58,7 +60,7 @@ FILES_${PN} +=  "${includedir}/*"
> >>    FILES_${PN} +=  "${sysconfdir}/*"
> >>      PACKAGES =+ "${PN}-plugins"
> >> -FILES_${PN}-plugins = "${libdir}/libsrv_init.so
> >> ${libdir}/libsrv_um.so ${libdir}/libglslcompiler.so
> >> ${libdir}/libPVRScopeServices.so ${libdir}/libGLESv2.so
> >> ${libdir}/libEGL.so ${libdir}/libGLES_CM.so
> >> ${libdir}/libpvrDRMWSEGL.so  ${libdir}/libpvrGBMWSEGL.so
> >> ${libdir}/libpvrws_WAYLAND.so"
> >> +FILES_${PN}-plugins = "${libdir}/libsrv_init.so
> >> ${libdir}/libsrv_um.so ${libdir}/libglslcompiler.so
> >> ${libdir}/libPVRScopeServices.so ${libdir}/libGLESv2.so
> >> ${libdir}/libEGL.so ${libdir}/libGLESv1_CM.so ${libdir}/libGLES_CM.so
> >> ${libdir}/libGLESv1_PVR_MESA.so ${libdir}/libGLESv2_PVR_MESA.so"
> >>    RDEPENDS_${PN} += "${PN}-plugins"
> >
> >
> > The newer binaries after the DDK commit "um: Attempt to load shared
> > object with version extension automatically" do not need all this
> > plugin
> > stuff, it can all be dropped.
> >
> > Andrew
> >
> >
> >>      ALLOW_EMPTY_${PN}-plugins = "1"
> >>
> 
> >>> -- 
> >>> ___
> >>

Re: [meta-ti] [PATCH] ti-sgx-ddk-um: update SRCREV to pick up Mesa-based EGL/GLES libraries

2019-10-29 Thread Denys Dmytriyenko
On Tue, Oct 29, 2019 at 09:20:20AM -0400, Eric Ruei wrote:
> This is the initial step toward Mesa-based EGL/GLES libraries which
> support all the required EGL 1.5 extensions. We plan to provide a
> Mesa-pvr recipe to build Mesa from source and SGX/DDK patches where
> ti-sgx-ddk-um shall provide the EGL/GLES plugins only at the next step.

Eric,

The new binaries are huge. The compressed package went from 900 KB to 8 MB in 
size and now both AM3 and AM4 won't fit into allocated rootfs size...


> Signed-off-by: Eric Ruei 
> ---
>  recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb | 8 +---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb 
> b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> index 7a6f013e..3991d917 100644
> --- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> +++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> @@ -11,7 +11,7 @@ PR = "r34"
>  BRANCH = "ti-img-sgx/thud/${PV}"
>  
>  SRC_URI = 
> "git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git;protocol=git;branch=${BRANCH}"
> -SRCREV = "87d7e5c1e4db1bab048939c9719059d549c1e8dd"
> +SRCREV = "2a2e5bb090ced870d73ed4edbc54793e952cc6d8"
>  
>  TARGET_PRODUCT_omap-a15 = "jacinto6evm"
>  TARGET_PRODUCT_ti33x = "ti335x"
> @@ -47,7 +47,9 @@ S = "${WORKDIR}/git"
>  
>  do_install () {
>  oe_runmake install DESTDIR=${D} TARGET_PRODUCT=${TARGET_PRODUCT}
> -ln -sf libGLESv2.so.${PV} ${D}${libdir}/libGLESv2.so.1
> +ln -sf libGLESv2.so ${D}${libdir}/libGLESv2.so.1
> +
> +rm -rf ${D}${includedir}/GL
>  
>  chown -R root:root ${D}
>  }
> @@ -58,7 +60,7 @@ FILES_${PN} +=  "${includedir}/*"
>  FILES_${PN} +=  "${sysconfdir}/*"
>  
>  PACKAGES =+ "${PN}-plugins"
> -FILES_${PN}-plugins = "${libdir}/libsrv_init.so ${libdir}/libsrv_um.so 
> ${libdir}/libglslcompiler.so ${libdir}/libPVRScopeServices.so 
> ${libdir}/libGLESv2.so ${libdir}/libEGL.so ${libdir}/libGLES_CM.so 
> ${libdir}/libpvrDRMWSEGL.so  ${libdir}/libpvrGBMWSEGL.so  
> ${libdir}/libpvrws_WAYLAND.so"
> +FILES_${PN}-plugins = "${libdir}/libsrv_init.so ${libdir}/libsrv_um.so 
> ${libdir}/libglslcompiler.so ${libdir}/libPVRScopeServices.so 
> ${libdir}/libGLESv2.so ${libdir}/libEGL.so ${libdir}/libGLESv1_CM.so 
> ${libdir}/libGLES_CM.so ${libdir}/libGLESv1_PVR_MESA.so 
> ${libdir}/libGLESv2_PVR_MESA.so"
>  RDEPENDS_${PN} += "${PN}-plugins"
>  
>  ALLOW_EMPTY_${PN}-plugins = "1"
> -- 
> 2.17.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH] ti-display-sharing-fw: update to 06.01.00.00

2019-10-21 Thread Denys Dmytriyenko
On Mon, Oct 21, 2019 at 02:32:38PM -0700, Khem Raj wrote:
> On Thu, Oct 17, 2019 at 10:58 AM Denys Dmytriyenko  wrote:
> >
> > Signed-off-by: Denys Dmytriyenko 
> > ---
> >  .../ti-display-sharing-fw/ti-display-sharing-fw_git.bb| 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb 
> > b/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb
> > index db095d90..9115b6b4 100644
> > --- a/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb
> > +++ b/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb
> > @@ -3,7 +3,7 @@ SUMMARY = "TI Display Sharing Firmware"
> >  LICENSE = "TI-TFL"
> >  LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=b5aebf0668bdf95621259288c4a46d76"
> >
> > -PV = "00.09.00.00-git${SRCPV}"
> > +PV = "06.01.00.00+git${SRCPV}"
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >
> >  inherit deploy
> > @@ -11,7 +11,7 @@ inherit update-alternatives
> >
> >  PROTOCOL = "git"
> >  BRANCH = "ti-linux-firmware"
> > -SRCREV = "4a86f16df9b44798851e51fa465825710cda76cf"
> > +SRCREV = "e7be1ab85266c47236330e2909997d20fc62e312"
> >
> 
> I get
> 
> Cloning into bare repository
> 'TOPDIR/downloads/git2/git.ti.com.processor-firmware.ti-linux-firmware.git'...
> fatal: unable to connect to git.ti.com:
> git.ti.com[0: 198.47.28.207]: errno=Connection refused
> 
> 
> ERROR: Fetcher failure for URL:
> 'git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=ti-linux-firmware'.
> Unable to fetch URL from any source.
> 
> is this temporary ?

Hopefully temporary, but don't know for how long.
https://www.dallasnews.com/news/weather/2019/10/21/3-tornadoes-tear-through-dallas-leveling-homes-and-leaving-thousands-in-north-texas-without-power/

Let me know if you need mirror tarballs for those repo...

Denys


> >  SRC_URI = 
> > "git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=${PROTOCOL};branch=${BRANCH}"
> >
> > --
> > 2.17.1
> >
> > --
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [master][PATCH] ti-ipc: update 0001-Add-kernel-build-dir.patch

2019-10-17 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/ipc/ti-ipc/0001-Add-kernel-build-dir.patch | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/recipes-ti/ipc/ti-ipc/0001-Add-kernel-build-dir.patch 
b/recipes-ti/ipc/ti-ipc/0001-Add-kernel-build-dir.patch
index e612ddc..71d5b2b 100644
--- a/recipes-ti/ipc/ti-ipc/0001-Add-kernel-build-dir.patch
+++ b/recipes-ti/ipc/ti-ipc/0001-Add-kernel-build-dir.patch
@@ -1,4 +1,4 @@
-From 7d9f57983c6d14ac14f26987eddc555ea5c75d61 Mon Sep 17 00:00:00 2001
+From c3ada6bf49e6fcf7bc49e5bf09754f384838ca6a Mon Sep 17 00:00:00 2001
 From: Denys Dmytriyenko 
 Date: Mon, 27 Jul 2015 11:51:52 -0400
 Subject: [PATCH] Add kernel build dir
@@ -17,18 +17,18 @@ Signed-off-by: Denys Dmytriyenko 
  4 files changed, 14 insertions(+), 1 deletion(-)
 
 diff --git a/configure.ac b/configure.ac
-index f0b4b61..9b5d07c 100644
+index 4d4a559..84ac78b 100644
 --- a/configure.ac
 +++ b/configure.ac
 @@ -71,6 +71,7 @@ AC_SUBST([AM_LDFLAGS])
- AC_ARG_VAR(PLATFORM, Platform to build. Options are: 'OMAPL138' 'OMAP54XX' 
'66AK2E' 'TCI6630' 'TCI6636' 'TCI6638' '66AK2G' and 'DRA7XX'. If not defined 
all platforms will be built.)
+ AC_ARG_VAR(PLATFORM, Platform to build. Options are: 'OMAPL138' 'OMAP54XX' 
'66AK2E' 'TCI6630' 'TCI6636' 'TCI6638' '66AK2G' 'DRA7XX' and 'AM65XX'. If not 
defined all platforms will be built.)
  AC_ARG_VAR(CMEM_INSTALL_DIR, Installation path directory to the CMEM 
libraries)
  AC_ARG_VAR(KERNEL_INSTALL_DIR, Installation path to the Linux kernel.)
 +AC_ARG_VAR(KERNEL_BUILD_DIR, Path to the Linux kernel build artifacts.)
  AC_ARG_VAR(AF_RPMSG, Address Family used by the RPMSG driver)
  AC_ARG_VAR(DRM_PREFIX, Installation location to the DRM library.)
  
-@@ -111,6 +112,7 @@ AS_IF([test "x$PLATFORM" = "x"], [CMEM_INSTALL_DIR=])
+@@ -113,6 +114,7 @@ AS_IF([test "x$PLATFORM" = "x"], [CMEM_INSTALL_DIR=])
  AC_SUBST([PLATFORM])
  AC_SUBST([CMEM_INSTALL_DIR])
  AC_SUBST([KERNEL_INSTALL_DIR])
@@ -36,7 +36,7 @@ index f0b4b61..9b5d07c 100644
  AC_SUBST([AF_RPMSG])
  AC_SUBST([DRM_PREFIX])
  
-@@ -127,6 +129,7 @@ AM_CONDITIONAL([DRA7XX], [test "x$PLATFORM" = "xDRA7XX"])
+@@ -130,6 +132,7 @@ AM_CONDITIONAL([AM65XX], [test "x$PLATFORM" = "xAM65XX"])
  AM_CONDITIONAL([CMEM], [test "x$CMEM_INSTALL_DIR" != "x"])
  AM_CONDITIONAL([KDIR], [test "x$KERNEL_INSTALL_DIR" != "x"])
  AM_CONDITIONAL([KERNEL_INSTALL_DIR], [test -n "$KERNEL_INSTALL_DIR"])
@@ -44,7 +44,7 @@ index f0b4b61..9b5d07c 100644
  AM_CONDITIONAL([DRM], [test "x$DRM_PREFIX" != "x"])
  AM_CONDITIONAL([AF_RPMSG], [test -n "$AF_RPMSG"])
  
-@@ -157,6 +160,9 @@ You have configured to build for the '${PLATFORM}' platform
+@@ -160,6 +163,9 @@ You have configured to build for the '${PLATFORM}' platform
  Your KERNEL installation directory is set to:
  '${KERNEL_INSTALL_DIR}'
  
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] kselftests: re-add ptp into main RDEPENDS

2019-10-17 Thread Denys Dmytriyenko
Commit 371b7bb52225a3f7aadf57910aa9af3bf26c0e78 enabled ptp package, but
did not add it to RDEPENDS, fix it.

Signed-off-by: Denys Dmytriyenko 
---
 recipes-kernel/kselftests/kselftests_4.10.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-kernel/kselftests/kselftests_4.10.bb 
b/recipes-kernel/kselftests/kselftests_4.10.bb
index b28868f5..96263875 100644
--- a/recipes-kernel/kselftests/kselftests_4.10.bb
+++ b/recipes-kernel/kselftests/kselftests_4.10.bb
@@ -160,6 +160,7 @@ RDEPENDS_${PN} += "bash \
${PN}-net \
${PN}-nsfs \
${PN}-pstore \
+   ${PN}-ptp \
${PN}-ptrace \
${PN}-seccomp \
${PN}-sigaltstack \
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] ti-display-sharing-fw: update to 06.01.00.00

2019-10-17 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 .../ti-display-sharing-fw/ti-display-sharing-fw_git.bb| 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb 
b/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb
index db095d90..9115b6b4 100644
--- a/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb
+++ b/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb
@@ -3,7 +3,7 @@ SUMMARY = "TI Display Sharing Firmware"
 LICENSE = "TI-TFL"
 LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=b5aebf0668bdf95621259288c4a46d76"
 
-PV = "00.09.00.00-git${SRCPV}"
+PV = "06.01.00.00+git${SRCPV}"
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
 inherit deploy
@@ -11,7 +11,7 @@ inherit update-alternatives
 
 PROTOCOL = "git"
 BRANCH = "ti-linux-firmware"
-SRCREV = "4a86f16df9b44798851e51fa465825710cda76cf"
+SRCREV = "e7be1ab85266c47236330e2909997d20fc62e312"
 
 SRC_URI = 
"git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=${PROTOCOL};branch=${BRANCH}"
 
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 1] ipc-lld: inherit update-alternatives for softlink

2019-10-14 Thread Denys Dmytriyenko
On Fri, Oct 11, 2019 at 01:02:15PM -0500, Santosh Jha wrote:
> - Fixed softlink  - inherit update-alternatives
> - Added alli-bios binaries in install

What is alli-bios?


> ---

What version is this? It says [PATCH 1], which should be v2, v3, etc.


BTW, what's "allrtos" package down there?


> Changes:
>  - Removed 'inherit deploy'
>  - Updated Commit message
>  - Removed deploy appends
> ---
> 
> Signed-off-by: Santosh Jha 
> 
> Signed-off-by: Santosh Jha 
> ---
>  .../ipc-lld/ipc-lld-examples-rtos_git.bb  | 45 +++
>  recipes-bsp/ipc-lld/ipc-lld.inc   |  2 +-
>  2 files changed, 17 insertions(+), 30 deletions(-)
> 
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> index 75db2162..e4e8f09f 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> +++ b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> @@ -2,11 +2,16 @@ SUMMARY = "echo_test for IPC-LLD"
>  
>  require ipc-lld.inc
>  
> +inherit update-alternatives
> +
>  DEPENDS += " ipc-lld-rtos common-csl-ip-rtos sciclient-rtos board-rtos"
>  
> -REMOTE_FW_DIR = "${S}/examples/echo_test/yocto_bin"
> +REMOTE_FW_DIR = "${S}/examples/yocto_bin"
>  REMOTE_FW_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_test/bin"
>  REMOTE_FWB_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_testb/bin"
> +RTOS_ALL_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex02_bios_multicore_echo_test/bin"
> +RTOS_2_CORES_BIN_DIR = "${REMOTE_FW_DIR}/ex01_bios_2core_echo_test/bin"
> +LINUX_2_CORES_BIN_DIR = 
> "${REMOTE_FW_DIR}/ex03_linux_bios_2core_echo_test/bin"
>  
>  DST_BIN_PATH = "${base_libdir}/firmware/pdk-ipc"
>  
> @@ -116,37 +121,19 @@ ALTERNATIVE_TARGET[j7-c71_0-fw] = 
> "${base_libdir}/firmware/pdk-ipc/ipc_echo_test
>  
>  ALTERNATIVE_PRIORITY = "10"
>  
> -# copy the executables into the deploy directory
> -
> -do_deploy() {
> -:
> -}
> -
> -do_deploy_am65xx() {
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_1_release.xer5f 
> ${DEPLOYDIR}/
> -}
> +#add source and all rtos binaries package
> +PACKAGES =+ "${PN}-src"
> +PACKAGES =+ "${PN}-allrtos"
>  
> -do_deploy_j7-evm() {
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu1_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu1_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu1_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu2_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu2_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu2_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu2_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu3_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu3_0_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_mcu3_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FWB_BIN_DIR}/ipc_echo_testb_mcu3_1_release.xer5f 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_c66xdsp_1_release.xe66 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_c66xdsp_2_release.xe66 
> ${DEPLOYDIR}/
> -install ${REMOTE_FW_BIN_DIR}/ipc_echo_test_c7x_1_release.xe71 
> ${DEPLOYDIR}/
> -}
>  # make sure that lib/firmware, and all its contents are part of the package
>  FILES_${PN} += "${base_libdir}/firmware"
> -FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +FILES_${PN}-src += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +FILES_${PN}-allrtos_append_am65xx += "${RTOS_ALL_CORES_BIN_DIR}/am65xx_evm"
> +FILES_${PN}-allrtos_append_j7-evm += "${RTOS_ALL_CORES_BIN_DIR}/j721e_evm"
> +FILES_${PN}-allrtos_append_am65xx += "${RTOS_2_CORES_BIN_DIR}/am65xx_evm"
> +FILES_${PN}-allrtos_append_j7-evm += "${RTOS_2_CORES_BIN_DIR}/j721e_evm"
> +FILES_${PN}-allrtos_append_am65xx += "${LINUX_2_CORES_BIN_DIR}/am65xx_evm"
> +FILES_${PN}-allrtos_append_j7-evm += "${LINUX_2_CORES_BIN_DIR}/j721e_evm"
>  
>  INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
>  
> diff --git a/recipes-bsp/ipc-lld/ipc-lld.inc b/recipes-bsp/ipc-lld/ipc-lld.inc
> index 06683a06..243678f4 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld.inc
> +++ b/recipes-bsp/ipc-lld/ipc-lld.inc
> @@ -18,7 +18,7 @@ SRC_URI = 
> "${IPCLLD_GIT_URI};protocol=${IPCLLD_GIT_PROTOCOL};branch=${BRANCH}"
>  
>  SRCREV = "${IPCLLD_SRCREV}"
>  PV = "01.00.00.00"
> -PR = "r1"
> +PR = "r2"
>  
>  # Build with make instead of XDC
>  TI_PDK_XDCMAKE = "0"
> -- 
> 2.17.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti ma

[meta-ti] [thud/master][PATCH] am335x-hs-evm.conf: fix typo in machine description

2019-10-14 Thread Denys Dmytriyenko
There was a typo in machine description - AM435x instead of AM335x

Reported-by: Andrew F. Davis 
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am335x-hs-evm.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/am335x-hs-evm.conf b/conf/machine/am335x-hs-evm.conf
index 5f78965..7caa5bf 100644
--- a/conf/machine/am335x-hs-evm.conf
+++ b/conf/machine/am335x-hs-evm.conf
@@ -1,6 +1,6 @@
 #@TYPE: Machine
 #@NAME: AM335x HS EVM
-#@DESCRIPTION: Machine configuration for the TI AM435x HS EVM
+#@DESCRIPTION: Machine configuration for the TI AM335x HS EVM
 
 require conf/machine/am335x-evm.conf
 
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] pru-pwm-fw: add PRU PWM Firmware recipe

2019-10-08 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/pru/pru-pwm-fw_git.bb | 40 +++
 1 file changed, 40 insertions(+)
 create mode 100644 recipes-bsp/pru/pru-pwm-fw_git.bb

diff --git a/recipes-bsp/pru/pru-pwm-fw_git.bb 
b/recipes-bsp/pru/pru-pwm-fw_git.bb
new file mode 100644
index 000..0fe7987
--- /dev/null
+++ b/recipes-bsp/pru/pru-pwm-fw_git.bb
@@ -0,0 +1,40 @@
+SUMMARY = "Programmable Real-time Unit PWM Firmware"
+LICENSE = "BSD-3-Clause"
+
+LIC_FILES_CHKSUM = 
"file://main.c;beginline=1;endline=32;md5=893d6a0cf1644338ea96642c0db97f59"
+
+require recipes-ti/includes/ti-paths.inc
+
+COMPATIBLE_MACHINE = "am65xx"
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+# Below commit ID corresponds to "DEV.PRUSS_LLD.01.00.00.15B"
+SRCREV = "989f802266d52f50a6db8f2be6967eacd9d2b409"
+
+PV = "01.00.00.15B"
+
+BRANCH = "master"
+SRC_URI = 
"git://git.ti.com/keystone-rtos/pruss-lld.git;protocol=git;branch=${BRANCH}"
+
+DEPENDS = "ti-cgt-pru-native pru-icss common-csl-ip-rtos"
+
+S = "${WORKDIR}/git/example/apps/icssg_pwm/firmware/src"
+
+EXTRA_OEMAKE += " \
+PRU_CGT="${TI_CGT_PRU_INSTALL_DIR}" \
+PRU_SSP="${STAGING_DIR_TARGET}/usr" \
+PDK_INSTALL_DIR="${STAGING_DATADIR}/ti/ti-pdk-tree/packages" \
+"
+
+do_compile() {
+   oe_runmake
+}
+
+do_install() {
+   install -d ${D}/lib/firmware/ti-pruss
+   install -m 0644 ${S}/gen/pwm.out 
${D}/lib/firmware/ti-pruss/am65x-pru0-pwm-fw.elf
+}
+
+FILES_${PN} = "/lib/firmware"
+
+INSANE_SKIP_${PN} = "arch"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] jailhouse: update to ti2019.04-rc3 tag

2019-10-02 Thread Denys Dmytriyenko
This includes ramdisk alignment fix.

Signed-off-by: Denys Dmytriyenko 
---
 recipes-kernel/jailhouse/jailhouse_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
b/recipes-kernel/jailhouse/jailhouse_git.bb
index 409b3252..4186dc3a 100644
--- a/recipes-kernel/jailhouse/jailhouse_git.bb
+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
@@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = " \
 "
 
 PV = "0.10+git${SRCPV}"
-SRCREV = "8858ba60ab078d8e3e5317fd644f09c560775a99"
+SRCREV = "b3a68ac89d7ed955546eae91954b184ec1583ce3"
 BRANCH = "ti-jailhouse-0.10"
 
 SRC_URI = " \
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [master][PATCH] rwmem: moved to meta-oe, remove

2019-10-02 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/rwmem/rwmem_1.2.bb | 27 ---
 1 file changed, 27 deletions(-)
 delete mode 100644 recipes-bsp/rwmem/rwmem_1.2.bb

diff --git a/recipes-bsp/rwmem/rwmem_1.2.bb b/recipes-bsp/rwmem/rwmem_1.2.bb
deleted file mode 100644
index 0545b0c..000
--- a/recipes-bsp/rwmem/rwmem_1.2.bb
+++ /dev/null
@@ -1,27 +0,0 @@
-SUMMARY = "A small tool to read/write memory"
-LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
-
-DEPENDS += "python3"
-
-PV .= "+git${SRCPV}"
-
-SRCREV_rwmem = "cc296c5366a35a4c4271cfa3cc9831f6f34bfd9d"
-SRCREV_inih = "4b10c654051a86556dfdb634c891b6c3224c4109"
-SRCREV_pybind11 = "9a19306fbf30642ca331d0ec88e7da54a96860f9"
-
-SRCREV_FORMAT = "rwmem_inih_pybind11"
-
-SRC_URI = "git://github.com/tomba/rwmem.git;protocol=https;name=rwmem \
-   
git://github.com/benhoyt/inih.git;protocol=https;name=inih;nobranch=1;destsuffix=git/ext/inih
 \
-   
git://github.com/pybind/pybind11.git;protocol=https;name=pybind11;nobranch=1;destsuffix=git/ext/pybind11
 \
-   "
-
-S = "${WORKDIR}/git"
-
-inherit cmake pkgconfig
-
-do_install() {
-   install -D -m 0755 ${B}/bin/rwmem ${D}${bindir}/rwmem
-   install -D -m 0644 ${B}/lib/librwmem.a ${D}${libdir}/librwmem.a
-}
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master PATCH v2] recipes-bsp: ivshmem-uio: Add new recipe for ivshmem-uio driver

2019-10-01 Thread Denys Dmytriyenko
On Tue, Oct 01, 2019 at 02:57:41PM -0700, Khem Raj wrote:
> On Tue, Oct 1, 2019 at 1:07 PM Denys Dmytriyenko  wrote:
> 
> > On Mon, Sep 30, 2019 at 11:41:43PM -0700, Khem Raj wrote:
> > > On Fri, Sep 27, 2019 at 2:17 AM Nikhil Devshatwar 
> > wrote:
> > > >
> > > > This is external kernel module which enables userspace io over the
> > > > Jailhouse ivhsmem (inter VM shared memory)
> > > > This driver is useful to test the inter VM communication.
> > > >
> > > > Signed-off-by: Nikhil Devshatwar 
> > > > ---
> > > > Changes from v1:
> > > > * Split the ivshmem recipe separately
> > > > * Add summary and remove PACKAGE_ARCH define
> > > >
> > > >  recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb | 27
> > +++
> > > >  1 file changed, 27 insertions(+)
> > > >  create mode 100644 recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> > > >
> > > > diff --git a/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> > b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> > > > new file mode 100644
> > > > index 000..33fb946
> > > > --- /dev/null
> > > > +++ b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> > > > @@ -0,0 +1,27 @@
> > > > +DESCRIPTION =  "Kernel driver for IVSHMEM based UIO driver"
> > > > +SUMMARY = "Kernel module which registers a UIO (userspace io) device
> > for inter VM shared memory"
> > > > +HOMEPAGE = "https://github.com/henning-schild-work/ivshmem-guest-code
> > "
> > > > +LICENSE = "GPLv2"
> > > > +LIC_FILES_CHKSUM =
> > "file://COPYING;md5=0546a27aad86c83b75ad4ee6133e9d5e"
> > > > +
> > > > +inherit module
> > > > +
> > > > +RDEPENDS_${PN} = "jailhouse"
> > > > +
> > >
> > > jailhouse is marked as ti-soc specific, so please mark this recipe
> > > ti-soc specific as well. It will help meta-ti to live in a multi-BSP
> > > distros
> > >
> > >
> > http://jenkins.nas-admin.org/view/OE/job/oe_world_qemux86-64/1164/consoleFull
> > >
> > > if you could test meta-ti patches with one non-ti machine like qemux86
> > > or some such it will help catch this kind of errors
> >
> > That would only fail when building "world", but thanks for the report.
> 
> MACHINE=qemux86 bitbake  would do it
> This would really help the distros

Well, I do know how to break it specifically... :) BTW, building it directly 
like that with COMPATIBLE_MACHINE set would also fail with "Nothing PROVIDES" 
error.

My point was that people add recipes and expect them to only be included in an 
image for their machine. In their view they cannot understand how it would get 
into an x86 build on its own, unless someone consciously adds it to their 
image. Hence my comment about building "world". And in that case it would be 
safely skipped by COMPATIBLE_MACHINE and won't result in an error.


> > > > +PROTOCOL = "git"
> > > > +BRANCH = "jailhouse"
> > > > +SRCREV = "f3ad79881bebb6c6068966ee3d265d8034c20492"
> > > > +SRC_URI = "git://
> > github.com/henning-schild-work/ivshmem-guest-code.git;protocol=${PROTOCOL};branch=${BRANCH}
> > <http://github.com/henning-schild-work/ivshmem-guest-code.git;protocol=$%7BPROTOCOL%7D;branch=$%7BBRANCH%7D>
> > "
> > > > +
> > > > +S = "${WORKDIR}/git"
> > > > +
> > > > +EXTRA_OEMAKE += 'KDIR="${STAGING_KERNEL_DIR}"'
> > > > +
> > > > +do_compile_prepend() {
> > > > +cd ${S}/kernel_module/uio
> > > > +}
> > > > +
> > > > +do_install() {
> > > > +install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > > > +install -m 644 ${S}/kernel_module/uio/uio_ivshmem.ko
> > ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > > > +}
> > > > --
> > > > 1.9.1
> > > >
> > > > --
> > > > ___
> > > > meta-ti mailing list
> > > > meta-ti@yoctoproject.org
> > > > https://lists.yoctoproject.org/listinfo/meta-ti
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
> >
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master PATCH v3] recipes-bsp: ivshmem-uio: Add new recipe for ivshmem-uio driver

2019-10-01 Thread Denys Dmytriyenko
Since v2 was already merged, you can't just replace it with v3. But Khem has 
already provided a patch to fix it on top of v2. Thanks.


On Tue, Oct 01, 2019 at 03:41:57PM +0530, Nikhil Devshatwar wrote:
> This is external kernel module which enables userspace io over the
> Jailhouse ivhsmem (inter VM shared memory)
> This driver is useful to test the inter VM communication.
> 
> Signed-off-by: Nikhil Devshatwar 
> ---
> Changes from v2:
> * Define recipe to be compatible only for ti-soc
> 
> Changes from v1:
> * Split the ivshmem recipe separately
> * Add summary and remove PACKAGE_ARCH define
> 
>  recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb | 28 
> +++
>  1 file changed, 28 insertions(+)
>  create mode 100644 recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> 
> diff --git a/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb 
> b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> new file mode 100644
> index 000..d77c28e
> --- /dev/null
> +++ b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> @@ -0,0 +1,28 @@
> +SUMMARY =  "Kernel driver for IVSHMEM based UIO driver"
> +DESCRIPTION = "Kernel module which registers a UIO (userspace io) device for 
> inter VM shared memory"
> +HOMEPAGE = "https://github.com/henning-schild-work/ivshmem-guest-code";
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=0546a27aad86c83b75ad4ee6133e9d5e"
> +
> +inherit module
> +
> +RDEPENDS_${PN} = "jailhouse"
> +COMPATIBLE_MACHINE = "(ti-soc)"
> +
> +PROTOCOL = "git"
> +BRANCH = "jailhouse"
> +SRCREV = "f3ad79881bebb6c6068966ee3d265d8034c20492"
> +SRC_URI = 
> "git://github.com/henning-schild-work/ivshmem-guest-code.git;protocol=${PROTOCOL};branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +EXTRA_OEMAKE += 'KDIR="${STAGING_KERNEL_DIR}"'
> +
> +do_compile_prepend() {
> +cd ${S}/kernel_module/uio
> +}
> +
> +do_install() {
> +install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> +install -m 644 ${S}/kernel_module/uio/uio_ivshmem.ko 
> ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> +}
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master PATCH v2] recipes-bsp: ivshmem-uio: Add new recipe for ivshmem-uio driver

2019-10-01 Thread Denys Dmytriyenko
On Mon, Sep 30, 2019 at 11:41:43PM -0700, Khem Raj wrote:
> On Fri, Sep 27, 2019 at 2:17 AM Nikhil Devshatwar  wrote:
> >
> > This is external kernel module which enables userspace io over the
> > Jailhouse ivhsmem (inter VM shared memory)
> > This driver is useful to test the inter VM communication.
> >
> > Signed-off-by: Nikhil Devshatwar 
> > ---
> > Changes from v1:
> > * Split the ivshmem recipe separately
> > * Add summary and remove PACKAGE_ARCH define
> >
> >  recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb | 27 
> > +++
> >  1 file changed, 27 insertions(+)
> >  create mode 100644 recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> >
> > diff --git a/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb 
> > b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> > new file mode 100644
> > index 000..33fb946
> > --- /dev/null
> > +++ b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> > @@ -0,0 +1,27 @@
> > +DESCRIPTION =  "Kernel driver for IVSHMEM based UIO driver"
> > +SUMMARY = "Kernel module which registers a UIO (userspace io) device for 
> > inter VM shared memory"
> > +HOMEPAGE = "https://github.com/henning-schild-work/ivshmem-guest-code";
> > +LICENSE = "GPLv2"
> > +LIC_FILES_CHKSUM = "file://COPYING;md5=0546a27aad86c83b75ad4ee6133e9d5e"
> > +
> > +inherit module
> > +
> > +RDEPENDS_${PN} = "jailhouse"
> > +
> 
> jailhouse is marked as ti-soc specific, so please mark this recipe
> ti-soc specific as well. It will help meta-ti to live in a multi-BSP
> distros
> 
> http://jenkins.nas-admin.org/view/OE/job/oe_world_qemux86-64/1164/consoleFull
> 
> if you could test meta-ti patches with one non-ti machine like qemux86
> or some such it will help catch this kind of errors

That would only fail when building "world", but thanks for the report.


> > +PROTOCOL = "git"
> > +BRANCH = "jailhouse"
> > +SRCREV = "f3ad79881bebb6c6068966ee3d265d8034c20492"
> > +SRC_URI = 
> > "git://github.com/henning-schild-work/ivshmem-guest-code.git;protocol=${PROTOCOL};branch=${BRANCH}"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +EXTRA_OEMAKE += 'KDIR="${STAGING_KERNEL_DIR}"'
> > +
> > +do_compile_prepend() {
> > +cd ${S}/kernel_module/uio
> > +}
> > +
> > +do_install() {
> > +install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > +install -m 644 ${S}/kernel_module/uio/uio_ivshmem.ko 
> > ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > +}
> > --
> > 1.9.1
> >
> > --
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH 3/3] beaglebone-getting-started: Mention CC-BY-SA-3.0 and correct GPL version

2019-09-30 Thread Denys Dmytriyenko
On Mon, Sep 30, 2019 at 05:07:01PM -0700, Khem Raj wrote:
> On Mon, Sep 30, 2019 at 5:00 PM Denys Dmytriyenko  wrote:
> >
> > On Mon, Sep 30, 2019 at 04:43:56PM -0400, Denys Dmytriyenko wrote:
> > > On Mon, Sep 30, 2019 at 01:40:23PM -0700, Khem Raj wrote:
> > > >
> > > >
> > > > On 9/30/19 11:32 AM, Denys Dmytriyenko wrote:
> > > > > On Sun, Sep 29, 2019 at 08:43:35AM -0700, Khem Raj wrote:
> > > > >> This is as per
> > > > >> https://github.com/jadonk/beaglebone-getting-started/blob/master/LICENSE.txt
> > > > >
> > > > > You are looking at the latest LICENSE file, while the recipe hasn't 
> > > > > updated
> > > > > its SRCREV since early 2012, back when beagleboard.org was still 
> > > > > active in OE.
> > > > > Specifically, GPLv3+ was added in 2013:
> > > > > https://github.com/jadonk/beaglebone-getting-started/commits/master/LICENSE.txt
> > > > >
> > > > > We don't use this package, but I kept it in case someone still needs 
> > > > > it. I did
> > > > > put a README with a note in that directory:
> > > > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/README
> > > > >
> > > > > Probably, this can be updated to the latest, as part of fixing the 
> > > > > LICENSE? :)
> > > > >
> > > >
> > > > The README should be specific about which recipes are not maintained, it
> > > > has a general statement which gives a scare, if the recipe is not
> > > > maintained then this should be removed or atleast blacklisted if you
> > > > still want to keep it around.
> > > >
> > > > I was trying to help clearing up license warnings, other than that I
> >
> > BTW, the only warning I see for this recipe, is that "others" license is
> > unknown. Your patch was not addressing it - should I just remove "others"
> > from the list, as this was back from the days when the list wasn't checked
> > so strictly?
> >
> 
> Yes, go ahead.

https://lists.yoctoproject.org/pipermail/meta-ti/2019-September/012292.html


> > > > dont have any interest in this recipe.
> > > >
> > > > I can send a patch to blacklist it if thats fine with you.
> > >
> > > Fair enough, let me take a look at it myself.
> > >
> > >
> > > > >> Signed-off-by: Khem Raj 
> > > > >> ---
> > > > >>  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
> > > > >>  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >>
> > > > >> diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> > > > >> b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > > >> index 6c61a4e9..c86e3518 100644
> > > > >> --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > > >> +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > > > >> @@ -4,7 +4,7 @@ PR = "r21"
> > > > >>
> > > > >>  inherit allarch
> > > > >>
> > > > >> -LICENSE = "GPLv2+ & MIT & PD & others"
> > > > >> +LICENSE = "CC-BY-SA-3.0 & GPLv3+ & MIT & PD & others"
> > > > >>  LIC_FILES_CHKSUM = 
> > > > >> "file://LICENSE.txt;md5=603591dea023c3c75b48e07cb47ce639"
> > > > >>
> > > > >>  SRCREV = "6c548a307c948b28a99d48fd17d9790b56182196"
> > > > >> --
> > > > >> 2.23.0
> > > > >>
> > > > >> --
> > > > >> ___
> > > > >> meta-ti mailing list
> > > > >> meta-ti@yoctoproject.org
> > > > >> https://lists.yoctoproject.org/listinfo/meta-ti
> > > --
> > > ___
> > > meta-ti mailing list
> > > meta-ti@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [PATCH] beaglebone-getting-started: update to the latest and fix licenses

2019-09-30 Thread Denys Dmytriyenko
From: Khem Raj 

This is as per
https://github.com/jadonk/beaglebone-getting-started/blob/master/LICENSE.txt
* Mention CC-BY-SA-3.0
* Update to GPLv3+ since RNDIS addition
* Remove ambiguous "others" license

Package now contains sample bash scripts for the host
* skip file-rdeps QA check

Signed-off-by: Khem Raj 
Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/beagleboard/beaglebone-getting-started.bb | 11 ++-
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
b/recipes-ti/beagleboard/beaglebone-getting-started.bb
index 6c61a4e..adde30b 100644
--- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
+++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
@@ -1,13 +1,13 @@
-DESCRIPTION = "BeagleBone Getting Started Guide"
+SUMMARY = "BeagleBone Getting Started Guide"
 
-PR = "r21"
+PR = "r22"
 
 inherit allarch
 
-LICENSE = "GPLv2+ & MIT & PD & others"
-LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=603591dea023c3c75b48e07cb47ce639"
+LICENSE = "CC-BY-SA-3.0 & GPLv3+ & MIT & PD"
+LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=f6f02761e31334c48f7021fb94c89aaa"
 
-SRCREV = "6c548a307c948b28a99d48fd17d9790b56182196"
+SRCREV = "05bedba192646152b7bc80b0accaea75aef864e5"
 SRC_URI = "git://github.com/jadonk/beaglebone-getting-started.git"
 
 S = "${WORKDIR}/git"
@@ -18,3 +18,4 @@ do_install() {
 }
 
 FILES_${PN} += "${datadir}/${PN}"
+INSANE_SKIP_${PN} = "file-rdeps"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH 3/3] beaglebone-getting-started: Mention CC-BY-SA-3.0 and correct GPL version

2019-09-30 Thread Denys Dmytriyenko
On Mon, Sep 30, 2019 at 04:43:56PM -0400, Denys Dmytriyenko wrote:
> On Mon, Sep 30, 2019 at 01:40:23PM -0700, Khem Raj wrote:
> > 
> > 
> > On 9/30/19 11:32 AM, Denys Dmytriyenko wrote:
> > > On Sun, Sep 29, 2019 at 08:43:35AM -0700, Khem Raj wrote:
> > >> This is as per
> > >> https://github.com/jadonk/beaglebone-getting-started/blob/master/LICENSE.txt
> > > 
> > > You are looking at the latest LICENSE file, while the recipe hasn't 
> > > updated 
> > > its SRCREV since early 2012, back when beagleboard.org was still active 
> > > in OE. 
> > > Specifically, GPLv3+ was added in 2013:
> > > https://github.com/jadonk/beaglebone-getting-started/commits/master/LICENSE.txt
> > > 
> > > We don't use this package, but I kept it in case someone still needs it. 
> > > I did 
> > > put a README with a note in that directory:
> > > http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/README
> > > 
> > > Probably, this can be updated to the latest, as part of fixing the 
> > > LICENSE? :)
> > > 
> > 
> > The README should be specific about which recipes are not maintained, it
> > has a general statement which gives a scare, if the recipe is not
> > maintained then this should be removed or atleast blacklisted if you
> > still want to keep it around.
> > 
> > I was trying to help clearing up license warnings, other than that I

BTW, the only warning I see for this recipe, is that "others" license is 
unknown. Your patch was not addressing it - should I just remove "others" 
from the list, as this was back from the days when the list wasn't checked 
so strictly?


> > dont have any interest in this recipe.
> > 
> > I can send a patch to blacklist it if thats fine with you.
> 
> Fair enough, let me take a look at it myself.
> 
> 
> > >> Signed-off-by: Khem Raj 
> > >> ---
> > >>  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
> > >>  1 file changed, 1 insertion(+), 1 deletion(-)
> > >>
> > >> diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> > >> b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > >> index 6c61a4e9..c86e3518 100644
> > >> --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > >> +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > >> @@ -4,7 +4,7 @@ PR = "r21"
> > >>  
> > >>  inherit allarch
> > >>  
> > >> -LICENSE = "GPLv2+ & MIT & PD & others"
> > >> +LICENSE = "CC-BY-SA-3.0 & GPLv3+ & MIT & PD & others"
> > >>  LIC_FILES_CHKSUM = 
> > >> "file://LICENSE.txt;md5=603591dea023c3c75b48e07cb47ce639"
> > >>  
> > >>  SRCREV = "6c548a307c948b28a99d48fd17d9790b56182196"
> > >> -- 
> > >> 2.23.0
> > >>
> > >> -- 
> > >> ___
> > >> meta-ti mailing list
> > >> meta-ti@yoctoproject.org
> > >> https://lists.yoctoproject.org/listinfo/meta-ti
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH 3/3] beaglebone-getting-started: Mention CC-BY-SA-3.0 and correct GPL version

2019-09-30 Thread Denys Dmytriyenko
On Mon, Sep 30, 2019 at 01:40:23PM -0700, Khem Raj wrote:
> 
> 
> On 9/30/19 11:32 AM, Denys Dmytriyenko wrote:
> > On Sun, Sep 29, 2019 at 08:43:35AM -0700, Khem Raj wrote:
> >> This is as per
> >> https://github.com/jadonk/beaglebone-getting-started/blob/master/LICENSE.txt
> > 
> > You are looking at the latest LICENSE file, while the recipe hasn't updated 
> > its SRCREV since early 2012, back when beagleboard.org was still active in 
> > OE. 
> > Specifically, GPLv3+ was added in 2013:
> > https://github.com/jadonk/beaglebone-getting-started/commits/master/LICENSE.txt
> > 
> > We don't use this package, but I kept it in case someone still needs it. I 
> > did 
> > put a README with a note in that directory:
> > http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/README
> > 
> > Probably, this can be updated to the latest, as part of fixing the LICENSE? 
> > :)
> > 
> 
> The README should be specific about which recipes are not maintained, it
> has a general statement which gives a scare, if the recipe is not
> maintained then this should be removed or atleast blacklisted if you
> still want to keep it around.
> 
> I was trying to help clearing up license warnings, other than that I
> dont have any interest in this recipe.
> 
> I can send a patch to blacklist it if thats fine with you.

Fair enough, let me take a look at it myself.


> >> Signed-off-by: Khem Raj 
> >> ---
> >>  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> >> b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> >> index 6c61a4e9..c86e3518 100644
> >> --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> >> +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> >> @@ -4,7 +4,7 @@ PR = "r21"
> >>  
> >>  inherit allarch
> >>  
> >> -LICENSE = "GPLv2+ & MIT & PD & others"
> >> +LICENSE = "CC-BY-SA-3.0 & GPLv3+ & MIT & PD & others"
> >>  LIC_FILES_CHKSUM = 
> >> "file://LICENSE.txt;md5=603591dea023c3c75b48e07cb47ce639"
> >>  
> >>  SRCREV = "6c548a307c948b28a99d48fd17d9790b56182196"
> >> -- 
> >> 2.23.0
> >>
> >> -- 
> >> ___
> >> meta-ti mailing list
> >> meta-ti@yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH 3/3] beaglebone-getting-started: Mention CC-BY-SA-3.0 and correct GPL version

2019-09-30 Thread Denys Dmytriyenko
On Sun, Sep 29, 2019 at 08:43:35AM -0700, Khem Raj wrote:
> This is as per
> https://github.com/jadonk/beaglebone-getting-started/blob/master/LICENSE.txt

You are looking at the latest LICENSE file, while the recipe hasn't updated 
its SRCREV since early 2012, back when beagleboard.org was still active in OE. 
Specifically, GPLv3+ was added in 2013:
https://github.com/jadonk/beaglebone-getting-started/commits/master/LICENSE.txt

We don't use this package, but I kept it in case someone still needs it. I did 
put a README with a note in that directory:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-ti/README

Probably, this can be updated to the latest, as part of fixing the LICENSE? :)

Denys


> Signed-off-by: Khem Raj 
> ---
>  recipes-ti/beagleboard/beaglebone-getting-started.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-ti/beagleboard/beaglebone-getting-started.bb 
> b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> index 6c61a4e9..c86e3518 100644
> --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> @@ -4,7 +4,7 @@ PR = "r21"
>  
>  inherit allarch
>  
> -LICENSE = "GPLv2+ & MIT & PD & others"
> +LICENSE = "CC-BY-SA-3.0 & GPLv3+ & MIT & PD & others"
>  LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=603591dea023c3c75b48e07cb47ce639"
>  
>  SRCREV = "6c548a307c948b28a99d48fd17d9790b56182196"
> -- 
> 2.23.0
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH 1/3] u-boot-ti: Drop using COREBASE

2019-09-29 Thread Denys Dmytriyenko
On Sun, Sep 29, 2019 at 08:43:33AM -0700, Khem Raj wrote:
> COREBASE is hardcoding the path and moreover its obsolete the better way
> is to use relative path which is automatically searched in BBPATH by
> bitbake

This was actually done on purpose - there are many versions of u-boot.bb and 
u-boot.inc in different OE layers:
https://layers.openembedded.org/layerindex/branch/master/recipes/?q=u-boot

To avoid any conflicts, I specifically include the one from OE-Core.

COREBASE itself is not obsolete, just ${COREBASE}/LICENSE is:
https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-COREBASE
https://git.openembedded.org/openembedded-core/tree/meta/conf/layer.conf#n20
https://git.openembedded.org/openembedded-core/tree/meta/classes/insane.bbclass#n468

-- 
Denys


> Signed-off-by: Khem Raj 
> ---
>  recipes-bsp/u-boot/u-boot-ti.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-bsp/u-boot/u-boot-ti.inc 
> b/recipes-bsp/u-boot/u-boot-ti.inc
> index f1187e64..f7434712 100644
> --- a/recipes-bsp/u-boot/u-boot-ti.inc
> +++ b/recipes-bsp/u-boot/u-boot-ti.inc
> @@ -13,7 +13,7 @@ UBOOT_LOCALVERSION = 
> "-g${@get_git_revision('${S}').__str__()[:10]}"
>  UBOOT_SUFFIX ?= "img"
>  SPL_BINARY ?= "MLO"
>  
> -require ${COREBASE}/meta/recipes-bsp/u-boot/u-boot.inc
> +require recipes-bsp/u-boot/u-boot.inc
>  
>  FILESEXTRAPATHS_prepend := "${THISDIR}/u-boot:"
>  
> -- 
> 2.23.0
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master PATCH v2] recipes-bsp: ivshmem-uio: Add new recipe for ivshmem-uio driver

2019-09-27 Thread Denys Dmytriyenko
On Fri, Sep 27, 2019 at 02:46:44PM +0530, Nikhil Devshatwar wrote:
> This is external kernel module which enables userspace io over the
> Jailhouse ivhsmem (inter VM shared memory)
> This driver is useful to test the inter VM communication.
> 
> Signed-off-by: Nikhil Devshatwar 
> ---
> Changes from v1:
> * Split the ivshmem recipe separately
> * Add summary and remove PACKAGE_ARCH define
> 
>  recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb | 27 
> +++
>  1 file changed, 27 insertions(+)
>  create mode 100644 recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> 
> diff --git a/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb 
> b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> new file mode 100644
> index 000..33fb946
> --- /dev/null
> +++ b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
> @@ -0,0 +1,27 @@
> +DESCRIPTION =  "Kernel driver for IVSHMEM based UIO driver"
> +SUMMARY = "Kernel module which registers a UIO (userspace io) device for 
> inter VM shared memory"

The other way around - SUMMARY is short and DESCRIPTION is long.


> +HOMEPAGE = "https://github.com/henning-schild-work/ivshmem-guest-code";
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=0546a27aad86c83b75ad4ee6133e9d5e"
> +
> +inherit module
> +
> +RDEPENDS_${PN} = "jailhouse"
> +
> +PROTOCOL = "git"
> +BRANCH = "jailhouse"
> +SRCREV = "f3ad79881bebb6c6068966ee3d265d8034c20492"
> +SRC_URI = 
> "git://github.com/henning-schild-work/ivshmem-guest-code.git;protocol=${PROTOCOL};branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +EXTRA_OEMAKE += 'KDIR="${STAGING_KERNEL_DIR}"'
> +
> +do_compile_prepend() {
> +cd ${S}/kernel_module/uio
> +}
> +
> +do_install() {
> +install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> +install -m 644 ${S}/kernel_module/uio/uio_ivshmem.ko 
> ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> +}
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH] rwmem: Update to 2.0-rc2+

2019-09-26 Thread Denys Dmytriyenko
On Thu, Sep 26, 2019 at 11:28:29AM -0700, Khem Raj wrote:
> On 9/26/19 11:25 AM, Denys Dmytriyenko wrote:
> >Does this need:
> >
> >DEPENDS += "python3"
> >
> >Otherwise do_configure fails:
> >
> >-- Checking for module 'python3'
> >--   No package 'python3' found
> >
> 
> it was looking for that on build system so inherit python3native should have
> fixed it. Sent a v2 just now

inherit python3native was already in v1 and it was giving me that error 
anyway.


> >On Thu, Sep 26, 2019 at 09:01:50AM -0700, Khem Raj wrote:
> >>- New versions uses CMake and extra modules
> >>- Correct detection of nm/ranlib/ar for LTO
> >>- Fix build with clang/libc++
> >>
> >>Signed-off-by: Khem Raj 
> >>---
> >>  ...Make-provided-vars-for-ar-and-ranlib.patch | 34 +++
> >>  h-Include-cerrno-for-errno-definiti.patch | 24 +
> >>  recipes-bsp/rwmem/rwmem_1.1.bb| 13 ---
> >>  recipes-bsp/rwmem/rwmem_1.2.bb| 27 +++
> >>  4 files changed, 85 insertions(+), 13 deletions(-)
> >>  create mode 100644 
> >> recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> >>  create mode 100644 
> >> recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> >>  delete mode 100644 recipes-bsp/rwmem/rwmem_1.1.bb
> >>  create mode 100644 recipes-bsp/rwmem/rwmem_1.2.bb
> >>
> >>diff --git 
> >>a/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> >> 
> >>b/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> >>new file mode 100644
> >>index ..79968f32
> >>--- /dev/null
> >>+++ 
> >>b/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> >>@@ -0,0 +1,34 @@
> >>+From ee3bbdaae568118b4aad453c8fbb1ec648e8fbf2 Mon Sep 17 00:00:00 2001
> >>+From: Khem Raj 
> >>+Date: Sat, 8 Dec 2018 22:48:23 -0800
> >>+Subject: [PATCH] Use CMake provided vars for ar and ranlib
> >>+
> >>+hardcoding them means we may not be able to cross compile the package
> >>+reliably as build host may or may not have gcc-ar and gcc-ranlib
> >>+installed, using the cross tools is the correct thing to do here
> >>+
> >>+Upstream-Status: Submitted [https://github.com/tomba/rwmem/pull/5]
> >>+
> >>+Signed-off-by: Khem Raj 
> >>+---
> >>+ CMakeLists.txt | 4 ++--
> >>+ 1 file changed, 2 insertions(+), 2 deletions(-)
> >>+
> >>+diff --git a/CMakeLists.txt b/CMakeLists.txt
> >>+index 5e7f327..e36fca0 100644
> >>+--- a/CMakeLists.txt
> >> b/CMakeLists.txt
> >>+@@ -50,8 +50,8 @@ if (NOT ${U_CMAKE_BUILD_TYPE} MATCHES DEBUG)
> >>+   if (HAS_LTO_FLAG)
> >>+   set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -flto")
> >>+   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -flto")
> >>+-  set(CMAKE_AR gcc-ar)
> >>+-  set(CMAKE_RANLIB gcc-ranlib)
> >>++  set(CMAKE_AR ${CMAKE_CXX_COMPILER_AR})
> >>++  set(CMAKE_RANLIB ${CMAKE_CXX_COMPILER_RANLIB})
> >>+   endif()
> >>+ endif()
> >>+
> >>+--
> >>+2.19.2
> >>+
> >>diff --git 
> >>a/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> >> 
> >>b/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> >>new file mode 100644
> >>index ..9f33fa5e
> >>--- /dev/null
> >>+++ 
> >>b/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> >>@@ -0,0 +1,24 @@
> >>+From 9f1d52590336caeab8038cdd015294df2e5d8c1f Mon Sep 17 00:00:00 2001
> >>+From: Khem Raj 
> >>+Date: Fri, 1 Feb 2019 23:47:04 -0800
> >>+Subject: [PATCH] librwmem/helpers.h: Include  for errno definitions
> >>+
> >>+this is found with libc++
> >>+
> >>+Upstream-Status: Submitted [https://github.com/tomba/rwmem/pull/5]
> >>+Signed-off-by: Khem Raj 
> >>+---
> >>+ librwmem/helpers.h | 1 +
> >>+ 1 file changed, 1 insertion(+)
> >>+
> >>+diff --git a/librwmem/helpers.h b/librwmem/helpers.h
> >>+index ccc6c9e..686943e 100644
> >>+--- a/librwmem/helpers.h
> >> b/librwmem/helpers.h
> >>+@@ -1,5 +1,6 @@
> >>+ #pragma once
&g

Re: [meta-ti] [PATCH] rwmem: Update to 2.0-rc2+

2019-09-26 Thread Denys Dmytriyenko
Does this need:

DEPENDS += "python3"

Otherwise do_configure fails:

-- Checking for module 'python3'
--   No package 'python3' found


On Thu, Sep 26, 2019 at 09:01:50AM -0700, Khem Raj wrote:
> - New versions uses CMake and extra modules
> - Correct detection of nm/ranlib/ar for LTO
> - Fix build with clang/libc++
> 
> Signed-off-by: Khem Raj 
> ---
>  ...Make-provided-vars-for-ar-and-ranlib.patch | 34 +++
>  h-Include-cerrno-for-errno-definiti.patch | 24 +
>  recipes-bsp/rwmem/rwmem_1.1.bb| 13 ---
>  recipes-bsp/rwmem/rwmem_1.2.bb| 27 +++
>  4 files changed, 85 insertions(+), 13 deletions(-)
>  create mode 100644 
> recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
>  create mode 100644 
> recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
>  delete mode 100644 recipes-bsp/rwmem/rwmem_1.1.bb
>  create mode 100644 recipes-bsp/rwmem/rwmem_1.2.bb
> 
> diff --git 
> a/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
>  
> b/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> new file mode 100644
> index ..79968f32
> --- /dev/null
> +++ 
> b/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> @@ -0,0 +1,34 @@
> +From ee3bbdaae568118b4aad453c8fbb1ec648e8fbf2 Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Sat, 8 Dec 2018 22:48:23 -0800
> +Subject: [PATCH] Use CMake provided vars for ar and ranlib
> +
> +hardcoding them means we may not be able to cross compile the package
> +reliably as build host may or may not have gcc-ar and gcc-ranlib
> +installed, using the cross tools is the correct thing to do here
> +
> +Upstream-Status: Submitted [https://github.com/tomba/rwmem/pull/5]
> +
> +Signed-off-by: Khem Raj 
> +---
> + CMakeLists.txt | 4 ++--
> + 1 file changed, 2 insertions(+), 2 deletions(-)
> +
> +diff --git a/CMakeLists.txt b/CMakeLists.txt
> +index 5e7f327..e36fca0 100644
> +--- a/CMakeLists.txt
>  b/CMakeLists.txt
> +@@ -50,8 +50,8 @@ if (NOT ${U_CMAKE_BUILD_TYPE} MATCHES DEBUG)
> + if (HAS_LTO_FLAG)
> + set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -flto")
> + set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -flto")
> +-set(CMAKE_AR gcc-ar)
> +-set(CMAKE_RANLIB gcc-ranlib)
> ++set(CMAKE_AR ${CMAKE_CXX_COMPILER_AR})
> ++set(CMAKE_RANLIB ${CMAKE_CXX_COMPILER_RANLIB})
> + endif()
> + endif()
> + 
> +-- 
> +2.19.2
> +
> diff --git 
> a/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
>  
> b/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> new file mode 100644
> index ..9f33fa5e
> --- /dev/null
> +++ 
> b/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> @@ -0,0 +1,24 @@
> +From 9f1d52590336caeab8038cdd015294df2e5d8c1f Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Fri, 1 Feb 2019 23:47:04 -0800
> +Subject: [PATCH] librwmem/helpers.h: Include  for errno definitions
> +
> +this is found with libc++
> +
> +Upstream-Status: Submitted [https://github.com/tomba/rwmem/pull/5]
> +Signed-off-by: Khem Raj 
> +---
> + librwmem/helpers.h | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/librwmem/helpers.h b/librwmem/helpers.h
> +index ccc6c9e..686943e 100644
> +--- a/librwmem/helpers.h
>  b/librwmem/helpers.h
> +@@ -1,5 +1,6 @@
> + #pragma once
> + 
> ++#include 
> + #include 
> + #include 
> + #include 
> diff --git a/recipes-bsp/rwmem/rwmem_1.1.bb b/recipes-bsp/rwmem/rwmem_1.1.bb
> deleted file mode 100644
> index 2848e1cd..
> --- a/recipes-bsp/rwmem/rwmem_1.1.bb
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -SUMMARY = "A small tool to read/write memory"
> -LICENSE = "GPLv2+"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> -
> -SRCREV = "54904b8873b265d8f1faf82617c2f04814c102c6"
> -SRC_URI = "git://github.com/tomba/rwmem.git"
> -
> -S = "${WORKDIR}/git"
> -
> -do_install() {
> - install -d ${D}${bindir}
> - install -m 0755 rwmem ${D}${bindir}
> -}
> diff --git a/recipes-bsp/rwmem/rwmem_1.2.bb b/recipes-bsp/rwmem/rwmem_1.2.bb
> new file mode 100644
> index ..c4d2bc49
> --- /dev/null
> +++ b/recipes-bsp/rwmem/rwmem_1.2.bb
> @@ -0,0 +1,27 @@
> +SUMMARY = "A small tool to read/write memory"
> +LICENSE = "GPLv2+"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> +
> +PV .= "+git${SRCPV}"
> +
> +SRCREV_rwmem = "7e5ca9802c1b8ff1f6407c19dfd0b9415501bb11"
> +SRCREV_inih = "4b10c654051a86556dfdb634c891b6c3224c4109"
> +SRCREV_pybind11 = "9a19306fbf30642ca331d0ec88e7da54a96860f9"
> +
> +SRCREV_FORMAT = "rwmem_inih_pybind11"
> +
> +SRC_URI = "git://github.com/tomba/rwmem.git;protocol=https;name=rwmem \
> +   
> git://github.com/benhoyt/inih.git;protocol=https;name=inih;nobranch=1;destsuffix=git/ext/ini

Re: [meta-ti] [thud/master][PATCH v2] ipc-lld: Adding recipe for IPC low-level driver and examples

2019-09-26 Thread Denys Dmytriyenko
Looks good, thanks for addressing the comments.

On Wed, Sep 25, 2019 at 10:15:07AM -0500, Santosh Jha wrote:
> IPC-LLD provides the low-level RPMSG based
> communication interface between various cores
> 
> Signed-off-by: Santosh Jha 
> 
> ---
> 
> Changed from previous version of patch
>  - Moved from recipe-ti to recipe-bsp directory
>  - Addressed review comments
> 
> ---
> ---
>  .../ipc-lld/ipc-lld-examples-rtos_git.bb  | 47 +++
>  recipes-bsp/ipc-lld/ipc-lld-rtos_git.bb   | 45 ++
>  recipes-bsp/ipc-lld/ipc-lld.inc   | 36 ++
>  3 files changed, 128 insertions(+)
>  create mode 100644 recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
>  create mode 100644 recipes-bsp/ipc-lld/ipc-lld-rtos_git.bb
>  create mode 100644 recipes-bsp/ipc-lld/ipc-lld.inc
> 
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> new file mode 100644
> index ..44f76675
> --- /dev/null
> +++ b/recipes-bsp/ipc-lld/ipc-lld-examples-rtos_git.bb
> @@ -0,0 +1,47 @@
> +SUMMARY = "echo_test for IPC-LLD"
> +
> +require ipc-lld.inc
> +
> +DEPENDS += " ipc-lld-rtos common-csl-ip-rtos sciclient-rtos board-rtos"
> +
> +REMOTE_FW_DIR = "${S}/examples/echo_test/yocto_bin"
> +REMOTE_FW_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_test/bin"
> +
> +DST_BIN_PATH = "${base_libdir}/firmware/pdk-ipc/"
> +
> +do_configure[noexec] = "1"
> +
> +do_compile() {
> +cd ${S}
> +
> +for board in ${TI_PDK_LIMIT_BOARDS}
> +do
> +for core in ${TI_PDK_LIMIT_CORES}
> +do
> +oe_runmake examples BOARD="$board" CORE="$core" 
> DEST_ROOT=${REMOTE_FW_DIR}
> +done
> +done
> +}
> +
> +do_install() {
> +install -d ${D}${DST_BIN_PATH}
> +
> +for board in ${TI_PDK_LIMIT_BOARDS}
> +do
> +for core in ${TI_PDK_LIMIT_CORES}
> +do
> +install -m 0644 
> ${REMOTE_FW_BIN_DIR}/$board/ipc_echo_test_${core}_release.x* 
> ${D}${DST_BIN_PATH}
> +
> +#removing map files copied in previous line
> +rm ${D}${DST_BIN_PATH}/*.map
> +done
> +done
> +}
> +
> +# make sure that lib/firmware, and all its contents are part of the package
> +FILES_${PN} += "${base_libdir}/firmware"
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +
> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> +
> +INSANE_SKIP_${PN}-dbg = "arch"
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-rtos_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-rtos_git.bb
> new file mode 100644
> index ..e005ea70
> --- /dev/null
> +++ b/recipes-bsp/ipc-lld/ipc-lld-rtos_git.bb
> @@ -0,0 +1,45 @@
> +SUMMARY = "TI RTOS low level driver for IPC"
> +
> +require ipc-lld.inc
> +
> +DEPENDS += " osal-rtos common-csl-ip-rtos sciclient-rtos"
> +
> +do_configure() {
> +# remove any previous package
> +rm -rf ${IPCLLD_PACKAGE_BASE}
> +cd ${S}
> +
> +mkdir -p ${IPCLLD_ROOTPATH}
> +
> +for board in ${TI_PDK_LIMIT_BOARDS}
> +do
> +# make the release package before building it
> +oe_runmake package BOARD=$board DEST_ROOT=${IPCLLD_PACKAGE_BASE} 
> PDK_IPC_COMP_PATH=${S}
> +done
> +
> +}
> +
> +do_compile() {
> +cd ${IPCLLD_ROOTPATH}
> +
> +oe_runmake lib LIMIT_BOARDS="${TI_PDK_LIMIT_BOARDS}" 
> PDK_IPC_COMP_PATH=${IPCLLD_ROOTPATH}
> +}
> +
> +do_install() {
> +cd ${IPCLLD_ROOTPATH}
> +
> +#remove prebuilt binaries
> +rm -rf examples/echo_test/binaries
> +
> +#archive
> +tar -cf ipc-lld.tar --exclude='*.tar' ./*
> +
> +install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/ipc
> +find -name "*.tar" -exec tar xf {} --no-same-owner -C 
> ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/ipc \;
> +}
> +
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +
> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> +
> +INSANE_SKIP_${PN}-dbg = "arch"
> diff --git a/recipes-bsp/ipc-lld/ipc-lld.inc b/recipes-bsp/ipc-lld/ipc-lld.inc
> new file mode 100644
> index ..3fed3726
> --- /dev/null
> +++ b/recipes-bsp/ipc-lld/ipc-lld.inc
> @@ -0,0 +1,36 @@
> +inherit ti-pdk
> +
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=7eae093f2b09fd39307f30028a068b91"
> +
> +COMPATIBLE_MACHINE = "k3"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +IPCLLD_GIT_URI = "git://git.ti.com/keystone-rtos/ipc-lld.git"
> +IPCLLD_GIT_PROTOCOL = "git"
> +IPCLLD_GIT_BRANCH = "master"
> +
> +# Below commit ID corresponds to "01.00.00.00"
> +IPCLLD_SRCREV = "c695ca99aa4b7242e808889cfeacf848f14112c7"
> +
> +BRANCH = "${IPCLLD_GIT_BRANCH}"
> +SRC_URI = 
> "${IPCLLD_GIT_URI};protocol=${IPCLLD_GIT_PROTOCOL};branch=${BRANCH}"
> +
> +SRCREV = "${IPCLLD_SRCREV}"
> +PV = "01.00.00.00"
> +PR = "r0"
> +
> +# Build with make instead of XDC
> +TI_PDK_XDCMAKE = "0"
> +
> +IPCLLD_PACKAGE_BASE   = "${S}/../ipclld_base"
> +IPCLLD_ROOTPATH = 
> "${IPCLLD_PACKAGE_BASE}/package/all/pdk_/packages/ti/drv/ipc"
> +
> +export PDK_INSTALL_PATH = "${PDK_INSTALL_DIR}/package

Re: [meta-ti] [thud/master PATCH v1] recipes-kernel: jailhouse: update SRCREV to ti2019.04-rc2 tag

2019-09-26 Thread Denys Dmytriyenko
On Thu, Sep 26, 2019 at 09:37:39PM +0530, Nikhil Devshatwar wrote:
> /work/nikhil/ybd/k3-yocto-26-Sep/sources/meta-ti/recipes-kernel/jailhouse/jailhouse_git.bb

What's this for?


> Signed-off-by: Nikhil Devshatwar 
> ---
>  recipes-kernel/jailhouse/jailhouse_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> b/recipes-kernel/jailhouse/jailhouse_git.bb
> index 32aecf8..409b325 100644
> --- a/recipes-kernel/jailhouse/jailhouse_git.bb
> +++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = " \
>  "
>  
>  PV = "0.10+git${SRCPV}"
> -SRCREV = "6dce20f902f73fe9ce53ba0c41262a4defa8d328"
> +SRCREV = "8858ba60ab078d8e3e5317fd644f09c560775a99"
>  BRANCH = "ti-jailhouse-0.10"
>  
>  SRC_URI = " \
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH] rwmem: Update to 2.0-rc2+

2019-09-26 Thread Denys Dmytriyenko
Thanks! It's been on my todo list lately...

There's pybind11 recipe in meta-openembedded/meta-python that I originally 
submitted back in 2016, but unfortunately meta-ti does not depend on that 
layer and probably shouldn't for now.


On Thu, Sep 26, 2019 at 09:01:50AM -0700, Khem Raj wrote:
> - New versions uses CMake and extra modules
> - Correct detection of nm/ranlib/ar for LTO
> - Fix build with clang/libc++
> 
> Signed-off-by: Khem Raj 
> ---
>  ...Make-provided-vars-for-ar-and-ranlib.patch | 34 +++
>  h-Include-cerrno-for-errno-definiti.patch | 24 +
>  recipes-bsp/rwmem/rwmem_1.1.bb| 13 ---
>  recipes-bsp/rwmem/rwmem_1.2.bb| 27 +++
>  4 files changed, 85 insertions(+), 13 deletions(-)
>  create mode 100644 
> recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
>  create mode 100644 
> recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
>  delete mode 100644 recipes-bsp/rwmem/rwmem_1.1.bb
>  create mode 100644 recipes-bsp/rwmem/rwmem_1.2.bb
> 
> diff --git 
> a/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
>  
> b/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> new file mode 100644
> index ..79968f32
> --- /dev/null
> +++ 
> b/recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> @@ -0,0 +1,34 @@
> +From ee3bbdaae568118b4aad453c8fbb1ec648e8fbf2 Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Sat, 8 Dec 2018 22:48:23 -0800
> +Subject: [PATCH] Use CMake provided vars for ar and ranlib
> +
> +hardcoding them means we may not be able to cross compile the package
> +reliably as build host may or may not have gcc-ar and gcc-ranlib
> +installed, using the cross tools is the correct thing to do here
> +
> +Upstream-Status: Submitted [https://github.com/tomba/rwmem/pull/5]
> +
> +Signed-off-by: Khem Raj 
> +---
> + CMakeLists.txt | 4 ++--
> + 1 file changed, 2 insertions(+), 2 deletions(-)
> +
> +diff --git a/CMakeLists.txt b/CMakeLists.txt
> +index 5e7f327..e36fca0 100644
> +--- a/CMakeLists.txt
>  b/CMakeLists.txt
> +@@ -50,8 +50,8 @@ if (NOT ${U_CMAKE_BUILD_TYPE} MATCHES DEBUG)
> + if (HAS_LTO_FLAG)
> + set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -flto")
> + set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -flto")
> +-set(CMAKE_AR gcc-ar)
> +-set(CMAKE_RANLIB gcc-ranlib)
> ++set(CMAKE_AR ${CMAKE_CXX_COMPILER_AR})
> ++set(CMAKE_RANLIB ${CMAKE_CXX_COMPILER_RANLIB})
> + endif()
> + endif()
> + 
> +-- 
> +2.19.2
> +
> diff --git 
> a/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
>  
> b/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> new file mode 100644
> index ..9f33fa5e
> --- /dev/null
> +++ 
> b/recipes-bsp/rwmem/rwmem/0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.patch
> @@ -0,0 +1,24 @@
> +From 9f1d52590336caeab8038cdd015294df2e5d8c1f Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Fri, 1 Feb 2019 23:47:04 -0800
> +Subject: [PATCH] librwmem/helpers.h: Include  for errno definitions
> +
> +this is found with libc++
> +
> +Upstream-Status: Submitted [https://github.com/tomba/rwmem/pull/5]
> +Signed-off-by: Khem Raj 
> +---
> + librwmem/helpers.h | 1 +
> + 1 file changed, 1 insertion(+)
> +
> +diff --git a/librwmem/helpers.h b/librwmem/helpers.h
> +index ccc6c9e..686943e 100644
> +--- a/librwmem/helpers.h
>  b/librwmem/helpers.h
> +@@ -1,5 +1,6 @@
> + #pragma once
> + 
> ++#include 
> + #include 
> + #include 
> + #include 
> diff --git a/recipes-bsp/rwmem/rwmem_1.1.bb b/recipes-bsp/rwmem/rwmem_1.1.bb
> deleted file mode 100644
> index 2848e1cd..
> --- a/recipes-bsp/rwmem/rwmem_1.1.bb
> +++ /dev/null
> @@ -1,13 +0,0 @@
> -SUMMARY = "A small tool to read/write memory"
> -LICENSE = "GPLv2+"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> -
> -SRCREV = "54904b8873b265d8f1faf82617c2f04814c102c6"
> -SRC_URI = "git://github.com/tomba/rwmem.git"
> -
> -S = "${WORKDIR}/git"
> -
> -do_install() {
> - install -d ${D}${bindir}
> - install -m 0755 rwmem ${D}${bindir}
> -}
> diff --git a/recipes-bsp/rwmem/rwmem_1.2.bb b/recipes-bsp/rwmem/rwmem_1.2.bb
> new file mode 100644
> index ..c4d2bc49
> --- /dev/null
> +++ b/recipes-bsp/rwmem/rwmem_1.2.bb
> @@ -0,0 +1,27 @@
> +SUMMARY = "A small tool to read/write memory"
> +LICENSE = "GPLv2+"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> +
> +PV .= "+git${SRCPV}"
> +
> +SRCREV_rwmem = "7e5ca9802c1b8ff1f6407c19dfd0b9415501bb11"
> +SRCREV_inih = "4b10c654051a86556dfdb634c891b6c3224c4109"
> +SRCREV_pybind11 = "9a19306fbf30642ca331d0ec88e7da54a96860f9"
> +
> +SRCREV_FORMAT = "rwmem_inih_pybind11"
> +
> +SRC_URI = "git://github.com/tomba/rwmem.git;protocol=https;name=rwmem \
> +   

Re: [meta-ti] [thud/master PATCH] pru-icss: add J721E Support

2019-09-24 Thread Denys Dmytriyenko
On Mon, Sep 23, 2019 at 04:24:49PM -0500, Suman Anna wrote:
> From: Nick Saulnier 
> 
> Updated git commit & version number for PRU Software Support Package.
> 
> Builds J721E Halt and RPMsg examples and packages them into lib/firmware/pru
> 
> Signed-off-by: Nick Saulnier 
> Signed-off-by: Suman Anna 
> ---
>  recipes-bsp/pru/pru-icss_git.bb | 68 +++--
>  1 file changed, 65 insertions(+), 3 deletions(-)
> 
> diff --git a/recipes-bsp/pru/pru-icss_git.bb b/recipes-bsp/pru/pru-icss_git.bb
> index 812caae9ade0..4fb059084e19 100644
> --- a/recipes-bsp/pru/pru-icss_git.bb
> +++ b/recipes-bsp/pru/pru-icss_git.bb
> @@ -8,9 +8,9 @@ inherit update-alternatives
>  
>  BRANCH = "master"
>  SRC_URI = 
> "git://git.ti.com/pru-software-support-package/pru-software-support-package.git;protocol=git;branch=${BRANCH}"
> -SRCREV = "99b1bfd8ca8780fd2306c2c939f3fd477b2e5218"
> +SRCREV = "1ff0393b3b9454fe9c58399c1b5d2db511e8049c"
>  
> -PV = "5.4.0"
> +PV = "5.5.0"
>  PR = "r1"
>  
>  require recipes-ti/includes/ti-paths.inc
> @@ -41,6 +41,7 @@ PLATFORM_ti43x = "am437x"
>  PLATFORM_omap-a15 = "am572x"
>  PLATFORM_k2g = "k2g"
>  PLATFORM_am65xx = "am65x"
> +PLATFORM_j7-evm = "j7-evm"

I believe it should be:

PLATFORM_j7-evm = "j721e"

Please confirm.


>  do_compile() {
>  for dir in ${SUBDIRS}
> @@ -131,7 +132,31 @@ do_install_append_am65xx() {
>  done
>  }
>  
> -FILES_${PN}-halt = "/lib/firmware/pru/PRU_Halt* /lib/firmware/pru/RTU_Halt*"
> +do_install_append_j7-evm() {
> +for i in 0 1
> +do
> +install -m 644 
> ${S}/examples/${PLATFORM}/PRU_Halt/gen/PRU${i}/PRU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +install -m 644 
> ${S}/examples/${PLATFORM}/RTU_Halt/gen/RTU${i}/RTU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +install -m 644 
> ${S}/examples/${PLATFORM}/TX_PRU_Halt/gen/TX_PRU${i}/TX_PRU_Halt_${i}.out \
> +   ${D}/lib/firmware/pru
> +done
> +for i in 0 1
> +do
> +for j in 0 1
> +do
> +install -m 0644 
> ${S}/examples/j721e/PRU_RPMsg_Echo_Interrupt${j}/gen/icssg${i}/PRU_RPMsg_Echo_Interrupt${i}_${j}.out
>  \
> +${D}/lib/firmware/pru
> +install -m 0644 
> ${S}/examples/j721e/RTU_RPMsg_Echo_Interrupt${j}/gen/icssg${i}/RTU_RPMsg_Echo_Interrupt${i}_${j}.out
>  \
> +${D}/lib/firmware/pru
> +
> +done
> +done
> +}
> +
> +
> +FILES_${PN}-halt = "/lib/firmware/pru/PRU_Halt* /lib/firmware/pru/RTU_Halt* 
> /lib/firmware/pru/TX_PRU_Halt*"
>  FILES_${PN}-rpmsg-echo = "/lib/firmware/pru/PRU_RPMsg_Echo_Interrupt* 
> /lib/firmware/pru/RTU_RPMsg_Echo_Interrupt*"
>  
>  # Set up names for the firmwares
> @@ -140,6 +165,7 @@ PRU_ICSS_ALTERNATIVES_ti43x= "am437x-pru0_0-fw 
> am437x-pru0_1-fw am437x-pru1_
>  PRU_ICSS_ALTERNATIVES_omap-a15 = "am57xx-pru1_0-fw am57xx-pru1_1-fw 
> am57xx-pru2_0-fw am57xx-pru2_1-fw"
>  PRU_ICSS_ALTERNATIVES_k2g  = "k2g-pru0_0-fw k2g-pru0_1-fw k2g-pru1_0-fw 
> k2g-pru1_1-fw"
>  PRU_ICSS_ALTERNATIVES_am65xx   = "am65x-pru0_0-fw am65x-pru0_1-fw 
> am65x-pru1_0-fw am65x-pru1_1-fw am65x-pru2_0-fw am65x-pru2_1-fw 
> am65x-rtu0_0-fw am65x-rtu0_1-fw am65x-rtu1_0-fw am65x-rtu1_1-fw 
> am65x-rtu2_0-fw am65x-rtu2_1-fw"
> +PRU_ICSS_ALTERNATIVES_j7-evm   = "j7-pru0_0-fw j7-pru0_1-fw j7-pru1_0-fw 
> j7-pru1_1-fw j7-rtu0_0-fw j7-rtu0_1-fw j7-rtu1_0-fw j7-rtu1_1-fw 
> j7-txpru0_0-fw j7-txpru0_1-fw j7-txpru1_0-fw j7-txpru1_1-fw"
>  
>  # Set up link names for the firmwares
>  ALTERNATIVE_LINK_NAME[am335x-pru0-fw] = "/lib/firmware/am335x-pru0-fw"
> @@ -173,6 +199,19 @@ ALTERNATIVE_LINK_NAME[am65x-rtu1_1-fw] = 
> "/lib/firmware/am65x-rtu1_1-fw"
>  ALTERNATIVE_LINK_NAME[am65x-rtu2_0-fw] = "/lib/firmware/am65x-rtu2_0-fw"
>  ALTERNATIVE_LINK_NAME[am65x-rtu2_1-fw] = "/lib/firmware/am65x-rtu2_1-fw"
>  
> +ALTERNATIVE_LINK_NAME[j7-pru0_0-fw] = "/lib/firmware/j7-pru0_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-pru0_1-fw] = "/lib/firmware/j7-pru0_1-fw"
> +ALTERNATIVE_LINK_NAME[j7-pru1_0-fw] = "/lib/firmware/j7-pru1_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-pru1_1-fw] = "/lib/firmware/j7-pru1_1-fw"
> +ALTERNATIVE_LINK_NAME[j7-rtu0_0-fw] = "/lib/firmware/j7-rtu0_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-rtu0_1-fw] = "/lib/firmware/j7-rtu0_1-fw"
> +ALTERNATIVE_LINK_NAME[j7-rtu1_0-fw] = "/lib/firmware/j7-rtu1_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-rtu1_1-fw] = "/lib/firmware/j7-rtu1_1-fw"
> +ALTERNATIVE_LINK_NAME[j7-txpru0_0-fw] = "/lib/firmware/j7-txpru0_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-txpru0_1-fw] = "/lib/firmware/j7-txpru0_1-fw"
> +ALTERNATIVE_LINK_NAME[j7-txpru1_0-fw] = "/lib/firmware/j7-txpru1_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-txpru1_1-fw] = "/lib/firmware/j7-txpru1_1-fw"
> +
>  # Create the pru-icss-halt firmware alternatives
>  ALTERNATIVE_pru-icss-halt = "${PRU_ICSS_ALTERNATIVES}"
>  
> @@ -207,6 +246,20 @@ ALTERNATIVE_TARGET_pru-icss-halt[am65x-rtu1_1-fw] = 
> "/lib/firmware/pru/RTU_Halt_
>  ALTERNATIVE_TARGET_pru-ics

Re: [meta-ti] [thud/master][PATCH] ipc-lld: Adding recipe for IPC low-level driver and examples

2019-09-23 Thread Denys Dmytriyenko
Why there are 2 identical patches and are there any differences?

Anyway, the patch seems mostly fine, please address few comments below inline. 
Thanks.


On Fri, Sep 20, 2019 at 12:21:11PM -0500, Santosh Jha wrote:
> IPC-LLD provides the low-level RPMSG based
> communication interface between various cores
> 
> Signed-off-by: Santosh Jha 
> ---
>  .../ipc-lld/ipc-lld-examples-rtos_git.bb  | 51 +++
>  recipes-ti/ipc-lld/ipc-lld-rtos_git.bb| 45 
>  recipes-ti/ipc-lld/ipc-lld.inc| 38 ++
>  3 files changed, 134 insertions(+)
>  create mode 100644 recipes-ti/ipc-lld/ipc-lld-examples-rtos_git.bb
>  create mode 100644 recipes-ti/ipc-lld/ipc-lld-rtos_git.bb
>  create mode 100644 recipes-ti/ipc-lld/ipc-lld.inc

Normally all LLDs reside in recipes.bsp. Moreorver, we already have 
recipes-bsp/ipc-lld/ with ipc-lld-fw.bb pre-built FW recipe.


> diff --git a/recipes-ti/ipc-lld/ipc-lld-examples-rtos_git.bb 
> b/recipes-ti/ipc-lld/ipc-lld-examples-rtos_git.bb
> new file mode 100644
> index ..cadde4d2
> --- /dev/null
> +++ b/recipes-ti/ipc-lld/ipc-lld-examples-rtos_git.bb
> @@ -0,0 +1,51 @@
> +SUMMARY = "echo_test for IPC-LLD"
> +
> +require ipc-lld.inc
> +
> +DEPENDS_append = " ipc-lld-rtos common-csl-ip-rtos sciclient-rtos board-rtos"

Not critical, but DEPENDS += here would be better


> +REMOTE_FW_DIR = "${S}/examples/echo_test/yocto_bin"
> +REMOTE_FW_BIN_DIR = "${REMOTE_FW_DIR}/ipc_echo_test/bin"
> +
> +# make sure that lib/firmware, and all its contents are part of the package
> +FILES_${PN} += "${base_libdir}/firmware"

There's another FILES_${PN} below


> +DST_BIN_PATH = "${base_libdir}/firmware/pdk-ipc/"
> +
> +do_configure() {
> +#Nothing to configure
> +:
> +}

This is preferred:
do_configure[noexec] = "1"


> +do_compile() {
> +cd ${S}
> +
> +for board in ${TI_PDK_LIMIT_BOARDS}
> +do
> +for core in ${TI_PDK_LIMIT_CORES}
> +do
> +oe_runmake examples BOARD="${board}" CORE="${core}" 
> DEST_ROOT=${REMOTE_FW_DIR}

Use $board and $core instead for shell vars instead of bitbake vars.


> +done
> +done
> +}
> +
> +do_install() {
> +install -d ${D}${DST_BIN_PATH}
> +
> +for board in ${TI_PDK_LIMIT_BOARDS}
> +do
> +for core in ${TI_PDK_LIMIT_CORES}
> +do
> +install -m 0644 
> ${REMOTE_FW_BIN_DIR}/${board}/ipc_echo_test_${core}_release.x* 
> ${D}${DST_BIN_PATH}

Same comment as above


> +#removing map files copied in previous line
> +rm ${D}${DST_BIN_PATH}/*.map
> +done
> +done
> +}
> +
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"

There's another FILES_${PN} above - please keep them in the same spot


> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> +
> +INSANE_SKIP_${PN}-dbg = "arch"
> diff --git a/recipes-ti/ipc-lld/ipc-lld-rtos_git.bb 
> b/recipes-ti/ipc-lld/ipc-lld-rtos_git.bb
> new file mode 100644
> index ..eff3cea1
> --- /dev/null
> +++ b/recipes-ti/ipc-lld/ipc-lld-rtos_git.bb
> @@ -0,0 +1,45 @@
> +SUMMARY = "TI RTOS low level driver for IPC"
> +
> +require ipc-lld.inc
> +
> +DEPENDS_append = " osal-rtos common-csl-ip-rtos sciclient-rtos"

Same as above


> +do_configure() {
> +# remove any previous package
> +rm -rf ${IPCLLD_PACKAGE_BASE}
> +cd ${S}
> +
> +mkdir -p ${IPCLLD_ROOTPATH}
> +
> +for board in ${TI_PDK_LIMIT_BOARDS}
> +do
> +# make the release package before building it
> +oe_runmake package BOARD=${board} DEST_ROOT=${IPCLLD_PACKAGE_BASE} 
> PDK_IPC_COMP_PATH=${S}

Use shell vars


> +done
> +
> +}
> +
> +do_compile() {
> +cd ${IPCLLD_ROOTPATH}
> +
> +oe_runmake lib LIMIT_BOARDS="${TI_PDK_LIMIT_BOARDS}" 
> PDK_IPC_COMP_PATH=${IPCLLD_ROOTPATH}
> +}
> +
> +do_install() {
> +cd ${IPCLLD_ROOTPATH}
> +
> +#remove prebuilt binaries
> +rm -rf examples/echo_test/binaries
> +
> +#archive
> +tar -cf ipc-lld.tar --exclude='*.tar' ./*
> +
> +install -d ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/ipc
> +find -name "*.tar" -exec tar xf {} --no-same-owner -C 
> ${D}${PDK_INSTALL_DIR_RECIPE}/packages/ti/drv/ipc \;
> +}
> +
> +FILES_${PN} += "${PDK_INSTALL_DIR_RECIPE}/packages"
> +
> +INSANE_SKIP_${PN} = "arch ldflags file-rdeps"
> +
> +INSANE_SKIP_${PN}-dbg = "arch"
> diff --git a/recipes-ti/ipc-lld/ipc-lld.inc b/recipes-ti/ipc-lld/ipc-lld.inc
> new file mode 100644
> index ..7a0ebec8
> --- /dev/null
> +++ b/recipes-ti/ipc-lld/ipc-lld.inc
> @@ -0,0 +1,38 @@
> +SUMMARY = "TI RTOS low level driver for IPC"

Both of the recipe that include this .inc overwrite SUMMARY anyway


> +
> +inherit ti-pdk
> +
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=7eae093f2b09fd39307f30028a068b91"
> +
> +COMPATIBLE_MACHINE = "k3"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +IPCLLD_GIT_URI = "git://git.ti.com/keystone-rtos/ipc-lld.git"
> +IPCLLD_GIT_PROTOCOL = "git"
> +IPCLLD_GIT_BRANCH = "ma

[meta-ti] [thud/master][PATCH] conf/machine: mtools and dosfsutils are now in wic depends by default

2019-09-23 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am65xx-evm.conf | 2 +-
 conf/machine/beagle-x15.conf | 2 --
 conf/machine/beaglebone.conf | 1 -
 conf/machine/j7-evm.conf | 2 +-
 4 files changed, 2 insertions(+), 5 deletions(-)

diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
index 0652a0af..cc15d73f 100644
--- a/conf/machine/am65xx-evm.conf
+++ b/conf/machine/am65xx-evm.conf
@@ -32,4 +32,4 @@ OPTEEOUTPUTMACHINE = "k3"
 IMAGE_BOOT_FILES = "tispl.bin u-boot.img"
 WKS_FILE ?= "sdimage-bootpart.wks"
 
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot u-boot:do_deploy"
+do_image_wic[depends] += "u-boot:do_deploy"
diff --git a/conf/machine/beagle-x15.conf b/conf/machine/beagle-x15.conf
index 1386ff05..d5e05ec7 100644
--- a/conf/machine/beagle-x15.conf
+++ b/conf/machine/beagle-x15.conf
@@ -16,8 +16,6 @@ WKS_FILE ?= "sdimage-bootpart.wks"
 IMAGE_BOOT_FILES = "MLO u-boot.img"
 IMAGE_FSTYPES += "tar.xz wic.xz"
 
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
-
 # UBI information.  Note that this is board and kernel specific.  Changes
 # in your kernel port may require changes in these variables.  For more
 # details about this board please see
diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 69db4215..d8fd4062 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -15,7 +15,6 @@ SERIAL_CONSOLES = "115200;ttyS0"
 
 WKS_FILE ?= "sdimage-bootpart.wks"
 
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
 IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} ${SPL_BINARY}"
 
 IMAGE_FSTYPES += "tar.xz wic.xz"
diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
index da3cc8e7..0a0c5bd5 100644
--- a/conf/machine/j7-evm.conf
+++ b/conf/machine/j7-evm.conf
@@ -29,7 +29,7 @@ OPTEEOUTPUTMACHINE = "k3"
 IMAGE_BOOT_FILES = "tispl.bin u-boot.img"
 WKS_FILE ?= "sdimage-bootpart.wks"
 
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot u-boot:do_deploy"
+do_image_wic[depends] += "u-boot:do_deploy"
 
 # Set the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_SOCS = "j721e"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] j7-evm: add new k3-j721e-proc-board-tps65917.dtb

2019-09-20 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/j7-evm.conf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
index 65525fa..da3cc8e 100644
--- a/conf/machine/j7-evm.conf
+++ b/conf/machine/j7-evm.conf
@@ -11,6 +11,7 @@ SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
 
 KERNEL_DEVICETREE = " \
 ti/k3-j721e-common-proc-board.dtb \
+ti/k3-j721e-proc-board-tps65917.dtb \
 ti/k3-j721e-common-proc-board-infotainment.dtbo \
 ti/k3-j721e-common-proc-board-infotainment-display-sharing.dtbo \
 ti/k3-j721e-common-proc-board-jailhouse.dtbo \
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH v2] ti-ipc: Update to new version 3.50.04.07

2019-09-19 Thread Denys Dmytriyenko
Now ti-ipc-examples-linux fails on Keystone2 devices and omapl138.


On Wed, Sep 18, 2019 at 02:50:46PM -0400, Sam Nelson wrote:
> Signed-off-by: Sam Nelson 
> 
> ---
> Update from previous version of the patch
> - Updated ipc-examples commit
> - This has dependency on sciclient update
> so nned to merge only after sciclient patch
> ---
> ---
>  recipes-ti/ipc/ti-ipc-common.inc | 2 +-
>  recipes-ti/ipc/ti-ipc-rtos.inc   | 8 
>  recipes-ti/ipc/ti-ipc.inc| 4 ++--
>  3 files changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/recipes-ti/ipc/ti-ipc-common.inc 
> b/recipes-ti/ipc/ti-ipc-common.inc
> index 4ec72cc..365486e 100644
> --- a/recipes-ti/ipc/ti-ipc-common.inc
> +++ b/recipes-ti/ipc/ti-ipc-common.inc
> @@ -1,4 +1,4 @@
> -PV = "3.50.04.06"
> +PV = "3.50.04.07"
>  INC_PR = "r0"
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> diff --git a/recipes-ti/ipc/ti-ipc-rtos.inc b/recipes-ti/ipc/ti-ipc-rtos.inc
> index 460befe..ef8640e 100644
> --- a/recipes-ti/ipc/ti-ipc-rtos.inc
> +++ b/recipes-ti/ipc/ti-ipc-rtos.inc
> @@ -24,10 +24,10 @@ protocol=${TI_IPC_METADATA_GIT_PROTOCOL};\
>  branch=${TI_IPC_METADATA_GIT_BRANCH};\
>  name=${TI_IPC_METADATA_NAME}"
>  
> -# Corresponds to tag: 3.50.04.06
> -TI_IPC_METADATA_SRCREV = "15d256ea3c3a35fe065a0513f09f4ea6ece58725"
> -# Corresponds to tag: 3.50.04.06
> -TI_IPC_EXAMPLES_SRCREV = "f29c27652302892abbe78ce2c22a2aae28b28d69"
> +# Corresponds to tag: 3.50.04.07
> +TI_IPC_METADATA_SRCREV = "37e85ff1966f7d093fe2bde2dd9d4546f29d0d80"
> +# Corresponds to tag: 3.50.04.07
> +TI_IPC_EXAMPLES_SRCREV = "90e68a120c29f489fc8760fe8b86c5b765bdd76f"
>  
>  SRCREV_FORMAT = "default"
>  SRCREV_ipc-metadata = "${TI_IPC_METADATA_SRCREV}"
> diff --git a/recipes-ti/ipc/ti-ipc.inc b/recipes-ti/ipc/ti-ipc.inc
> index b9f9ca9..000c5c0 100644
> --- a/recipes-ti/ipc/ti-ipc.inc
> +++ b/recipes-ti/ipc/ti-ipc.inc
> @@ -8,8 +8,8 @@ TI_IPC_GIT_URI = "git://git.ti.com/ipc/ipcdev.git"
>  TI_IPC_GIT_PROTOCOL = "git"
>  TI_IPC_GIT_BRANCH = "3.50"
>  
> -#Corresponds to 3.50.04.06
> -TI_IPC_SRCREV = "ca7ce99b8ec82331559f0fd99a174bdcca1da9ac"
> +#Corresponds to 3.50.04.07
> +TI_IPC_SRCREV = "129b6f44c50cbe760a5c1481b34b323b7a42ead5"
>  
>  BRANCH = "${TI_IPC_GIT_BRANCH}"
>  SRC_URI = 
> "${TI_IPC_GIT_URI};protocol=${TI_IPC_GIT_PROTOCOL};branch=${BRANCH};name=ipcdev"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] libion: update to fix musl builds by avoiding __BEGIN_DECL/__END_DECL

2019-09-17 Thread Denys Dmytriyenko
The fix from Khem Raj to use extern "C" instead of __BEGIN_DECL/__END_DECL 
macros

Signed-off-by: Denys Dmytriyenko 
Cc: Khem Raj 
---
 recipes-devtools/ion/libion_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-devtools/ion/libion_git.bb 
b/recipes-devtools/ion/libion_git.bb
index 7c93ed3..8bfe19e 100644
--- a/recipes-devtools/ion/libion_git.bb
+++ b/recipes-devtools/ion/libion_git.bb
@@ -7,7 +7,7 @@ PV = "1.0.0"
 
 BRANCH = "master"
 SRC_URI = "git://github.com/glneo/libion.git;protocol=git;branch=${BRANCH}"
-SRCREV = "11dad7977ec3ecba37c013da7ec0408c01413000"
+SRCREV = "813bd63e2f2118e17cb1c5d38505a1e572a2381c"
 
 S = "${WORKDIR}/git"
 
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud][PATCH V3] cpsw9g-eth-fw: Add CPSW 9G support for J7

2019-09-16 Thread Denys Dmytriyenko
On Mon, Sep 16, 2019 at 10:47:41AM +0530, Santhana Bharathi wrote:
> Signed-off-by: Santhana Bharathi 
> ---

Thanks. For next time please document patch revision changes here. I.e. what 
changed in v2, what changed in v3, etc. I'll merge this one as is now - no 
need to resubmit.


>  recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb | 44 
> ++
>  1 file changed, 44 insertions(+)
>  create mode 100644 recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> 
> diff --git a/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb 
> b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> new file mode 100644
> index 000..29a5f1d
> --- /dev/null
> +++ b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> @@ -0,0 +1,44 @@
> +SUMMARY = "R5 PSDK CPSW9G Ethernet Switch Firmware"
> +
> +LICENSE = "TI-TFL"
> +LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=04ad0a015d4bb63c2b9e7b112debf3db"
> +
> +PV = "1.0+git${SRCPV}"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +inherit deploy
> +inherit update-alternatives
> +
> +PROTOCOL = "git"
> +BRANCH = "master"
> +SRCREV = "df7f399319ee401dfbda9317878128a0f718507f"
> +
> +SRC_URI = 
> "git://git.ti.com/glsdk/ti-eth-fw.git;protocol=${PROTOCOL};branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +CPSW9G_FW_DIR = "${S}/ethfw"
> +CPSW9G_FW_FILENAME = "app_remoteswitchcfg_server.xer5f"
> +
> +# make sure that lib/firmware, and all its contents are part of the package
> +FILES_${PN} += "${base_libdir}/firmware"
> +
> +do_install() {
> +  install -d ${D}${base_libdir}/firmware
> +# Ethernet firmware to be loaded on Main R5 core(needs read permission)
> +  install -m 0644 ${CPSW9G_FW_DIR}/${CPSW9G_FW_FILENAME} 
> ${D}${base_libdir}/firmware
> +}
> +
> +TARGET_MAIN_R5FSS0_0 = "j7-main-r5f0_0-fw"
> +ALTERNATIVE_${PN} = "j7-main-r5f0_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
> +ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/${CPSW9G_FW_FILENAME}"
> +ALTERNATIVE_PRIORITY = "17"
> +
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +INSANE_SKIP_${PN} += "arch"
> +
> +do_compile[noexec] = "1"
> +do_configure[noexec] = "1"
> +
> -- 
> 1.9.1
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] meta-ti (a345e0c2) Linux kernel fails to boot on Beagleboard-xM (rev C)

2019-09-16 Thread Denys Dmytriyenko
On Thu, Sep 12, 2019 at 03:14:33PM +, kevin.e.cri...@l3harris.com wrote:
> I created a Yocto Project Bugzilla bug (13517) for this problem. Randy 
> MacLeod said "meta-ti is not tracked in this bugzilla. Please contact the 
> BSP owner".

> https://bugzilla.yoctoproject.org/show_bug.cgi?id=13517
> 
> What is the correct procedure for reporting problems with the meta-ti layer?

Kevin,

Thank you for the report.

Regarding the use of Yocto Project bugzilla for metat-ti bugs - I've discussed 
this with fellow Yocto Project TSC members and there's a confusion caused by 
limited resources. We'll try to get this sorted out...

Meanwhile, as of the booting issue itself. As you can see, meta-ti uses TI 
"staging" tree, where active development for current and latest platforms 
happens during the upstreaming process. OMAP3 SOC is 10-15 years old and what 
is called a legacy device. It has been fully supported in mainline Linux 
kernel for many years. Yes, TI is also responsible for maintaining existing 
support in the mainline kernel and ensuring no regressions. But that is not 
against the TI "staging" tree - i.e. there's no active testing being done of 
meta-ti working on OMAP3 platforms like Beagleboard-xM, unfortunately. This is 
left to corresponding communities, such as Beagleboard.org

I'll see what I can do to get this looked at in meta-ti. Otherwise, do you see 
any issues using a mainline kernel for your platform? Thanks.

-- 
Denys
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH] libion: Fix musl build

2019-09-16 Thread Denys Dmytriyenko
Khem,

Thanks for the fix. What's the Upstream-Status: ? :)
I guess "Pending" would be appropriate for now.


Andrew,

Would you be willing to take the change in, so we don't have to carry the 
patch in meta-ti, or do you see any issues with it?

-- 
Denys


On Sat, Sep 14, 2019 at 07:43:26AM -0700, Khem Raj wrote:
> Signed-off-by: Khem Raj 
> ---
>  ...tead-of-__BEGIN_DECL-__END_DECL-macr.patch | 42 +++
>  recipes-devtools/ion/libion_git.bb|  4 +-
>  2 files changed, 45 insertions(+), 1 deletion(-)
>  create mode 100644 
> recipes-devtools/ion/libion/0001-Use-extern-C-instead-of-__BEGIN_DECL-__END_DECL-macr.patch
> 
> diff --git 
> a/recipes-devtools/ion/libion/0001-Use-extern-C-instead-of-__BEGIN_DECL-__END_DECL-macr.patch
>  
> b/recipes-devtools/ion/libion/0001-Use-extern-C-instead-of-__BEGIN_DECL-__END_DECL-macr.patch
> new file mode 100644
> index ..530c869e
> --- /dev/null
> +++ 
> b/recipes-devtools/ion/libion/0001-Use-extern-C-instead-of-__BEGIN_DECL-__END_DECL-macr.patch
> @@ -0,0 +1,42 @@
> +From 197e7bf9a20076c6564a860bd2215e8101ee4cad Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Sat, 14 Sep 2019 07:36:47 -0700
> +Subject: [PATCH] Use extern "C" instead of __BEGIN_DECL/__END_DECL macros
> +
> +these macros are defined in sys/cdefs.h for glibc and this header is not 
> available on all libc
> +
> +for glibc they are defined like below
> +
> +Signed-off-by: Khem Raj 
> +---
> + include/ion/ion.h | 8 ++--
> + 1 file changed, 6 insertions(+), 2 deletions(-)
> +
> +diff --git a/include/ion/ion.h b/include/ion/ion.h
> +index 81ab9cc..e95df4b 100644
> +--- a/include/ion/ion.h
>  b/include/ion/ion.h
> +@@ -24,7 +24,9 @@
> + #include 
> + #include 
> + 
> +-__BEGIN_DECLS
> ++#ifdef __cplusplus
> ++extern "C" {
> ++#endif
> + 
> + int ion_open();
> + int ion_close(int fd);
> +@@ -34,6 +36,8 @@ int ion_free(int fd, int handle_fd);
> + int ion_query_heap_cnt(int fd, int* cnt);
> + int ion_query_get_heaps(int fd, int cnt, void* buffers);
> + 
> +-__END_DECLS
> ++#ifdef __cplusplus
> ++}
> ++#endif
> + 
> + #endif /* __ION_H */
> +-- 
> +2.23.0
> +
> diff --git a/recipes-devtools/ion/libion_git.bb 
> b/recipes-devtools/ion/libion_git.bb
> index 7c93ed3f..38ba9bd8 100644
> --- a/recipes-devtools/ion/libion_git.bb
> +++ b/recipes-devtools/ion/libion_git.bb
> @@ -6,7 +6,9 @@ LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
>  PV = "1.0.0"
>  
>  BRANCH = "master"
> -SRC_URI = "git://github.com/glneo/libion.git;protocol=git;branch=${BRANCH}"
> +SRC_URI = "git://github.com/glneo/libion.git;protocol=git;branch=${BRANCH} \
> +   
> file://0001-Use-extern-C-instead-of-__BEGIN_DECL-__END_DECL-macr.patch \
> +"
>  SRCREV = "11dad7977ec3ecba37c013da7ec0408c01413000"
>  
>  S = "${WORKDIR}/git"
> -- 
> 2.23.0
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master][RFC] Mesa recipie now provides GL frontend libs

2019-09-16 Thread Denys Dmytriyenko
On Mon, Sep 16, 2019 at 11:52:42AM -0400, Andrew F. Davis wrote:
> On 9/16/19 11:43 AM, Denys Dmytriyenko wrote:
> > Andrew,
> > 
> > Thanks for pushing this forward! I'll give it some thought and more 
> > thorough 
> > review, but the first comment I had so far is that bbappend won't work for 
> > this purpose, as it would modify Mesa recipe unconditionally and BSP layers 
> > are not allowed to do that.
> 
> It wouldn't have to be unconditional would it, how do others change a
> packages URL to a forked version?

It's harder to make bbappends unconditional. The Yocto Project Compatible 
requirement states that a mere inclusion of a layer should not alter core 
recipes in unconditional way. Any such changes should be explicitly enabled by 
either a separate variable, or only applicable to those platforms defined by 
the layer. This requirement was originally for BSP layers (which meta-ti is) 
and later extended to other layers, including Distros. That's why a lot of 
forking and customizations was done in meta-arago, and not in meta-ti. As an 
example, here's a proper bbappend in meta-ti, that only makes alterations for 
our platforms - note that every variable uses ti-soc override, which was added 
to easily address all TI platforms:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-core/udev/eudev_%25.bbappend

This means that adding meta-ti layer into your setup, but building for non-TI 
platform, won't change SRC_URI and PR variables, as well, as do_install() task 
for core eudev recipe.

Actually, instead of using a bbappend, having a modified mesa-pvr recipe that 
PROVIDES="mesa" is a better alternative, as setting PREFERRED_PROVIDER easily 
satisfies the above requirement.


> > Also, can the dependency between Mesa and DDK be 
> > the other way around?
> > 
> 
> I'm not sure what you mean here, DDK depend on Mesa? If so I'm not sure
> how that would work, Mesa provides the front-end libs, it has a link
> time dependency on the backend driver (pvr_dri_support.so).
> 
> Well thinking a bit more I probably could make them build independently,
> as Mesa dlopens the backend and relies on it exporting an interface that
> Mesa defines, so really there is no built-time inter-dependency at all..
> but what would that do for us?

Are there any other precedents for Mesa to have a separate backend driver that 
gets built on its own? Making generic Mesa (if we ever want to upstream this 
support) build-depend on platform-specific component would be questionable.

-- 
Denys


> Andrew
> 
> > Denys
> > 
> > 
> > On Sat, Sep 14, 2019 at 09:51:51AM -0400, Andrew F. Davis wrote:
> >> Signed-off-by: Andrew F. Davis 
> >> ---
> >>
> >> Hello all,
> >>
> >> This is a preview change of our GPU driver stack. Mesa can now used to
> >> provide the GL frontend libraries (EGL/GBM) for our SGX based systems.
> >> This greatly expands our supported extensions and improves compatibility
> >> with software designed to work with Mesa and Mesa provided tooling. The
> >> existing backend is now confined to just a DRI backend used to provide
> >> the GLES1/2 functions. The extensions/compatibility on this part of the
> >> stack will not change.
> >>
> >> The Mesa-side-glue to interface with the SGX DRI blobs is currently
> >> internal only until we can find the right way to distribute the patches
> >> (recipe patches in meta-ti or as a fork of Mesa hosted on git.ti.com).
> >> Currently they are on my internal only bitbucket, so those outside TI
> >> will not be able to test just yet :( but can review this recipe patch
> >> just the same.
> >>
> >> What you need to do right now for this to have an effect is to change
> >> your preferred provider of GL libs over in your distro layer to the
> >> new mesa-pvr.
> >>
> >> -PREFERRED_PROVIDER_virtual/egl = "ti-sgx-ddk-um"
> >> -PREFERRED_PROVIDER_virtual/libgles1 = "ti-sgx-ddk-um"
> >> -PREFERRED_PROVIDER_virtual/libgles2 = "ti-sgx-ddk-um"
> >> -PREFERRED_PROVIDER_virtual/libgbm = "ti-sgx-ddk-um"
> >> +PREFERRED_PROVIDER_virtual/egl = "mesa-pvr"
> >> +PREFERRED_PROVIDER_virtual/libgles1 = "mesa-pvr"
> >> +PREFERRED_PROVIDER_virtual/libgles2 = "mesa-pvr"
> >> +PREFERRED_PROVIDER_virtual/libgbm = "mesa-pvr"
> >>
> >> At some point I'd like this to just be "mesa" but with some bbappends to
> >> change the repo and some per platform PACKAGECONFIG magic set so it
> >> builds the same a

Re: [meta-ti] [master][RFC] Mesa recipie now provides GL frontend libs

2019-09-16 Thread Denys Dmytriyenko
Andrew,

Thanks for pushing this forward! I'll give it some thought and more thorough 
review, but the first comment I had so far is that bbappend won't work for 
this purpose, as it would modify Mesa recipe unconditionally and BSP layers 
are not allowed to do that. Also, can the dependency between Mesa and DDK be 
the other way around?

Denys


On Sat, Sep 14, 2019 at 09:51:51AM -0400, Andrew F. Davis wrote:
> Signed-off-by: Andrew F. Davis 
> ---
> 
> Hello all,
> 
> This is a preview change of our GPU driver stack. Mesa can now used to
> provide the GL frontend libraries (EGL/GBM) for our SGX based systems.
> This greatly expands our supported extensions and improves compatibility
> with software designed to work with Mesa and Mesa provided tooling. The
> existing backend is now confined to just a DRI backend used to provide
> the GLES1/2 functions. The extensions/compatibility on this part of the
> stack will not change.
> 
> The Mesa-side-glue to interface with the SGX DRI blobs is currently
> internal only until we can find the right way to distribute the patches
> (recipe patches in meta-ti or as a fork of Mesa hosted on git.ti.com).
> Currently they are on my internal only bitbucket, so those outside TI
> will not be able to test just yet :( but can review this recipe patch
> just the same.
> 
> What you need to do right now for this to have an effect is to change
> your preferred provider of GL libs over in your distro layer to the
> new mesa-pvr.
> 
> -PREFERRED_PROVIDER_virtual/egl = "ti-sgx-ddk-um"
> -PREFERRED_PROVIDER_virtual/libgles1 = "ti-sgx-ddk-um"
> -PREFERRED_PROVIDER_virtual/libgles2 = "ti-sgx-ddk-um"
> -PREFERRED_PROVIDER_virtual/libgbm = "ti-sgx-ddk-um"
> +PREFERRED_PROVIDER_virtual/egl = "mesa-pvr"
> +PREFERRED_PROVIDER_virtual/libgles1 = "mesa-pvr"
> +PREFERRED_PROVIDER_virtual/libgles2 = "mesa-pvr"
> +PREFERRED_PROVIDER_virtual/libgbm = "mesa-pvr"
> 
> At some point I'd like this to just be "mesa" but with some bbappends to
> change the repo and some per platform PACKAGECONFIG magic set so it
> builds the same as this recipe.
> 
> All comments, opinions, and concerns welcome :)
> 
> Andrew
> 
>  recipes-graphics/libgles/mesa-pvr_git.bb  | 46 +++
>  .../libgles/ti-sgx-ddk-um_1.17.4948957.bb | 28 ++-
>  2 files changed, 49 insertions(+), 25 deletions(-)
>  create mode 100644 recipes-graphics/libgles/mesa-pvr_git.bb
> 
> diff --git a/recipes-graphics/libgles/mesa-pvr_git.bb 
> b/recipes-graphics/libgles/mesa-pvr_git.bb
> new file mode 100644
> index ..f66197c5
> --- /dev/null
> +++ b/recipes-graphics/libgles/mesa-pvr_git.bb
> @@ -0,0 +1,46 @@
> +SUMMARY = "Mesa with IMG PVR DRI driver"
> +
> +HOMEPAGE = "http://mesa3d.org";
> +LICENSE = "MIT"
> +LIC_FILES_CHKSUM = 
> "file://docs/license.html;md5=725f991a1cc322aa7a0cd3a2016621c4"
> +
> +PV = "0.0+${PR}+gitr${SRCREV}"
> +
> +SRC_URI = 
> "git://g...@bitbucket.itg.ti.com/~a0226330/mesa.git;protocol=ssh;branch=${BRANCH}"
> +BRANCH = "mesa-19.1.6-pvr-buildup"
> +SRCREV = "ea27ae6fdaf9d813dc484113661afa6276cdd5da"
> +
> +S = "${WORKDIR}/git"
> +
> +DEPENDS = "expat makedepend-native flex-native bison-native libxml2-native 
> zlib chrpath-replacement-native python3-mako-native gettext-native 
> wayland-native wayland libdrm wayland-protocols xorgproto libdrm 
> ti-sgx-ddk-um"
> +RDEPENDS_${PN} = "ti-sgx-ddk-um"
> +EXTRANATIVEPATH += "chrpath-native"
> +PROVIDES = "virtual/libgles1 virtual/libgles2 virtual/egl virtual/libgbm"
> +
> +inherit meson pkgconfig python3native gettext distro_features_check
> +
> +BBCLASSEXTEND = "native nativesdk"
> +
> +ANY_OF_DISTRO_FEATURES_class-target = "opengl vulkan"
> +
> +EXTRA_OEMESON = " \
> +-Dshared-glapi=true \
> +-Dgallium-opencl=disabled \
> +-Dglx-read-only-text=true \
> +-Dplatforms=wayland,drm \
> +-Dglx=disabled \
> +-Ddri-drivers=pvr \
> +-Ddri3=false \
> +-Dgles1=true \
> +-Dgles2=true \
> +-Degl=true \
> +-Dgallium-drivers='' \
> +-Dvulkan-drivers='' \
> +-Dllvm=false \
> +-Dlibunwind=false \
> +"
> +
> +# mesa tries to run cross-built gen_matypes on build machine to get struct 
> size information
> +EXTRA_OEMESON_append = " -Dasm=false"
> +
> +FILES_${PN} += " ${libdir}/dri/*"
> diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb 
> b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> index 7a6f013e..f063e455 100644
> --- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> +++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
> @@ -6,12 +6,12 @@ LIC_FILES_CHKSUM = 
> "file://TI-Linux-Graphics-DDK-UM-Manifest.doc;md5=b17390502bc
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  COMPATIBLE_MACHINE = "ti33x|ti43x|omap-a15|k3"
>  
> -PR = "r34"
> +PR = "r35"
>  
> -BRANCH = "ti-img-sgx/thud/${PV}"
> +BRANCH = "ti-img-sgx/thud/${PV}-mesa-experimental"
>  
>  SRC_URI = 
> "git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git;protocol=git;branch=${BRANCH}"
> -SRCREV = "87d7e5c1

Re: [meta-ti] [thud][PATCH v2] videnc-test-app: Add the videnc-test-app recipe

2019-09-13 Thread Denys Dmytriyenko
On Fri, Sep 13, 2019 at 03:58:12PM -0500, David Huang wrote:
> The videnc-test-app provides the video encoder test app
> (tienc_encode) for j7-evm.
> 
> Signed-off-by: David Huang 
> ---

v2 changes here?


>  .../ti-img-encode-decode/videnc-test-app_1.0.0.bb  | 18 
> ++
>  1 file changed, 18 insertions(+)
>  create mode 100644 recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb
> 
> diff --git a/recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb 
> b/recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb
> new file mode 100644
> index ..1725da7eb6d9
> --- /dev/null
> +++ b/recipes-bsp/ti-img-encode-decode/videnc-test-app_1.0.0.bb
> @@ -0,0 +1,18 @@
> +SUMMARY = "Test applications for TI DEC (v4l2 decoder for IMG D5520)"

Encoder instead of decoder?


> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = 
> "file://main.c;beginline=1;endline=14;md5=3545dd5bdf513840937d38c10b866605"
> +
> +DEPENDS = "libdrm"
> +
> +inherit autotools pkgconfig
> +
> +PR = "r0"
> +SRCREV = "a5e7d820bea1be24f25a8369d4d4521c784f869a"
> +
> +EXTRA_OEMAKE = "CC="${CC}""
> +TARGET_CC_ARCH += "${LDFLAGS}"
> +
> +BRANCH = "master"
> +SRC_URI = 
> "git://git.ti.com/jacinto7_multimedia/videnc-test-app.git;protocol=git;branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud][PATCH V2] cpsw9g-eth-fw: Add CPSW 9G support for J7

2019-09-13 Thread Denys Dmytriyenko
On Fri, Sep 13, 2019 at 01:27:12PM +0530, Santhana Bharathi wrote:
> Signed-off-by: Santhana Bharathi 
> ---
>  recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb | 43 
> ++
>  1 file changed, 43 insertions(+)
>  create mode 100644 recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> 
> diff --git a/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb 
> b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> new file mode 100644
> index 000..2c597ff
> --- /dev/null
> +++ b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> @@ -0,0 +1,43 @@
> +SUMMARY = "R5 PSDK CPSW9G Ethernet Switch Firmware"
> +
> +LICENSE = "TI-TFL"
> +LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=04ad0a015d4bb63c2b9e7b112debf3db"
> +
> +PV = "1.0+git${SRCPV}"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +inherit deploy
> +inherit update-alternatives
> +
> +PROTOCOL = "git"
> +BRANCH = "master"
> +SRCREV = "df7f399319ee401dfbda9317878128a0f718507f"
> +
> +SRC_URI = 
> "git://git.ti.com/glsdk/ti-eth-fw.git;protocol=${PROTOCOL};branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +CPSW9G_FW_DIR = "${S}/ethfw"
> +CPSW9G_FW_FILENAME = "app_remoteswitchcfg_server.xer5f"
> +
> +# make sure that lib/firmware, and all its contents are part of the package
> +FILES_${PN} += "${base_libdir}/firmware"
> +
> +do_install() {
> +  install -d ${D}${base_libdir}/firmware
> +  install -m 0555 ${CPSW9G_FW_DIR}/${CPSW9G_FW_FILENAME} 
> ${D}${base_libdir}/firmware

0555 doesn't seem right. Standard Unix permissions are 0755 for executables 
and 0644 for regular files. Unless you specifically need something else - 
please explain.


> +}
> +
> +TARGET_MAIN_R5FSS0_0 = "j7-main-r5f0_0-fw"
> +ALTERNATIVE_${PN} = "j7-main-r5f0_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
> +ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/${CPSW9G_FW_FILENAME}"
> +ALTERNATIVE_PRIORITY = "17"
> +
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +INSANE_SKIP_${PN} += "arch"
> +
> +do_compile[noexec] = "1"
> +do_configure[noexec] = "1"
> +
> -- 
> 1.9.1
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH] ion: add libion and ion-tests packages for ION support

2019-09-13 Thread Denys Dmytriyenko
Ok, I'll take a look. Thanks.

On Fri, Sep 13, 2019 at 06:24:48AM -0700, Khem Raj wrote:
> thai breaks on musl  see
> 
> https://errors.yoctoproject.org/Errors/Details/270173/
> 
> a patch like meta/recipes-support/attr/attr/dont-use-decl-macros.patch
> from oe-core will solve it. Care to fix ?
> 
> On Thu, Sep 12, 2019 at 8:22 PM Denys Dmytriyenko  wrote:
> >
> > ION Userspace Memory Allocator Library and tests
> >
> > Signed-off-by: Denys Dmytriyenko 
> > ---
> >  ...-CMakeLists.txt-disable-phys-addr-for-now.patch | 34 
> > ++
> >  recipes-devtools/ion/ion-tests_git.bb  | 18 
> >  recipes-devtools/ion/libion_git.bb | 14 +
> >  3 files changed, 66 insertions(+)
> >  create mode 100644 
> > recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
> >  create mode 100644 recipes-devtools/ion/ion-tests_git.bb
> >  create mode 100644 recipes-devtools/ion/libion_git.bb
> >
> > diff --git 
> > a/recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
> >  
> > b/recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
> > new file mode 100644
> > index 000..7cf5895
> > --- /dev/null
> > +++ 
> > b/recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
> > @@ -0,0 +1,34 @@
> > +From 85264fc72a261d20107a50ea2fad0258900a132b Mon Sep 17 00:00:00 2001
> > +From: Denys Dmytriyenko 
> > +Date: Sat, 20 Apr 2019 16:54:03 +
> > +Subject: [PATCH] CMakeLists.txt: disable phys-addr for now
> > +
> > +Signed-off-by: Denys Dmytriyenko 
> > +---
> > + CMakeLists.txt | 13 -
> > + 1 file changed, 13 deletions(-)
> > +
> > +diff --git a/CMakeLists.txt b/CMakeLists.txt
> > +index 1d60003..eca6ba7 100644
> > +--- a/CMakeLists.txt
> >  b/CMakeLists.txt
> > +@@ -54,16 +54,3 @@ target_link_libraries(ion-print-heaps
> > + target_include_directories(ion-print-heaps PUBLIC ${LIBION_INCLUDE_DIRS})
> > +
> > + install(TARGETS ion-print-heaps RUNTIME DESTINATION bin)
> > +-
> > +-# phys-addr
> > +-
> > +-add_executable(phys-addr
> > +-  src/phys-addr.c
> > +-)
> > +-
> > +-target_link_libraries(phys-addr
> > +-  ${LIBION_LIBRARIES}
> > +-)
> > +-target_include_directories(phys-addr PUBLIC ${LIBION_INCLUDE_DIRS})
> > +-
> > +-install(TARGETS phys-addr RUNTIME DESTINATION bin)
> > +--
> > +2.17.1
> > +
> > diff --git a/recipes-devtools/ion/ion-tests_git.bb 
> > b/recipes-devtools/ion/ion-tests_git.bb
> > new file mode 100644
> > index 000..831f5e8
> > --- /dev/null
> > +++ b/recipes-devtools/ion/ion-tests_git.bb
> > @@ -0,0 +1,18 @@
> > +SUMMARY = "Test cases for ION"
> > +HOMEPAGE = "https://github.com/glneo/ion-tests";
> > +LICENSE = "Apache-2.0"
> > +LIC_FILES_CHKSUM = 
> > "file://src/ion_test.c;beginline=1;endline=15;md5=b225db900869a4cd31461606e55a3ec5"
> > +
> > +PV = "1.0"
> > +
> > +BRANCH = "master"
> > +SRC_URI = 
> > "git://github.com/glneo/ion-tests.git;protocol=git;branch=${BRANCH} \
> > +   file://0001-CMakeLists.txt-disable-phys-addr-for-now.patch \
> > +"
> > +SRCREV = "70d730cebca29e6fd37b21d9beac82ae645f3900"
> > +
> > +DEPENDS = "libion gtest"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +inherit cmake pkgconfig
> > diff --git a/recipes-devtools/ion/libion_git.bb 
> > b/recipes-devtools/ion/libion_git.bb
> > new file mode 100644
> > index 000..7c93ed3
> > --- /dev/null
> > +++ b/recipes-devtools/ion/libion_git.bb
> > @@ -0,0 +1,14 @@
> > +SUMMARY = "ION Userspace Memory Allocator Library"
> > +HOMEPAGE = "https://github.com/glneo/libion";
> > +LICENSE = "Apache-2.0"
> > +LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
> > +
> > +PV = "1.0.0"
> > +
> > +BRANCH = "master"
> > +SRC_URI = "git://github.com/glneo/libion.git;protocol=git;branch=${BRANCH}"
> > +SRCREV = "11dad7977ec3ecba37c013da7ec0408c01413000"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +inherit cmake pkgconfig
> > --
> > 2.7.4
> >
> > --
> > ___
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud][PATCH] cpsw9g-eth-fw: Add CPSW 9G support for J7

2019-09-12 Thread Denys Dmytriyenko
On Thu, Sep 12, 2019 at 12:40:43PM -0400, Denys Dmytriyenko wrote:
> Thanks, but please subscribe to the list before posting.
> 
> 
> On Thu, Sep 12, 2019 at 10:04:05PM +0530, Santhana Bharathi wrote:
> > Signed-off-by: Santhana Bharathi 
> > ---
> >  recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb | 47 
> > ++
> >  1 file changed, 47 insertions(+)
> >  create mode 100644 recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> > 
> > diff --git a/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb 
> > b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> > new file mode 100644
> > index 000..8677034
> > --- /dev/null
> > +++ b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> > @@ -0,0 +1,47 @@
> > +Summary = "R5 PSDK CPSW9G ethernet switch firmware"
> 
> Uppercase
> 
> 
> > +LICENSE = "TI-TFL"
> > +LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=04ad0a015d4bb63c2b9e7b112debf3db"
> > +
> > +PV = "1.0-git${SRCPV}"
> 
> 1.0+git...
> 
> 
> > +PACKAGE_ARCH = "${MACHINE_ARCH}"
> > +
> > +inherit deploy
> > +inherit update-alternatives
> > +
> > +PROTOCOL = "git"
> > +BRANCH = "master"
> > +SRCREV = "df7f399319ee401dfbda9317878128a0f718507f"
> > +
> > +SRC_URI = 
> > "git://git.ti.com/glsdk/ti-eth-fw.git;protocol=${PROTOCOL};branch=${BRANCH}"
> > +
> > +S = "${WORKDIR}/git"
> > +
> > +CPSW9G_FW_DIR = "${S}/ethfw"
> > +CPSW9G_FW_FILENAME = "app_remoteswitchcfg_server.xer5f"
> > +
> > +# make sure that lib/firmware, and all its contents are part of the package
> > +FILES_${PN} += "${base_libdir}/firmware"
> > +
> > +do_install() {
> > +  install -d ${D}${base_libdir}/firmware
> > +  install -m 0755 ${CPSW9G_FW_DIR}/${CPSW9G_FW_FILENAME} 
> > ${D}${base_libdir}/firmware

Also, why is it setting 755 permissions?


> > +}
> > +
> > +TARGET_MAIN_R5FSS0_0 = "j7-main-r5f0_0-fw"
> > +ALTERNATIVE_${PN} = "j7-main-r5f0_0-fw"
> > +ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = 
> > "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
> > +ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = 
> > "${base_libdir}/firmware/${CPSW9G_FW_FILENAME}"
> > +ALTERNATIVE_PRIORITY = "17"
> > +
> > +# This is used to prevent the build system to strip the executables
> > +INHIBIT_PACKAGE_STRIP = "1"
> > +# This is used to prevent the build system to split the debug info in a 
> > separate file
> > +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> > +# As it likely to be a different arch from the Yocto build, disable 
> > checking by adding "arch" to INSANE_SKIP
> > +INSANE_SKIP_${PN} += "arch"
> 
> No need to comment each and every line here - those comments were provided in 
> the example to explain what they do, but they don't need to be copied over 
> and 
> over in every new recipe...
> 
> 
> > +# we don't want to configure and build the source code
> > +do_compile[noexec] = "1"
> > +do_configure[noexec] = "1"
> > +
> > -- 
> > 1.9.1
> > 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] ion: add libion and ion-tests packages for ION support

2019-09-12 Thread Denys Dmytriyenko
ION Userspace Memory Allocator Library and tests

Signed-off-by: Denys Dmytriyenko 
---
 ...-CMakeLists.txt-disable-phys-addr-for-now.patch | 34 ++
 recipes-devtools/ion/ion-tests_git.bb  | 18 
 recipes-devtools/ion/libion_git.bb | 14 +
 3 files changed, 66 insertions(+)
 create mode 100644 
recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
 create mode 100644 recipes-devtools/ion/ion-tests_git.bb
 create mode 100644 recipes-devtools/ion/libion_git.bb

diff --git 
a/recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
 
b/recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
new file mode 100644
index 000..7cf5895
--- /dev/null
+++ 
b/recipes-devtools/ion/ion-tests/0001-CMakeLists.txt-disable-phys-addr-for-now.patch
@@ -0,0 +1,34 @@
+From 85264fc72a261d20107a50ea2fad0258900a132b Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko 
+Date: Sat, 20 Apr 2019 16:54:03 +
+Subject: [PATCH] CMakeLists.txt: disable phys-addr for now
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ CMakeLists.txt | 13 -
+ 1 file changed, 13 deletions(-)
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 1d60003..eca6ba7 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -54,16 +54,3 @@ target_link_libraries(ion-print-heaps
+ target_include_directories(ion-print-heaps PUBLIC ${LIBION_INCLUDE_DIRS})
+ 
+ install(TARGETS ion-print-heaps RUNTIME DESTINATION bin)
+-
+-# phys-addr
+-
+-add_executable(phys-addr
+-  src/phys-addr.c
+-)
+-
+-target_link_libraries(phys-addr
+-  ${LIBION_LIBRARIES}
+-)
+-target_include_directories(phys-addr PUBLIC ${LIBION_INCLUDE_DIRS})
+-
+-install(TARGETS phys-addr RUNTIME DESTINATION bin)
+-- 
+2.17.1
+
diff --git a/recipes-devtools/ion/ion-tests_git.bb 
b/recipes-devtools/ion/ion-tests_git.bb
new file mode 100644
index 000..831f5e8
--- /dev/null
+++ b/recipes-devtools/ion/ion-tests_git.bb
@@ -0,0 +1,18 @@
+SUMMARY = "Test cases for ION"
+HOMEPAGE = "https://github.com/glneo/ion-tests";
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = 
"file://src/ion_test.c;beginline=1;endline=15;md5=b225db900869a4cd31461606e55a3ec5"
+
+PV = "1.0"
+
+BRANCH = "master"
+SRC_URI = "git://github.com/glneo/ion-tests.git;protocol=git;branch=${BRANCH} \
+   file://0001-CMakeLists.txt-disable-phys-addr-for-now.patch \
+"
+SRCREV = "70d730cebca29e6fd37b21d9beac82ae645f3900"
+
+DEPENDS = "libion gtest"
+
+S = "${WORKDIR}/git"
+
+inherit cmake pkgconfig
diff --git a/recipes-devtools/ion/libion_git.bb 
b/recipes-devtools/ion/libion_git.bb
new file mode 100644
index 000..7c93ed3
--- /dev/null
+++ b/recipes-devtools/ion/libion_git.bb
@@ -0,0 +1,14 @@
+SUMMARY = "ION Userspace Memory Allocator Library"
+HOMEPAGE = "https://github.com/glneo/libion";
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
+
+PV = "1.0.0"
+
+BRANCH = "master"
+SRC_URI = "git://github.com/glneo/libion.git;protocol=git;branch=${BRANCH}"
+SRCREV = "11dad7977ec3ecba37c013da7ec0408c01413000"
+
+S = "${WORKDIR}/git"
+
+inherit cmake pkgconfig
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [master][PATCH] ti-softhsmv2, libp11, engine-pkcs11: openssl10 is no longer available

2019-09-12 Thread Denys Dmytriyenko
These packages still need to be migrated from 1.0 API to 1.1
Specific to Keystone2 platforms.

Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/engine-pkcs11/engine-pkcs11_git.bb | 2 +-
 recipes-ti/libp11/libp11_git.bb   | 2 +-
 recipes-ti/ti-softhsmv2/ti-softhsmv2_git.bb   | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-ti/engine-pkcs11/engine-pkcs11_git.bb 
b/recipes-ti/engine-pkcs11/engine-pkcs11_git.bb
index 7dd6f09..01bd58f 100644
--- a/recipes-ti/engine-pkcs11/engine-pkcs11_git.bb
+++ b/recipes-ti/engine-pkcs11/engine-pkcs11_git.bb
@@ -5,7 +5,7 @@ SECTION = "libs"
 
 inherit autotools pkgconfig
 
-DEPENDS = "openssl10 libtool libp11"
+DEPENDS = "openssl libtool libp11"
 
 COMPATIBLE_MACHINE = "keystone"
 
diff --git a/recipes-ti/libp11/libp11_git.bb b/recipes-ti/libp11/libp11_git.bb
index 9b1ea3e..a768f15 100644
--- a/recipes-ti/libp11/libp11_git.bb
+++ b/recipes-ti/libp11/libp11_git.bb
@@ -5,7 +5,7 @@ SECTION = "libs"
 
 inherit autotools pkgconfig
 
-DEPENDS = "openssl10 libtool"
+DEPENDS = "openssl libtool"
 RDEPENDS_${PN} = "ti-softhsmv2"
 
 COMPATIBLE_MACHINE = "keystone"
diff --git a/recipes-ti/ti-softhsmv2/ti-softhsmv2_git.bb 
b/recipes-ti/ti-softhsmv2/ti-softhsmv2_git.bb
index d281a51..6a196ae 100644
--- a/recipes-ti/ti-softhsmv2/ti-softhsmv2_git.bb
+++ b/recipes-ti/ti-softhsmv2/ti-softhsmv2_git.bb
@@ -7,7 +7,7 @@ mntdir = "/mnt"
 
 inherit autotools pkgconfig
 
-DEPENDS = "openssl10 libdaemon zlib"
+DEPENDS = "openssl libdaemon zlib"
 COMPATIBLE_MACHINE = "keystone"
 
 BRANCH = "ti-softhsm-rebase"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud][PATCH] cpsw9g-eth-fw: Add CPSW 9G support for J7

2019-09-12 Thread Denys Dmytriyenko
Thanks, but please subscribe to the list before posting.


On Thu, Sep 12, 2019 at 10:04:05PM +0530, Santhana Bharathi wrote:
> Signed-off-by: Santhana Bharathi 
> ---
>  recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb | 47 
> ++
>  1 file changed, 47 insertions(+)
>  create mode 100644 recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> 
> diff --git a/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb 
> b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> new file mode 100644
> index 000..8677034
> --- /dev/null
> +++ b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> @@ -0,0 +1,47 @@
> +Summary = "R5 PSDK CPSW9G ethernet switch firmware"

Uppercase


> +LICENSE = "TI-TFL"
> +LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=04ad0a015d4bb63c2b9e7b112debf3db"
> +
> +PV = "1.0-git${SRCPV}"

1.0+git...


> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +inherit deploy
> +inherit update-alternatives
> +
> +PROTOCOL = "git"
> +BRANCH = "master"
> +SRCREV = "df7f399319ee401dfbda9317878128a0f718507f"
> +
> +SRC_URI = 
> "git://git.ti.com/glsdk/ti-eth-fw.git;protocol=${PROTOCOL};branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +CPSW9G_FW_DIR = "${S}/ethfw"
> +CPSW9G_FW_FILENAME = "app_remoteswitchcfg_server.xer5f"
> +
> +# make sure that lib/firmware, and all its contents are part of the package
> +FILES_${PN} += "${base_libdir}/firmware"
> +
> +do_install() {
> +  install -d ${D}${base_libdir}/firmware
> +  install -m 0755 ${CPSW9G_FW_DIR}/${CPSW9G_FW_FILENAME} 
> ${D}${base_libdir}/firmware
> +}
> +
> +TARGET_MAIN_R5FSS0_0 = "j7-main-r5f0_0-fw"
> +ALTERNATIVE_${PN} = "j7-main-r5f0_0-fw"
> +ALTERNATIVE_LINK_NAME[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_0}"
> +ALTERNATIVE_TARGET[j7-main-r5f0_0-fw] = 
> "${base_libdir}/firmware/${CPSW9G_FW_FILENAME}"
> +ALTERNATIVE_PRIORITY = "17"
> +
> +# This is used to prevent the build system to strip the executables
> +INHIBIT_PACKAGE_STRIP = "1"
> +# This is used to prevent the build system to split the debug info in a 
> separate file
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +# As it likely to be a different arch from the Yocto build, disable checking 
> by adding "arch" to INSANE_SKIP
> +INSANE_SKIP_${PN} += "arch"

No need to comment each and every line here - those comments were provided in 
the example to explain what they do, but they don't need to be copied over and 
over in every new recipe...


> +# we don't want to configure and build the source code
> +do_compile[noexec] = "1"
> +do_configure[noexec] = "1"
> +
> -- 
> 1.9.1
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 2/4] ti-img-rogue-driver: port generic toolchain support from SGX

2019-09-11 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 .../0001-km-support-general-toolchain.patch| 56 ++
 .../ti-img-rogue-driver_1.10.5371573.bb|  4 +-
 2 files changed, 59 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch

diff --git 
a/recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch
 
b/recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch
new file mode 100644
index 000..4dc219c
--- /dev/null
+++ 
b/recipes-bsp/powervr-drivers/ti-img-rogue-driver/0001-km-support-general-toolchain.patch
@@ -0,0 +1,56 @@
+From dbdbd9309a58ee723fc827ef5fd45c28347cf61f Mon Sep 17 00:00:00 2001
+From: Eric Ruei 
+Date: Tue, 7 May 2019 17:06:09 -0400
+Subject: [PATCH] km: support general toolchain
+
+This is a patch from IMG to support general toolchains such as
+aarch64-oe-linux-gnu, aarch64-poky-linux-gnu, arm-none-linux-gnueabi
+per IMG ticket 122059
+
+Signed-off-by: Eric Ruei 
+Signed-off-by: Denys Dmytriyenko 
+---
+ build/linux/config/compiler.mk| 12 +++-
+ .../build/linux/config/compilers/arm-linux-gnueabi.mk   |  6 ++
+ 2 files changed, 17 insertions(+), 1 deletion(-)
+ create mode 100644 build/linux/config/compilers/arm-linux-gnueabi.mk
+
+diff --git a/build/linux/config/compiler.mk b/build/linux/config/compiler.mk
+index 82c9d44..dead2f9 100644
+--- a/build/linux/config/compiler.mk
 b/build/linux/config/compiler.mk
+@@ -48,13 +48,14 @@ define calculate-compiler-preferred-target
+  ifeq ($(2),qcc)
+   $(1)_compiler_preferred_target := qcc
+  else
+-  $(1)_compiler_preferred_target := $$(subst --,-,$$(shell $(2) -dumpmachine))
++  $(1)_compiler_preferred_target := $$(subst --,-,$$(subst unknown,,$$(shell 
$(2) -dumpmachine)))
+   ifeq ($$($(1)_compiler_preferred_target),)
+$$(warning No output from '$(2) -dumpmachine')
+$$(warning Check that the compiler is in your PATH and CROSS_COMPILE is)
+$$(warning set correctly.)
+$$(error Unable to run compiler '$(2)')
+   endif
++  $$(warning $(1) $(2))
+   ifneq ($$(filter %-w64-mingw32,$$($(1)_compiler_preferred_target)),)
+# Use the compiler target name.
+   else
+@@ -64,6 +65,15 @@ define calculate-compiler-preferred-target
+ifneq ($$(filter arm-linux-android,$$($(1)_compiler_preferred_target)),)
+ $(1)_compiler_preferred_target := arm-linux-androideabi
+endif
++  ifneq ($$(filter aarch64-%,$$($(1)_compiler_preferred_target)),)
++   $(1)_compiler_preferred_target := aarch64-linux-gnu
++  endif
++  ifneq ($$(filter arm-%-gnueabi armv7a-cros-linux-gnueabi 
armv7hl-redhat-linux-gnueabi,$$($(1)_compiler_preferred_target)),)
++   $(1)_compiler_preferred_target := arm-linux-gnueabi
++  endif
++  ifneq ($$(filter arm-%-gnueabihf,$$($(1)_compiler_preferred_target)),)
++   $(1)_compiler_preferred_target := arm-linux-gnueabihf
++  endif
+ifneq ($$(filter clang%,$(2)),)
+ ifeq ($(1),target)
+  ifeq (arm-linux-gnueabihf,$$(CROSS_TRIPLE))
+-- 
+2.7.4
+
diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb 
b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
index fcf35ed..0cd2f42 100644
--- a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
+++ b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
@@ -17,7 +17,9 @@ PROVIDES = "virtual/gpudriver"
 
 BRANCH = "linuxws/thud/k4.19/${PV}"
 
-SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-driver.git;branch=${BRANCH}"
+SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-driver.git;branch=${BRANCH} \
+file://0001-km-support-general-toolchain.patch \
+"
 S = "${WORKDIR}/git"
 
 SRCREV = "1531b98ba602911359bfded2d683e49b3c731313"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 1/4] jailhouse: ensure INITRAMFS_IMAGE is initialized, pass full CC var

2019-09-11 Thread Denys Dmytriyenko
* If both INITRAMFS_IMAGE and JH_RAMFS_IMAGE are unset, variables fail to
  expand, which leads to dependency errors.
* Passing full CC variable ensure all options are specified, especially
  --sysroot one for internal toolchains.

Signed-off-by: Denys Dmytriyenko 
---
 recipes-kernel/jailhouse/jailhouse_git.bb | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
b/recipes-kernel/jailhouse/jailhouse_git.bb
index 0b52ecb..32aecf8 100644
--- a/recipes-kernel/jailhouse/jailhouse_git.bb
+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
@@ -58,6 +58,7 @@ JH_SYSCONFIG_CELL ?= ""
 JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
 JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
 
+INITRAMFS_IMAGE ?= ""
 JH_RAMFS_IMAGE ?= "${INITRAMFS_IMAGE}"
 
 JH_CMDLINE ?= ""
@@ -78,10 +79,8 @@ USER_SPACE_CFLAGS = '${CFLAGS} 
-DLIBEXECDIR=\\\"${libexecdir}\\\" \
 -I../driver'
 
 TOOLS_SRC_DIR = "${S}/tools"
-TOOLS_OBJ_DIR = "${S}/tools"
-
-EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
KDIR=${STAGING_KERNEL_BUILDDIR}"
 
+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} CC="${CC}" 
KDIR=${STAGING_KERNEL_BUILDDIR}"
 
 do_compile() {
oe_runmake V=1
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 4/4] ti-gc320-libs: only compatible with DRA7xx platform

2019-09-11 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 9 +++--
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb 
b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
index df1a99e..e8c2f01 100644
--- a/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
+++ b/recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://git.ti.com/graphics/ti-gc320-libs";
 LICENSE = "TI-TSPA"
 LIC_FILES_CHKSUM = "file://Manifest.html;md5=a9121e8936ace09820d23f7626daaca5"
 
-PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_MACHINE = "dra7xx"
 
 CLEANBROKEN = "1"
 
@@ -24,9 +24,9 @@ python __anonymous() {
 raise bb.parse.SkipPackage("%s-%s ONLY supports hardfp mode for now" % 
(pkgn, pkgv))
 }
 
-TARGET_PRODUCT_omap-a15 = "jacinto6evm"
+TARGET_PRODUCT = "jacinto6evm"
 
-PR = "r2"
+PR = "r3"
 
 S = "${WORKDIR}/git"
 
@@ -38,6 +38,3 @@ do_install() {
 }
 
 INSANE_SKIP_${PN} += "ldflags"
-
-COMPATIBLE_HOST ?= "null"
-COMPATIBLE_HOST_ti-soc = "(.*)"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 3/4] ti-sgx-ddk-km: also support arm-oe-linux-gnueabi as a hardfp compiler

2019-09-11 Thread Denys Dmytriyenko
OE-built internal toolchain doesn't use "-gnueabihf" suffix and instead uses
"-gnueabi" for both softfp and hardfp.

For now we only support hardfp (user-space binaries are only available in
hardfp), but would be nice to check for "callconvention-hard" before applying
the patch.

Signed-off-by: Denys Dmytriyenko 
---
 ...OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch | 34 ++
 .../powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb  |  4 ++-
 2 files changed, 37 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch

diff --git 
a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch
 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch
new file mode 100644
index 000..071ce0c
--- /dev/null
+++ 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km/0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch
@@ -0,0 +1,34 @@
+From 755632b4f3a40996a12bc7816a9839af7112040a Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko 
+Date: Mon, 9 Sep 2019 17:05:48 -0400
+Subject: [PATCH] km: support OpenEmbedded hardfp toolchain w/o -gnueabihf
+ suffix
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ eurasia_km/eurasiacon/build/linux2/config/compiler.mk | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/eurasia_km/eurasiacon/build/linux2/config/compiler.mk 
b/eurasia_km/eurasiacon/build/linux2/config/compiler.mk
+index dead2f9..2ba3e5e 100644
+--- a/eurasia_km/eurasiacon/build/linux2/config/compiler.mk
 b/eurasia_km/eurasiacon/build/linux2/config/compiler.mk
+@@ -68,12 +68,12 @@ define calculate-compiler-preferred-target
+   ifneq ($$(filter aarch64-%,$$($(1)_compiler_preferred_target)),)
+$(1)_compiler_preferred_target := aarch64-linux-gnu
+   endif
++  ifneq ($$(filter arm-%-gnueabihf 
arm-oe-linux-gnueabi,$$($(1)_compiler_preferred_target)),)
++   $(1)_compiler_preferred_target := arm-linux-gnueabihf
++  endif
+   ifneq ($$(filter arm-%-gnueabi armv7a-cros-linux-gnueabi 
armv7hl-redhat-linux-gnueabi,$$($(1)_compiler_preferred_target)),)
+$(1)_compiler_preferred_target := arm-linux-gnueabi
+   endif
+-  ifneq ($$(filter arm-%-gnueabihf,$$($(1)_compiler_preferred_target)),)
+-   $(1)_compiler_preferred_target := arm-linux-gnueabihf
+-  endif
+  endif
+ endef
+ 
+-- 
+2.7.4
+
diff --git a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb 
b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
index 8338ed7..c8dbe4f 100644
--- a/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
+++ b/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
@@ -18,7 +18,9 @@ PROVIDES = "virtual/gpudriver"
 
 BRANCH = "ti-img-sgx/${PV}/k4.19"
 
-SRC_URI = 
"git://git.ti.com/graphics/omap5-sgx-ddk-linux.git;protocol=git;branch=${BRANCH}"
+SRC_URI = 
"git://git.ti.com/graphics/omap5-sgx-ddk-linux.git;protocol=git;branch=${BRANCH}
 \
+file://0001-km-support-OpenEmbedded-hardfp-toolchain-w-o-gnueabi.patch \
+"
 
 S = "${WORKDIR}/git"
 
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 4/5] ti-sgx-ddk-um: Drop omap5-sgx-ddk-um-linux package

2019-09-05 Thread Denys Dmytriyenko
Anand,

Nothing uses omap5-sgx-ddk-um-linux and hasn't been for few years now.

Those recipes you mention used ti-sgx-ddk-um dependency directly for some 
time, but were update earlier to depend on virtual egl and/or libgles 
providers.

Also, please mind the public mailing list. Thanks.

-- 
Denys


On Fri, Sep 06, 2019 at 01:03:40AM -0400, Balagopalakrishnan, Anand wrote:
>Andrew,
> 
>I remember some of the other recipes (eg kmscube, omapdrmtest) in meta-ti
>/ meta-arago that depended on omap5-sgx-ddk-um-linux.
> 
>We cleaned up some of those dependencies while adding J7. Not sure if all
>of them have been covered. Have you confirmed?
> 
>Regards,
> 
>Anand
> 
>  --
> 
>From: Davis, Andrew
>Sent: Thursday, September 5, 2019 10:08:46 PM
>To: Dmytriyenko, Denys; Tammana, Gowtham; Balagopalakrishnan, Anand; Ruei,
>Eric
>Cc: meta-ti@yoctoproject.org; Davis, Andrew
>Subject: [meta-ti][thud/master][PATCH 4/5] ti-sgx-ddk-um: Drop
>omap5-sgx-ddk-um-linux package
> 
>No one in-tree depends on this anymore. This used to be the name of the
>package so this was kept here for several years for backwards
>compatibility. Remove this from PROVIDES.
> 
>Signed-off-by: Andrew F. Davis 
>---
> .../libgles/ti-sgx-ddk-um_1.17.4948957.bb | 20 +--
> 1 file changed, 10 insertions(+), 10 deletions(-)
> 
>diff --git a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
>b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
>index 0695ca0a..53d2829e 100644
>--- a/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
>+++ b/recipes-graphics/libgles/ti-sgx-ddk-um_1.17.4948957.bb
>@@ -23,22 +23,22 @@ INITSCRIPT_PARAMS = "defaults 8"
> 
> inherit update-rc.d
> 
>-PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2 virtual/libgbm
>omap5-sgx-ddk-um-linux"
>+PROVIDES += "virtual/egl virtual/libgles1 virtual/libgles2
>virtual/libgbm"
> 
> DEPENDS += "libdrm udev wayland wayland-protocols libffi expat"
> RDEPENDS_${PN} += "libdrm libdrm-omap udev wayland wayland-protocols
>libffi expat"
> 
>-RPROVIDES_${PN} = "libegl libgles1 libgles2 libgbm
>omap5-sgx-ddk-um-linux"
>-RPROVIDES_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev
>omap5-sgx-ddk-um-linux-dev"
>-RPROVIDES_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg libgbm-dbg
>omap5-sgx-ddk-um-linux-dbg"
>+RPROVIDES_${PN} = "libegl libgles1 libgles2 libgbm"
>+RPROVIDES_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev"
>+RPROVIDES_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg libgbm-dbg"
> 
>-RREPLACES_${PN} = "libegl libgles1 libgles2 libgbm
>omap5-sgx-ddk-um-linux"
>-RREPLACES_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev
>omap5-sgx-ddk-um-linux-dev"
>-RREPLACES_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg libgbm-dbg
>omap5-sgx-ddk-um-linux-dbg"
>+RREPLACES_${PN} = "libegl libgles1 libgles2 libgbm"
>+RREPLACES_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev"
>+RREPLACES_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg libgbm-dbg"
> 
>-RCONFLICTS_${PN} = "libegl libgles1 libgles2 libgbm
>omap5-sgx-ddk-um-linux"
>-RCONFLICTS_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev
>omap5-sgx-ddk-um-linux-dev"
>-RCONFLICTS_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg libgbm-dbg
>omap5-sgx-ddk-um-linux-dbg"
>+RCONFLICTS_${PN} = "libegl libgles1 libgles2 libgbm"
>+RCONFLICTS_${PN}-dev = "libegl-dev libgles1-dev libgles2-dev libgbm-dev"
>+RCONFLICTS_${PN}-dbg = "libegl-dbg libgles1-dbg libgles2-dbg libgbm-dbg"
> 
> # The actual SONAME is libGLESv2.so.2, so need to explicitly specify
>RPROVIDES for .so.1 here
> RPROVIDES_${PN} += "libGLESv2.so.1"
>--
>2.17.1
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] cadence-mhdp-fw: update to 1.2.17

2019-09-05 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb 
b/recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb
index 38a1f82b..70c28671 100644
--- a/recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb
+++ b/recipes-bsp/cadence-mhdp-fw/cadence-mhdp-fw_git.bb
@@ -3,7 +3,7 @@ SUMMARY = "Cadence MHDP DP bridge firmware"
 LICENSE = "BSD-3-Clause | Apache-2.0"
 LIC_FILES_CHKSUM = 
"file://LICENCE.cadence;md5=009f46816f6956cfb75ede13d3e1cee0"
 
-PV = "1.2.15"
+PV = "1.2.17"
 PR = "r0"
 
 CLEANBROKEN = "1"
@@ -12,7 +12,7 @@ COMPATIBLE_MACHINE = "j7-evm"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
-SRCREV = "3930363562b35a5f3d495a61ea7e51739462b14a"
+SRCREV = "7bad9a69a343e01056ece5ce6da4d4060c42f6bc"
 BRANCH ?= "ti-linux-firmware"
 
 SRC_URI = 
"git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=${BRANCH}"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2] am65xx, j7-evm: add secondary serial console for Jailhouse

2019-08-30 Thread Denys Dmytriyenko
Perfect!
Merged everything to thud-next for testing, thanks!


On Fri, Aug 30, 2019 at 01:10:58PM -0400, Jacob Stiffler wrote:
> Signed-off-by: Jacob Stiffler 
> ---
> v2 changes:
> * update commit message
> * add SERIAL_CONSOLES_CHECK
> 
>  conf/machine/am65xx-evm.conf | 3 ++-
>  conf/machine/j7-evm.conf | 2 +-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
> index 27bb0b0..15bffde 100644
> --- a/conf/machine/am65xx-evm.conf
> +++ b/conf/machine/am65xx-evm.conf
> @@ -8,7 +8,8 @@ MACHINE_FEATURES += "touchscreen"
>  
>  IMAGE_FSTYPES += "tar.xz wic.xz"
>  
> -SERIAL_CONSOLES = "115200;ttyS2"
> +SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS1"
> +SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
>  
>  KERNEL_DEVICETREE = " \
>  ti/k3-am654-base-board.dtb ti/k3-am654-gp.dtbo \
> diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
> index ca594e8..7b11ba7 100644
> --- a/conf/machine/j7-evm.conf
> +++ b/conf/machine/j7-evm.conf
> @@ -6,7 +6,7 @@ require conf/machine/include/k3.inc
>  
>  IMAGE_FSTYPES += "tar.xz wic.xz"
>  
> -SERIAL_CONSOLES = "115200;ttyS2"
> +SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS1"
>  SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
>  
>  KERNEL_DEVICETREE = " \
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH] am65xx, j7-evm: add secondary serial console

2019-08-30 Thread Denys Dmytriyenko
Can you add "am65xx, j7-evm: add secondary serial console for Jailhouse"?


On Fri, Aug 30, 2019 at 01:00:42PM -0400, Jacob Stiffler wrote:
> Signed-off-by: Jacob Stiffler 
> ---
>  conf/machine/am65xx-evm.conf | 2 +-
>  conf/machine/j7-evm.conf | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
> index 27bb0b0..e4d5ee1 100644
> --- a/conf/machine/am65xx-evm.conf
> +++ b/conf/machine/am65xx-evm.conf
> @@ -8,7 +8,7 @@ MACHINE_FEATURES += "touchscreen"
>  
>  IMAGE_FSTYPES += "tar.xz wic.xz"
>  
> -SERIAL_CONSOLES = "115200;ttyS2"
> +SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS1"

This is helpful for SysVinit in case one of the devnodes is absent:

SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"


>  KERNEL_DEVICETREE = " \
>  ti/k3-am654-base-board.dtb ti/k3-am654-gp.dtbo \
> diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
> index ca594e8..7b11ba7 100644
> --- a/conf/machine/j7-evm.conf
> +++ b/conf/machine/j7-evm.conf
> @@ -6,7 +6,7 @@ require conf/machine/include/k3.inc
>  
>  IMAGE_FSTYPES += "tar.xz wic.xz"
>  
> -SERIAL_CONSOLES = "115200;ttyS2"
> +SERIAL_CONSOLES = "115200;ttyS2 115200;ttyS1"
>  SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
>  
>  KERNEL_DEVICETREE = " \
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo

2019-08-30 Thread Denys Dmytriyenko
On Fri, Aug 30, 2019 at 12:42:32PM -0400, Jacob Stiffler wrote:
> 
> On 8/30/2019 12:31 PM, Denys Dmytriyenko wrote:
> >On Fri, Aug 30, 2019 at 12:26:51PM -0400, Jacob Stiffler wrote:
> >>On 8/30/2019 12:23 PM, Denys Dmytriyenko wrote:
> >>>On Thu, Aug 29, 2019 at 02:21:51PM +0530, Nikhil Devshatwar wrote:
> >>>>On 20/08/19 11:41 PM, Jacob Stiffler wrote:
> >>>>>* Configure the linux-demo to use a ramfs for the linux inmate.
> >>>>>* Using JH_RAMFS_IMAGE, this can be set in some global conf.
> >>>>>
> >>>>>Signed-off-by: Jacob Stiffler 
> >>>>Tested-by: Nikhil Devshatwar 
> >>>>
> >>>>I manually built the core-image-minimal in cpio format with a bbappend of 
> >>>>my own.
> >>>>How is this supposed to be built automatically?
> >>>>
> >>>>Can you add a depends variable so that the build kicks automatically?
> >>>There's a proper DEPENDS being added in the anonymous function below, so
> >>>should work automatically.
> >>
> >>We do not have "cpio" in our IMAGE_TYPES, so it needs to be added for
> >>JH_RAMFS_IMAGE.
> >>
> >>I cannot think of a way to force that IMAGE_TYPE from this recipe, but is
> >>there a way?
> >No, the only way is to check that IMAGE_FSTYPES contains "cpio" when
> >JH_RAMFS_IMAGE is set and error out otherwise. Can be done in anonymous
> >function to bail out early and not wait until JH builds.
> >
> 
> But cpio can be added as a recipe override, so preemptively detecting this
> could get tricky.

All the overrides should be parsed and processed by the time anonymous 
functions are executed... Is there a specific use-case you have that doesn't 
work?


> >>>Denys
> >>>
> >>>
> >>>>Nikhil D
> >>>>
> >>>>>---
> >>>>>  recipes-kernel/jailhouse/jailhouse_git.bb | 21 +
> >>>>>  1 file changed, 17 insertions(+), 4 deletions(-)
> >>>>>
> >>>>>diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> >>>>>b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>>>>index 5d572d0..ba6772f 100644
> >>>>>--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >>>>>+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>>>>@@ -58,8 +58,10 @@ JH_SYSCONFIG_CELL ?= ""
> >>>>>  JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
> >>>>>  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
> >>>>>+JH_RAMFS_IMAGE ?= "core-image-minimal"
> >>>>>+
> >>>>>  JH_CMDLINE ?= ""
> >>>>>-JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> >>>>>rootfstype=ext4 rootwait"
> >>>>>+JH_CMDLINE_k3 ?= "console=ttyS1,115200n8"
> >>>>>  do_configure() {
> >>>>> if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ];
> >>>>>@@ -101,6 +103,16 @@ do_install() {
> >>>>> install -m 0644 ${B}/inmates/demos/${JH_ARCH}/*.bin 
> >>>>> ${D}${INMATES_DIR}
> >>>>> install -d ${D}/boot
> >>>>>+if [ -n "${JH_RAMFS_IMAGE}" ]
> >>>>>+then
> >>>>>+if [ -f 
> >>>>>${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> >>>>>+then
> >>>>>+install -m 0644 
> >>>>>${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> >>>>>+else
> >>>>>+bbwarn "Could find find JH_RAMFS_IMAGE 
> >>>>>(${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"
> >>>>>+bbwarn "Please make sure that \"cpio\" is in 
> >>>>>IMAGE_FSTYPES."
> >>>>>+fi
> >>>>>+fi
> >>>>> if [ -n "${JH_INMATE_DTB}" -a -n "${JH_LINUX_DEMO_CELL}" ]; then
> >>>>> cd ${TOOLS_SRC_DIR}
> >>>>>@@ -110,6 +122,7 @@ do_install() {
> >>>>> ./jailhouse-cell-linux -w 
> >>>>> ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
> >>>>> -a ${JH_ARCH} -c "${JH_CMDLINE}" \
> >>>>> -d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> >>>>>+-i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
> >>>>> ${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
> >>>>> ${DEPLOY_DIR_IMAGE}/Image \
> >>>>> | tr -cd '\11\12\15\40-\176' \
> >>>>>@@ -143,9 +156,9 @@ CELLS = ""
> >>>>>  python __anonymous () {
> >>>>>  d.appendVarFlag('do_install', 'depends', ' 
> >>>>> virtual/kernel:do_deploy')
> >>>>>-initrd = d.getVar('INITRAMFS_IMAGE', True)
> >>>>>-if initrd:
> >>>>>-d.appendVarFlag('do_install', 'depends', ' 
> >>>>>${INITRAMFS_IMAGE}:do_image_complete')
> >>>>>+ramfs = d.getVar('JH_RAMFS_IMAGE', True)
> >>>>>+if ramfs:
> >>>>>+d.appendVarFlag('do_install', 'depends', ' 
> >>>>>${JH_RAMFS_IMAGE}:do_image_complete')
> >>>>>  # Setup DEPENDS and RDEPENDS to included cells
> >>>>>  cells = d.getVar('CELLS', True) or ""
> >>>>>
> >>>>-- 
> >>>>___
> >>>>meta-ti mailing list
> >>>>meta-ti@yoctoproject.org
> >>>>https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo

2019-08-30 Thread Denys Dmytriyenko
On Fri, Aug 30, 2019 at 12:26:51PM -0400, Jacob Stiffler wrote:
> 
> On 8/30/2019 12:23 PM, Denys Dmytriyenko wrote:
> >On Thu, Aug 29, 2019 at 02:21:51PM +0530, Nikhil Devshatwar wrote:
> >>On 20/08/19 11:41 PM, Jacob Stiffler wrote:
> >>>* Configure the linux-demo to use a ramfs for the linux inmate.
> >>>* Using JH_RAMFS_IMAGE, this can be set in some global conf.
> >>>
> >>>Signed-off-by: Jacob Stiffler 
> >>Tested-by: Nikhil Devshatwar 
> >>
> >>I manually built the core-image-minimal in cpio format with a bbappend of 
> >>my own.
> >>How is this supposed to be built automatically?
> >>
> >>Can you add a depends variable so that the build kicks automatically?
> >There's a proper DEPENDS being added in the anonymous function below, so
> >should work automatically.
> 
> 
> We do not have "cpio" in our IMAGE_TYPES, so it needs to be added for
> JH_RAMFS_IMAGE.
> 
> I cannot think of a way to force that IMAGE_TYPE from this recipe, but is
> there a way?

No, the only way is to check that IMAGE_FSTYPES contains "cpio" when 
JH_RAMFS_IMAGE is set and error out otherwise. Can be done in anonymous 
function to bail out early and not wait until JH builds.


> >Denys
> >
> >
> >>Nikhil D
> >>
> >>>---
> >>>  recipes-kernel/jailhouse/jailhouse_git.bb | 21 +
> >>>  1 file changed, 17 insertions(+), 4 deletions(-)
> >>>
> >>>diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> >>>b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>>index 5d572d0..ba6772f 100644
> >>>--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >>>+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>>@@ -58,8 +58,10 @@ JH_SYSCONFIG_CELL ?= ""
> >>>  JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
> >>>  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
> >>>+JH_RAMFS_IMAGE ?= "core-image-minimal"
> >>>+
> >>>  JH_CMDLINE ?= ""
> >>>-JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> >>>rootfstype=ext4 rootwait"
> >>>+JH_CMDLINE_k3 ?= "console=ttyS1,115200n8"
> >>>  do_configure() {
> >>>   if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ];
> >>>@@ -101,6 +103,16 @@ do_install() {
> >>>   install -m 0644 ${B}/inmates/demos/${JH_ARCH}/*.bin ${D}${INMATES_DIR}
> >>>   install -d ${D}/boot
> >>>+  if [ -n "${JH_RAMFS_IMAGE}" ]
> >>>+  then
> >>>+  if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> >>>+  then
> >>>+  install -m 0644 
> >>>${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> >>>+  else
> >>>+  bbwarn "Could find find JH_RAMFS_IMAGE 
> >>>(${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"
> >>>+  bbwarn "Please make sure that \"cpio\" is in 
> >>>IMAGE_FSTYPES."
> >>>+  fi
> >>>+  fi
> >>>   if [ -n "${JH_INMATE_DTB}" -a -n "${JH_LINUX_DEMO_CELL}" ]; then
> >>>   cd ${TOOLS_SRC_DIR}
> >>>@@ -110,6 +122,7 @@ do_install() {
> >>>   ./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
> >>>   -a ${JH_ARCH} -c "${JH_CMDLINE}" \
> >>>   -d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> >>>+  -i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
> >>>   ${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
> >>>   ${DEPLOY_DIR_IMAGE}/Image \
> >>>   | tr -cd '\11\12\15\40-\176' \
> >>>@@ -143,9 +156,9 @@ CELLS = ""
> >>>  python __anonymous () {
> >>>  d.appendVarFlag('do_install', 'depends', ' virtual/kernel:do_deploy')
> >>>-initrd = d.getVar('INITRAMFS_IMAGE', True)
> >>>-if initrd:
> >>>-d.appendVarFlag('do_install', 'depends', ' 
> >>>${INITRAMFS_IMAGE}:do_image_complete')
> >>>+ramfs = d.getVar('JH_RAMFS_IMAGE', True)
> >>>+if ramfs:
> >>>+d.appendVarFlag('do_install', 'depends', ' 
> >>>${JH_RAMFS_IMAGE}:do_image_complete')
> >>>  # Setup DEPENDS and RDEPENDS to included cells
> >>>  cells = d.getVar('CELLS', True) or ""
> >>>
> >>-- 
> >>___
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo

2019-08-30 Thread Denys Dmytriyenko
On Fri, Aug 30, 2019 at 12:23:43PM -0400, Jacob Stiffler wrote:
> 
> On 8/30/2019 12:13 PM, Denys Dmytriyenko wrote:
> >On Tue, Aug 20, 2019 at 02:11:12PM -0400, Jacob Stiffler wrote:
> >>* Configure the linux-demo to use a ramfs for the linux inmate.
> >>* Using JH_RAMFS_IMAGE, this can be set in some global conf.
> >>
> >>Signed-off-by: Jacob Stiffler 
> >>---
> >>  recipes-kernel/jailhouse/jailhouse_git.bb | 21 +
> >>  1 file changed, 17 insertions(+), 4 deletions(-)
> >>
> >>diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> >>b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>index 5d572d0..ba6772f 100644
> >>--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >>+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>@@ -58,8 +58,10 @@ JH_SYSCONFIG_CELL ?= ""
> >>  JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
> >>  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
> >>+JH_RAMFS_IMAGE ?= "core-image-minimal"
> >Ok, after thinking about it a bit, I will agree to JH_RAMFS_IMAGE variable,
> >but I don't want to loose the default INITRAMFS_IMAGE usage. So, how about
> >changing the default here to something like this:
> >
> >JH_RAMFS_IMAGE ?= "${INITRAMFS_IMAGE}"
> >
> >That way either of the variables can be set my machine config or local.conf
> >and the default use is also preserved. Thoughts?
> 
> 
> I like that idea better as well.
> 
> 
> >
> >>  JH_CMDLINE ?= ""
> >>-JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> >>rootfstype=ext4 rootwait"
> >>+JH_CMDLINE_k3 ?= "console=ttyS1,115200n8"
> >>  do_configure() {
> >>if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ];
> >>@@ -101,6 +103,16 @@ do_install() {
> >>install -m 0644 ${B}/inmates/demos/${JH_ARCH}/*.bin ${D}${INMATES_DIR}
> >>install -d ${D}/boot
> >>+   if [ -n "${JH_RAMFS_IMAGE}" ]
> >>+   then
> >>+   if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> >>+   then
> >>+   install -m 0644 
> >>${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> >>+   else
> >>+   bbwarn "Could find find JH_RAMFS_IMAGE 
> >>(${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"
> >Typo in the message. Also, should it be an error instead of a warning?
> 
> 
> I did not want this recipe to force the requirement for an ramfs. But
> thinking about it now, making it an error is better in case the linux-demo
> is desired. If it is not, then JH_RAMFS_IMAGE can be unset in some conf.

Thanks. Can you do a v4 of all 3 patches quickly to address the comments in 
1/3 and 3/3, so I can merge them in for rc4? Thanks again.


> >>+   bbwarn "Please make sure that \"cpio\" is in 
> >>IMAGE_FSTYPES."
> >>+   fi
> >>+   fi
> >>if [ -n "${JH_INMATE_DTB}" -a -n "${JH_LINUX_DEMO_CELL}" ]; then
> >>cd ${TOOLS_SRC_DIR}
> >>@@ -110,6 +122,7 @@ do_install() {
> >>./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
> >>-a ${JH_ARCH} -c "${JH_CMDLINE}" \
> >>-d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> >>+   -i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
> >>${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
> >>${DEPLOY_DIR_IMAGE}/Image \
> >>| tr -cd '\11\12\15\40-\176' \
> >>@@ -143,9 +156,9 @@ CELLS = ""
> >>  python __anonymous () {
> >>  d.appendVarFlag('do_install', 'depends', ' virtual/kernel:do_deploy')
> >>-initrd = d.getVar('INITRAMFS_IMAGE', True)
> >>-if initrd:
> >>-d.appendVarFlag('do_install', 'depends', ' 
> >>${INITRAMFS_IMAGE}:do_image_complete')
> >>+ramfs = d.getVar('JH_RAMFS_IMAGE', True)
> >>+if ramfs:
> >>+d.appendVarFlag('do_install', 'depends', ' 
> >>${JH_RAMFS_IMAGE}:do_image_complete')
> >>  # Setup DEPENDS and RDEPENDS to included cells
> >>  cells = d.getVar('CELLS', True) or ""
> >>-- 
> >>2.7.4
> >>
> >>-- 
> >>___
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo

2019-08-30 Thread Denys Dmytriyenko
On Thu, Aug 29, 2019 at 02:21:51PM +0530, Nikhil Devshatwar wrote:
> On 20/08/19 11:41 PM, Jacob Stiffler wrote:
> >* Configure the linux-demo to use a ramfs for the linux inmate.
> >* Using JH_RAMFS_IMAGE, this can be set in some global conf.
> >
> >Signed-off-by: Jacob Stiffler 
> 
> Tested-by: Nikhil Devshatwar 
> 
> I manually built the core-image-minimal in cpio format with a bbappend of my 
> own.
> How is this supposed to be built automatically?
> 
> Can you add a depends variable so that the build kicks automatically?

There's a proper DEPENDS being added in the anonymous function below, so 
should work automatically.

Denys


> Nikhil D
> 
> >---
> >  recipes-kernel/jailhouse/jailhouse_git.bb | 21 +
> >  1 file changed, 17 insertions(+), 4 deletions(-)
> >
> >diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> >b/recipes-kernel/jailhouse/jailhouse_git.bb
> >index 5d572d0..ba6772f 100644
> >--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >@@ -58,8 +58,10 @@ JH_SYSCONFIG_CELL ?= ""
> >  JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
> >  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
> >+JH_RAMFS_IMAGE ?= "core-image-minimal"
> >+
> >  JH_CMDLINE ?= ""
> >-JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> >rootfstype=ext4 rootwait"
> >+JH_CMDLINE_k3 ?= "console=ttyS1,115200n8"
> >  do_configure() {
> > if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ];
> >@@ -101,6 +103,16 @@ do_install() {
> > install -m 0644 ${B}/inmates/demos/${JH_ARCH}/*.bin ${D}${INMATES_DIR}
> > install -d ${D}/boot
> >+if [ -n "${JH_RAMFS_IMAGE}" ]
> >+then
> >+if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> >+then
> >+install -m 0644 
> >${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> >+else
> >+bbwarn "Could find find JH_RAMFS_IMAGE 
> >(${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"
> >+bbwarn "Please make sure that \"cpio\" is in 
> >IMAGE_FSTYPES."
> >+fi
> >+fi
> > if [ -n "${JH_INMATE_DTB}" -a -n "${JH_LINUX_DEMO_CELL}" ]; then
> > cd ${TOOLS_SRC_DIR}
> >@@ -110,6 +122,7 @@ do_install() {
> > ./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
> > -a ${JH_ARCH} -c "${JH_CMDLINE}" \
> > -d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> >+-i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
> > ${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
> > ${DEPLOY_DIR_IMAGE}/Image \
> > | tr -cd '\11\12\15\40-\176' \
> >@@ -143,9 +156,9 @@ CELLS = ""
> >  python __anonymous () {
> >  d.appendVarFlag('do_install', 'depends', ' virtual/kernel:do_deploy')
> >-initrd = d.getVar('INITRAMFS_IMAGE', True)
> >-if initrd:
> >-d.appendVarFlag('do_install', 'depends', ' 
> >${INITRAMFS_IMAGE}:do_image_complete')
> >+ramfs = d.getVar('JH_RAMFS_IMAGE', True)
> >+if ramfs:
> >+d.appendVarFlag('do_install', 'depends', ' 
> >${JH_RAMFS_IMAGE}:do_image_complete')
> >  # Setup DEPENDS and RDEPENDS to included cells
> >  cells = d.getVar('CELLS', True) or ""
> >
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 2/3] jailhouse: provide tools package

2019-08-30 Thread Denys Dmytriyenko
On Fri, Aug 30, 2019 at 12:10:53PM -0400, Jacob Stiffler wrote:
> 
> On 8/30/2019 12:03 PM, Denys Dmytriyenko wrote:
> >On Tue, Aug 20, 2019 at 02:11:11PM -0400, Jacob Stiffler wrote:
> >>Create a package containing the jailhouse tools which are used to work
> >>with the cells and inmates. This recipe provides a good example for
> >Should it be s/recipe/package/ here ^^^?
> 
> 
> I did mean recipe as the do_install task show an usage example.

Ah, Ok, now I see what you mean.


> >>using the jailhouse-cell-linux tool.
> >>
> >>The tools require the pyjailhouse python modules, so package them as
> >>well.
> >Any specific reason to package into own "pyjailhouse" package instead of
> >bundling with ${PN}-tools, as it's the only consumer now?
> 
> 
> It just seemed logical to me. pyjailhouse appears to be a proper python
> module, so I kept it separate.

Thanks.


> >>Signed-off-by: Jacob Stiffler 
> >>---
> >>  recipes-kernel/jailhouse/jailhouse_git.bb | 24 
> >>  1 file changed, 20 insertions(+), 4 deletions(-)
> >>
> >>diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> >>b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>index d637d51..5d572d0 100644
> >>--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >>+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >>@@ -29,7 +29,7 @@ RDEPENDS_${PN} += "\
> >>  S = "${WORKDIR}/git"
> >>  require jailhouse-arch.inc
> >>-inherit module pythonnative bash-completion deploy
> >>+inherit module pythonnative bash-completion deploy setuptools
> >>  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >>  COMPATIBLE_MACHINE = "(ti-soc)"
> >>@@ -78,12 +78,21 @@ USER_SPACE_CFLAGS = '${CFLAGS} 
> >>-DLIBEXECDIR=\\\"${libexecdir}\\\" \
> >>  TOOLS_SRC_DIR = "${S}/tools"
> >>  TOOLS_OBJ_DIR = "${S}/tools"
> >>+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> >>KDIR=${STAGING_KERNEL_BUILDDIR}"
> >>+
> >>+
> >>  do_compile() {
> >>-   oe_runmake V=1 ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> >>KDIR=${STAGING_KERNEL_BUILDDIR}
> >>+   oe_runmake V=1
> >>  }
> >>  do_install() {
> >>-   oe_runmake ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> >>KDIR=${STAGING_KERNEL_BUILDDIR} DESTDIR=${D} install
> >>+   # Install pyjailhouse python modules needed by the tools
> >>+   distutils_do_install
> >>+
> >>+   # We want to install the python tools, but we do not want to use pip...
> >>+   # At least with v0.10, we can work around this with
> >>+   # 'PIP=":" PYTHON_PIP_USEABLE=yes'
> >>+   oe_runmake PIP=: PYTHON_PIP_USEABLE=yes DESTDIR=${D} install
> >>install -d ${D}${CELL_DIR}
> >>install -m 0644 ${B}/configs/${JH_ARCH}/${JH_CELL_FILES} 
> >> ${D}${CELL_DIR}/
> >>@@ -115,8 +124,15 @@ do_install() {
> >>fi
> >>  }
> >>-PACKAGE_BEFORE_PN = "kernel-module-jailhouse"
> >>+PACKAGE_BEFORE_PN = "kernel-module-jailhouse pyjailhouse ${PN}-tools"
> >>  FILES_${PN} = "${base_libdir}/firmware ${libexecdir} ${sbindir} 
> >> ${JH_DATADIR} /boot"
> >>+FILES_pyjailhouse = "${PYTHON_SITEPACKAGES_DIR}"
> >>+FILES_${PN}-tools = "${libexecdir}/${BPN}/${BPN}-*"
> >>+
> >>+RDEPENDS_${PN}-tools = "pyjailhouse python-mmap python-math 
> >>python-argparse python-datetime python-curses python-compression"
> >>+RDEPENDS_pyjailhouse = "python-core python-ctypes python-fcntl 
> >>python-shell"
> >>+
> >>+RRECCOMMENDS_${PN} = "${PN}-tools"
> >>  INSANE_SKIP_${PN} = "ldflags"
> >>-- 
> >>2.7.4
> >>
> >>-- 
> >>___
> >>meta-ti mailing list
> >>meta-ti@yoctoproject.org
> >>https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 3/3] jailhouse: use ramfs for linux-demo

2019-08-30 Thread Denys Dmytriyenko
On Tue, Aug 20, 2019 at 02:11:12PM -0400, Jacob Stiffler wrote:
> * Configure the linux-demo to use a ramfs for the linux inmate.
> * Using JH_RAMFS_IMAGE, this can be set in some global conf.
> 
> Signed-off-by: Jacob Stiffler 
> ---
>  recipes-kernel/jailhouse/jailhouse_git.bb | 21 +
>  1 file changed, 17 insertions(+), 4 deletions(-)
> 
> diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> b/recipes-kernel/jailhouse/jailhouse_git.bb
> index 5d572d0..ba6772f 100644
> --- a/recipes-kernel/jailhouse/jailhouse_git.bb
> +++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> @@ -58,8 +58,10 @@ JH_SYSCONFIG_CELL ?= ""
>  JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
>  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
>  
> +JH_RAMFS_IMAGE ?= "core-image-minimal"

Ok, after thinking about it a bit, I will agree to JH_RAMFS_IMAGE variable, 
but I don't want to loose the default INITRAMFS_IMAGE usage. So, how about 
changing the default here to something like this:

JH_RAMFS_IMAGE ?= "${INITRAMFS_IMAGE}"

That way either of the variables can be set my machine config or local.conf 
and the default use is also preserved. Thoughts?


>  JH_CMDLINE ?= ""
> -JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext4 rootwait"
> +JH_CMDLINE_k3 ?= "console=ttyS1,115200n8"
>  
>  do_configure() {
>   if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ]; 
> @@ -101,6 +103,16 @@ do_install() {
>   install -m 0644 ${B}/inmates/demos/${JH_ARCH}/*.bin ${D}${INMATES_DIR}
>  
>   install -d ${D}/boot
> + if [ -n "${JH_RAMFS_IMAGE}" ]
> + then
> + if [ -f ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ]
> + then
> + install -m 0644 
> ${DEPLOY_DIR_IMAGE}/${JH_RAMFS_IMAGE}-${MACHINE}.cpio ${D}/boot
> + else
> + bbwarn "Could find find JH_RAMFS_IMAGE 
> (${JH_RAMFS_IMAGE}-${MACHINE}.cpio)!"

Typo in the message. Also, should it be an error instead of a warning?


> + bbwarn "Please make sure that \"cpio\" is in 
> IMAGE_FSTYPES."
> + fi
> + fi
>  
>   if [ -n "${JH_INMATE_DTB}" -a -n "${JH_LINUX_DEMO_CELL}" ]; then
>   cd ${TOOLS_SRC_DIR}
> @@ -110,6 +122,7 @@ do_install() {
>   ./jailhouse-cell-linux -w ${D}${JH_DATADIR}/${JH_INMATE_DTB} \
>   -a ${JH_ARCH} -c "${JH_CMDLINE}" \
>   -d ../configs/${JH_ARCH}/dts/${JH_INMATE_DTB} \
> + -i ${D}/boot/${JH_RAMFS_IMAGE}-${MACHINE}.cpio \
>   ${D}${CELL_DIR}/${JH_LINUX_DEMO_CELL} \
>   ${DEPLOY_DIR_IMAGE}/Image \
>   | tr -cd '\11\12\15\40-\176' \
> @@ -143,9 +156,9 @@ CELLS = ""
>  
>  python __anonymous () {
>  d.appendVarFlag('do_install', 'depends', ' virtual/kernel:do_deploy')
> -initrd = d.getVar('INITRAMFS_IMAGE', True)
> -if initrd:
> -d.appendVarFlag('do_install', 'depends', ' 
> ${INITRAMFS_IMAGE}:do_image_complete')
> +ramfs = d.getVar('JH_RAMFS_IMAGE', True)
> +if ramfs:
> +d.appendVarFlag('do_install', 'depends', ' 
> ${JH_RAMFS_IMAGE}:do_image_complete')
>  
>  # Setup DEPENDS and RDEPENDS to included cells
>  cells = d.getVar('CELLS', True) or ""
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 2/3] jailhouse: provide tools package

2019-08-30 Thread Denys Dmytriyenko
On Thu, Aug 29, 2019 at 02:11:30PM +0530, Nikhil Devshatwar wrote:
> On 20/08/19 11:41 PM, Jacob Stiffler wrote:
> >Create a package containing the jailhouse tools which are used to work
> >with the cells and inmates. This recipe provides a good example for
> >using the jailhouse-cell-linux tool.
> >
> >The tools require the pyjailhouse python modules, so package them as
> >well.
> >
> >Signed-off-by: Jacob Stiffler 
> 
> 
> Tested-by: Nikhil Devshatwar 
> 
> I had to specifically install the pyjailhouse IPK for pyjailhouse.
> You can add this in the meta-arago packagegroup recipe

Shouldn't be necessary, as jailhouse-tools RDEPENDS on pyjailhouse. So 
pyjailhouse should be installed automatically when jailhouse-tools gets 
installed.

Denys


> Nikhil D
> 
> >---
> >  recipes-kernel/jailhouse/jailhouse_git.bb | 24 
> >  1 file changed, 20 insertions(+), 4 deletions(-)
> >
> >diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> >b/recipes-kernel/jailhouse/jailhouse_git.bb
> >index d637d51..5d572d0 100644
> >--- a/recipes-kernel/jailhouse/jailhouse_git.bb
> >+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> >@@ -29,7 +29,7 @@ RDEPENDS_${PN} += "\
> >  S = "${WORKDIR}/git"
> >  require jailhouse-arch.inc
> >-inherit module pythonnative bash-completion deploy
> >+inherit module pythonnative bash-completion deploy setuptools
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >  COMPATIBLE_MACHINE = "(ti-soc)"
> >@@ -78,12 +78,21 @@ USER_SPACE_CFLAGS = '${CFLAGS} 
> >-DLIBEXECDIR=\\\"${libexecdir}\\\" \
> >  TOOLS_SRC_DIR = "${S}/tools"
> >  TOOLS_OBJ_DIR = "${S}/tools"
> >+EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> >KDIR=${STAGING_KERNEL_BUILDDIR}"
> >+
> >+
> >  do_compile() {
> >-oe_runmake V=1 ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> >KDIR=${STAGING_KERNEL_BUILDDIR}
> >+oe_runmake V=1
> >  }
> >  do_install() {
> >-oe_runmake ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> >KDIR=${STAGING_KERNEL_BUILDDIR} DESTDIR=${D} install
> >+# Install pyjailhouse python modules needed by the tools
> >+distutils_do_install
> >+
> >+# We want to install the python tools, but we do not want to use pip...
> >+# At least with v0.10, we can work around this with
> >+# 'PIP=":" PYTHON_PIP_USEABLE=yes'
> >+oe_runmake PIP=: PYTHON_PIP_USEABLE=yes DESTDIR=${D} install
> > install -d ${D}${CELL_DIR}
> > install -m 0644 ${B}/configs/${JH_ARCH}/${JH_CELL_FILES} 
> > ${D}${CELL_DIR}/
> >@@ -115,8 +124,15 @@ do_install() {
> > fi
> >  }
> >-PACKAGE_BEFORE_PN = "kernel-module-jailhouse"
> >+PACKAGE_BEFORE_PN = "kernel-module-jailhouse pyjailhouse ${PN}-tools"
> >  FILES_${PN} = "${base_libdir}/firmware ${libexecdir} ${sbindir} 
> > ${JH_DATADIR} /boot"
> >+FILES_pyjailhouse = "${PYTHON_SITEPACKAGES_DIR}"
> >+FILES_${PN}-tools = "${libexecdir}/${BPN}/${BPN}-*"
> >+
> >+RDEPENDS_${PN}-tools = "pyjailhouse python-mmap python-math python-argparse 
> >python-datetime python-curses python-compression"
> >+RDEPENDS_pyjailhouse = "python-core python-ctypes python-fcntl python-shell"
> >+
> >+RRECCOMMENDS_${PN} = "${PN}-tools"
> >  INSANE_SKIP_${PN} = "ldflags"
> >
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 2/3] jailhouse: provide tools package

2019-08-30 Thread Denys Dmytriyenko
On Tue, Aug 20, 2019 at 02:11:11PM -0400, Jacob Stiffler wrote:
> Create a package containing the jailhouse tools which are used to work
> with the cells and inmates. This recipe provides a good example for

Should it be s/recipe/package/ here ^^^?


> using the jailhouse-cell-linux tool.
> 
> The tools require the pyjailhouse python modules, so package them as
> well.

Any specific reason to package into own "pyjailhouse" package instead of 
bundling with ${PN}-tools, as it's the only consumer now?


> Signed-off-by: Jacob Stiffler 
> ---
>  recipes-kernel/jailhouse/jailhouse_git.bb | 24 
>  1 file changed, 20 insertions(+), 4 deletions(-)
> 
> diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> b/recipes-kernel/jailhouse/jailhouse_git.bb
> index d637d51..5d572d0 100644
> --- a/recipes-kernel/jailhouse/jailhouse_git.bb
> +++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> @@ -29,7 +29,7 @@ RDEPENDS_${PN} += "\
>  S = "${WORKDIR}/git"
>  
>  require jailhouse-arch.inc
> -inherit module pythonnative bash-completion deploy
> +inherit module pythonnative bash-completion deploy setuptools
>  
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  COMPATIBLE_MACHINE = "(ti-soc)"
> @@ -78,12 +78,21 @@ USER_SPACE_CFLAGS = '${CFLAGS} 
> -DLIBEXECDIR=\\\"${libexecdir}\\\" \
>  TOOLS_SRC_DIR = "${S}/tools"
>  TOOLS_OBJ_DIR = "${S}/tools"
>  
> +EXTRA_OEMAKE = "ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> KDIR=${STAGING_KERNEL_BUILDDIR}"
> +
> +
>  do_compile() {
> - oe_runmake V=1 ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> KDIR=${STAGING_KERNEL_BUILDDIR}
> + oe_runmake V=1
>  }
>  
>  do_install() {
> - oe_runmake ARCH=${JH_ARCH} CROSS_COMPILE=${TARGET_PREFIX} 
> KDIR=${STAGING_KERNEL_BUILDDIR} DESTDIR=${D} install
> + # Install pyjailhouse python modules needed by the tools
> + distutils_do_install
> +
> + # We want to install the python tools, but we do not want to use pip...
> + # At least with v0.10, we can work around this with
> + # 'PIP=":" PYTHON_PIP_USEABLE=yes'
> + oe_runmake PIP=: PYTHON_PIP_USEABLE=yes DESTDIR=${D} install
>  
>   install -d ${D}${CELL_DIR}
>   install -m 0644 ${B}/configs/${JH_ARCH}/${JH_CELL_FILES} 
> ${D}${CELL_DIR}/
> @@ -115,8 +124,15 @@ do_install() {
>   fi
>  }
>  
> -PACKAGE_BEFORE_PN = "kernel-module-jailhouse"
> +PACKAGE_BEFORE_PN = "kernel-module-jailhouse pyjailhouse ${PN}-tools"
>  FILES_${PN} = "${base_libdir}/firmware ${libexecdir} ${sbindir} 
> ${JH_DATADIR} /boot"
> +FILES_pyjailhouse = "${PYTHON_SITEPACKAGES_DIR}"
> +FILES_${PN}-tools = "${libexecdir}/${BPN}/${BPN}-*"
> +
> +RDEPENDS_${PN}-tools = "pyjailhouse python-mmap python-math python-argparse 
> python-datetime python-curses python-compression"
> +RDEPENDS_pyjailhouse = "python-core python-ctypes python-fcntl python-shell"
> +
> +RRECCOMMENDS_${PN} = "${PN}-tools"
>  
>  INSANE_SKIP_${PN} = "ldflags"
>  
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH v2 1/3] jailhouse: update to ti2019.03-rc2

2019-08-30 Thread Denys Dmytriyenko
This won't apply, as v1 was already merged prior to v2:
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/commit/?h=thud&id=ee2665f793d3280b67e82bc4fba4b538a9647912

Moreover, can you update to ti2019.03-rc4 tag - there were several commits 
since rc2:
http://git.ti.com/gitweb/?p=jailhouse/ti-jailhouse.git;a=shortlog;h=refs/heads/ti-jailhouse-0.10

Thanks.

Denys


On Tue, Aug 20, 2019 at 02:11:10PM -0400, Jacob Stiffler wrote:
> * extend to am65xx family
> * and correct am65xx cell and inmate filenames.
> * remove earlycon bootargs for am65xx
> 
> Signed-off-by: Jacob Stiffler 
> ---
> v2 changes:
> * Remove earlycon args for all k3
> 
>  recipes-kernel/jailhouse/jailhouse_git.bb | 10 +-
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> b/recipes-kernel/jailhouse/jailhouse_git.bb
> index 5e2c71b..d637d51 100644
> --- a/recipes-kernel/jailhouse/jailhouse_git.bb
> +++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = " \
>  "
>  
>  PV = "0.10+git${SRCPV}"
> -SRCREV = "e71fd2dc7e8494a44cc3c762a24824532a412807"
> +SRCREV = "96329f098e655cd42d7d0dbb3cd2cc7c3492d633"
>  BRANCH = "ti-jailhouse-0.10"
>  
>  SRC_URI = " \
> @@ -47,19 +47,19 @@ JH_CELL_FILES ?= "*.cell"
>  JH_CELL_FILES_k3 ?= "k3-*.cell"
>  
>  JH_INMATE_DTB ?= ""
> -JH_INMATE_DTB_am65xx-evm ?= "inmate-k3-am654.dtb"
> +JH_INMATE_DTB_am65xx ?= "inmate-k3-am654-idk.dtb"
>  JH_INMATE_DTB_j7-evm ?= "inmate-k3-j721e-evm.dtb"
>  
>  JH_LINUX_DEMO_CELL ?= ""
> -JH_LINUX_DEMO_CELL_am65xx-evm ?= "k3-am654-linux-demo.cell"
> +JH_LINUX_DEMO_CELL_am65xx ?= "k3-am654-idk-linux-demo.cell"
>  JH_LINUX_DEMO_CELL_j7-evm ?= "k3-j721e-evm-linux-demo.cell"
>  
>  JH_SYSCONFIG_CELL ?= ""
> -JH_SYSCONFIG_CELL_am65xx-evm ?= "k3-am654.cell"
> +JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
>  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
>  
>  JH_CMDLINE ?= ""
> -JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext4 rootwait earlycon=ns16550a,mmio32,0x281"
> +JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext4 rootwait"
>  
>  do_configure() {
>   if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ]; 
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH v2 1/2] conf/machine: update with new DTBs/DTBOs

2019-08-19 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
v2 - fix missing .dtb suffix in sancloud-bbe

 conf/machine/am65xx-evm.conf   | 1 +
 conf/machine/include/ti33x.inc | 3 ++-
 conf/machine/j7-evm.conf   | 4 ++--
 3 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
index 83eae598..27bb0b06 100644
--- a/conf/machine/am65xx-evm.conf
+++ b/conf/machine/am65xx-evm.conf
@@ -16,6 +16,7 @@ KERNEL_DEVICETREE = " \
 ti/k3-am654-evm-csi2-ov490.dtbo ti/k3-am654-evm-csi2-ov5640.dtbo \
 ti/k3-am654-evm-oldi-lcd1evm.dtbo ti/k3-am654-evm-tc358876.dtbo \
 ti/k3-am654-pcie-usb2.dtbo ti/k3-am654-pcie-usb3.dtbo \
+ti/k3-am654-base-board-jailhouse.dtbo \
 "
 
 UBOOT_MACHINE = "am65x_evm_a53_defconfig"
diff --git a/conf/machine/include/ti33x.inc b/conf/machine/include/ti33x.inc
index 8ddae81c..5ff6efea 100644
--- a/conf/machine/include/ti33x.inc
+++ b/conf/machine/include/ti33x.inc
@@ -30,8 +30,9 @@ KERNEL_DEVICETREE = " \
 am335x-evm.dtb am335x-evmsk.dtb \
 am335x-icev2.dtb am335x-icev2-prueth.dtb \
 am335x-pocketbeagle.dtb am335x-bone.dtb am335x-boneblue.dtb \
-am335x-boneblack.dtb am335x-boneblack-wireless.dtb \
 am335x-bonegreen.dtb am335x-bonegreen-wireless.dtb \
+am335x-boneblack.dtb am335x-boneblack-wireless.dtb \
+am335x-boneblack-prusuart.dtb am335x-sancloud-bbe.dtb \
 "
 
 KERNEL_DEVICETREE += "${@oe.utils.conditional('ENABLE_TI_UIO_DEVICES', '1', 
'am335x-icev2-pru-excl-uio.dtb', '', d)}"
diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
index 1cb9aff5..ca594e81 100644
--- a/conf/machine/j7-evm.conf
+++ b/conf/machine/j7-evm.conf
@@ -28,9 +28,9 @@ OPTEEOUTPUTMACHINE = "k3"
 IMAGE_BOOT_FILES = "tispl.bin u-boot.img"
 WKS_FILE = "sdimage-bootpart.wks"
 
+do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot u-boot:do_deploy"
+
 # Set the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_SOCS = "j721e"
 TI_PDK_LIMIT_BOARDS = "j721e_evm"
 TI_PDK_LIMIT_CORES = "mpu1_0 mcu1_0 mcu1_1 mcu2_0 mpu2_1 mpu3_0 mpu3_1 
c66xdsp_1 c66xdsp_2 c7x_1"
-
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot u-boot:do_deploy"
-- 
2.17.1

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 1/2] conf/machine: update with new DTBs/DTBOs

2019-08-19 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am65xx-evm.conf   | 1 +
 conf/machine/include/ti33x.inc | 3 ++-
 conf/machine/j7-evm.conf   | 4 ++--
 3 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/conf/machine/am65xx-evm.conf b/conf/machine/am65xx-evm.conf
index 83eae59..27bb0b0 100644
--- a/conf/machine/am65xx-evm.conf
+++ b/conf/machine/am65xx-evm.conf
@@ -16,6 +16,7 @@ KERNEL_DEVICETREE = " \
 ti/k3-am654-evm-csi2-ov490.dtbo ti/k3-am654-evm-csi2-ov5640.dtbo \
 ti/k3-am654-evm-oldi-lcd1evm.dtbo ti/k3-am654-evm-tc358876.dtbo \
 ti/k3-am654-pcie-usb2.dtbo ti/k3-am654-pcie-usb3.dtbo \
+ti/k3-am654-base-board-jailhouse.dtbo \
 "
 
 UBOOT_MACHINE = "am65x_evm_a53_defconfig"
diff --git a/conf/machine/include/ti33x.inc b/conf/machine/include/ti33x.inc
index 8ddae81..28d0972 100644
--- a/conf/machine/include/ti33x.inc
+++ b/conf/machine/include/ti33x.inc
@@ -30,8 +30,9 @@ KERNEL_DEVICETREE = " \
 am335x-evm.dtb am335x-evmsk.dtb \
 am335x-icev2.dtb am335x-icev2-prueth.dtb \
 am335x-pocketbeagle.dtb am335x-bone.dtb am335x-boneblue.dtb \
-am335x-boneblack.dtb am335x-boneblack-wireless.dtb \
 am335x-bonegreen.dtb am335x-bonegreen-wireless.dtb \
+am335x-boneblack.dtb am335x-boneblack-wireless.dtb \
+am335x-boneblack-prusuart.dtb am335x-sancloud-bbe \
 "
 
 KERNEL_DEVICETREE += "${@oe.utils.conditional('ENABLE_TI_UIO_DEVICES', '1', 
'am335x-icev2-pru-excl-uio.dtb', '', d)}"
diff --git a/conf/machine/j7-evm.conf b/conf/machine/j7-evm.conf
index 1cb9aff..ca594e8 100644
--- a/conf/machine/j7-evm.conf
+++ b/conf/machine/j7-evm.conf
@@ -28,9 +28,9 @@ OPTEEOUTPUTMACHINE = "k3"
 IMAGE_BOOT_FILES = "tispl.bin u-boot.img"
 WKS_FILE = "sdimage-bootpart.wks"
 
+do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot u-boot:do_deploy"
+
 # Set the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_SOCS = "j721e"
 TI_PDK_LIMIT_BOARDS = "j721e_evm"
 TI_PDK_LIMIT_CORES = "mpu1_0 mcu1_0 mcu1_1 mcu2_0 mpu2_1 mpu3_0 mpu3_1 
c66xdsp_1 c66xdsp_2 c7x_1"
-
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot u-boot:do_deploy"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 2/2] layer.conf: list additional packages in SIGGEN_EXCLUDERECIPES_ABISAFE

2019-08-19 Thread Denys Dmytriyenko
This helps with sstate re-use when MACHINE changes in the dependency tree.

Signed-off-by: Denys Dmytriyenko 
---
 conf/layer.conf | 8 
 1 file changed, 8 insertions(+)

diff --git a/conf/layer.conf b/conf/layer.conf
index 824443d..cc19429 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -17,6 +17,10 @@ LAYERDEPENDS_meta-ti = "core"
 SIGGEN_EXCLUDERECIPES_ABISAFE += " \
 ti-sgx-ddk-km \
 ti-sgx-ddk-um \
+ti-img-rogue-driver \
+ti-img-rogue-umlibs \
+ti-gc320-driver \
+ti-gc320-libs \
 ti-ipc \
 ti-ipc-rtos \
 cmem-mod \
@@ -28,6 +32,10 @@ SIGGEN_EXCLUDERECIPES_ABISAFE += " \
 cppi-lld \
 qmss-lld \
 multiprocmgr \
+openmp-rtos \
+common-csl-ip \
+libulm \
+linux-ti-staging \
 "
 
 HOSTTOOLS_NONFATAL += "truncate xxd comm"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [master/thud][PATCH] jailhouse: update to ti2019.03-rc2

2019-08-19 Thread Denys Dmytriyenko
On Mon, Aug 19, 2019 at 08:58:14AM -0400, Jacob Stiffler wrote:
> * extend to am65xx family
> * and correct am65xx cell and inmate filenames.
> * remove earlycon bootargs for am65xx

IIRC, earlycon was causing some issues and was supposed to be removed by an 
owner... As well as updating commit and fixing DTBs and cells...


> Signed-off-by: Jacob Stiffler 
> ---
>  recipes-kernel/jailhouse/jailhouse_git.bb | 11 ++-
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> b/recipes-kernel/jailhouse/jailhouse_git.bb
> index 5e2c71b..e1d5263 100644
> --- a/recipes-kernel/jailhouse/jailhouse_git.bb
> +++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = " \
>  "
>  
>  PV = "0.10+git${SRCPV}"
> -SRCREV = "e71fd2dc7e8494a44cc3c762a24824532a412807"
> +SRCREV = "96329f098e655cd42d7d0dbb3cd2cc7c3492d633"
>  BRANCH = "ti-jailhouse-0.10"
>  
>  SRC_URI = " \
> @@ -47,19 +47,20 @@ JH_CELL_FILES ?= "*.cell"
>  JH_CELL_FILES_k3 ?= "k3-*.cell"
>  
>  JH_INMATE_DTB ?= ""
> -JH_INMATE_DTB_am65xx-evm ?= "inmate-k3-am654.dtb"
> +JH_INMATE_DTB_am65xx ?= "inmate-k3-am654-idk.dtb"
>  JH_INMATE_DTB_j7-evm ?= "inmate-k3-j721e-evm.dtb"
>  
>  JH_LINUX_DEMO_CELL ?= ""
> -JH_LINUX_DEMO_CELL_am65xx-evm ?= "k3-am654-linux-demo.cell"
> +JH_LINUX_DEMO_CELL_am65xx ?= "k3-am654-idk-linux-demo.cell"
>  JH_LINUX_DEMO_CELL_j7-evm ?= "k3-j721e-evm-linux-demo.cell"
>  
>  JH_SYSCONFIG_CELL ?= ""
> -JH_SYSCONFIG_CELL_am65xx-evm ?= "k3-am654.cell"
> +JH_SYSCONFIG_CELL_am65xx ?= "k3-am654-idk.cell"
>  JH_SYSCONFIG_CELL_j7-evm ?= "k3-j721e-evm.cell"
>  
>  JH_CMDLINE ?= ""
> -JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext4 rootwait earlycon=ns16550a,mmio32,0x281"
> +JH_CMDLINE_k3 ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext4 rootwait"
> +JH_CMDLINE_j7-evm ?= "console=ttyS1,115200n8 root=/dev/mmcblk0p2 rw 
> rootfstype=ext4 rootwait earlycon=ns16550a,mmio32,0x281"
>  
>  do_configure() {
>   if [ -d ${STAGING_DIR_HOST}/${CELLCONF_DIR} ]; 
> -- 
> 2.7.4
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [EXTERNAL] [thud/master][PATCH] sciclient-rtos: Adding support to j7-evm

2019-08-15 Thread Denys Dmytriyenko
On Tue, Aug 13, 2019 at 04:17:32PM -0400, Jacob Stiffler wrote:
> 
> On 8/13/2019 4:01 PM, Mahesh Radhakrishnan wrote:
> >Signed-off-by: Mahesh Radhakrishnan 
> >---
> >  recipes-bsp/sciclient/sciclient-rtos_git.bb | 7 ++-
> >  1 file changed, 6 insertions(+), 1 deletion(-)
> >
> >diff --git a/recipes-bsp/sciclient/sciclient-rtos_git.bb 
> >b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> >index 36de7c4..8599f6a 100644
> >--- a/recipes-bsp/sciclient/sciclient-rtos_git.bb
> >+++ b/recipes-bsp/sciclient/sciclient-rtos_git.bb
> >@@ -37,8 +37,13 @@ export PDK_SCICLIENT_ROOT_PATH = 
> >"${SCICLIENT_PACKAGE_BASE}/package/all/pdk_/pac
> >  #export DEST_ROOT="${S}"
> >  LIMSOCS_am65xx = "am65xx"
> >+LIMSOCS_j7-evm = "j721e"
> >+
> >  LIMBOARDS_am65xx = "am65xx_evm"
> >+LIMBOARDS_j7-evm = "j721e_evm"
> 
> Can you use the TI_PDK_LIMIT_* vars defined in the machine configuration?

Was this comment addressed?


> >  BOARD_PACKAGE_am65xx = "am65xx_evm"
> >+BOARD_PACKAGE_j7-evm = "j721e_evm"
> >  # HTML doc link params
> >  PDK_COMP_LINK_TEXT = "SCICLIENT"
> >@@ -66,7 +71,7 @@ do_compile() {
> >  # make clean LIMIT_SOCS="${LIMSOCS}" LIMIT_BOARDS="${LIMBOARDS}"
> >  # Build am65xx libraries
> >-make lib xdc_meta doxygen LIMIT_SOCS="${LIMSOCS}" 
> >LIMIT_BOARDS="${LIMBOARDS}"
> >+make lib xdc_meta doxygen LIMIT_SOCS="${LIMSOCS}" 
> >LIMIT_BOARDS="${LIMBOARDS}" LIMIT_CORES="${TI_PDK_LIMIT_CORES}"
> >  #archive
> >  tar -cf sciclient.tar --exclude='*.tar' ./*
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH v3] ti-cgt-7x: Initial version of TI-CGT-C7000 recipe

2019-08-15 Thread Denys Dmytriyenko
Thanks for addressing the comments. Was this tested?

On Tue, Aug 13, 2019 at 09:25:11PM -0400, Mahesh Radhakrishnan wrote:
> This tool is not publically fetchable yet and requires pre-downloading
> 
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  v3 - Removed class-target references,redundant defs,corrected LIC_CHECKSUM 
> file
>  v2 - Changes to remove class-target (LIC_CHECKSUM),updated commit
>  
>  recipes-ti/devtools/ti-cgt7x_1.1.0.bb | 47 
> +++
>  1 file changed, 47 insertions(+)
>  create mode 100644 recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> 
> diff --git a/recipes-ti/devtools/ti-cgt7x_1.1.0.bb 
> b/recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> new file mode 100644
> index 000..233c840
> --- /dev/null
> +++ b/recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> @@ -0,0 +1,47 @@
> +SUMMARY = "TI DSP Code Generation Tools"
> +DESCRIPTION = "Texas Instruments (TI) Code Generation Tools are custom \
> +utilities targeted for TI embedded processors. This Digital Signal \
> +Processor (DSP) suite contains tools needed to create and debug \
> +applications for the C7000 DSP family. This includes tools such as: \
> +compiler, linker, assembler, etc. This also includes C runtime \
> +libraries and standard header files needed to produce a working DSP 
> application."
> +HOMEPAGE = 
> "https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm";
> +LICENSE = "(TI-TSPA & Thai-Open-Source-Software-Center) & BSD-3-Clause & 
> BSL-1.0 & Patrick-Powell & AFL-3.0 & MIT & BSD-2-Clause & PD"
> +
> +LIC_FILES_CHKSUM = 
> "file://ti-cgt-c7000_${PV}/C7000_1.0.x_CodeGenerationTools_Manifest.html;md5=3074e433c5d52657076d1d138dfbdaf8"
> +
> +require recipes-ti/includes/ti-unpack.inc
> +
> +# only x86_64 is supported
> +COMPATIBLE_HOST = "x86_64.*-linux"
> +COMPATIBLE_HOST_class-target = "null"
> +
> +BINFILE = "ti_cgt_c7000_${PV}_linux_installer_x86.bin"
> +BINFILE_NAME = "cgt7x_x86_installer"
> +
> +# Please note, "install.source.dir.local" is not a real URL, below files 
> need to be pre-downloaded
> +SRC_URI = "http://install.source.dir.local/${BINFILE};name=${BINFILE_NAME}";
> +
> +TI_BIN_UNPK_ARGS = "--prefix ${S}"
> +TI_BIN_UNPK_CMDS = ""
> +
> +SRC_URI[cgt7x_x86_installer.md5sum]= "feb668b4213403c661909adcf65d2ba8"
> +SRC_URI[cgt7x_x86_installer.sha256sum] = 
> "4a3954c973622c00a9b91fa90473cf921f4b763300b0e7c32735304867856ab8"
> +
> +S = "${WORKDIR}/c7000_${PV}"
> +
> +do_install() {
> +install -d ${D}/${TI_CGT7X_INSTALL_DIR_RECIPE}
> +cp -rP --preserve=mode,links,timestamps --no-preserve=ownership 
> ${WORKDIR}/c7000_${PV}/. ${D}/${TI_CGT7X_INSTALL_DIR_RECIPE}
> +}
> +
> +
> +FILES_${PN} += "${TI_CGT7X_INSTALL_DIR_RECIPE}"
> +
> +INSANE_SKIP_${PN} += "arch staticdev textrel"
> +
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIBIT_SYSROOT_STRIP = "1"
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +
> +BBCLASSEXTEND = "native nativesdk"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] am65xx-hs-evm: add DTB/DTBO load addresses and offset

2019-08-13 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 conf/machine/am65xx-hs-evm.conf | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/conf/machine/am65xx-hs-evm.conf b/conf/machine/am65xx-hs-evm.conf
index 97afd31..f989750 100644
--- a/conf/machine/am65xx-hs-evm.conf
+++ b/conf/machine/am65xx-hs-evm.conf
@@ -6,10 +6,13 @@ require conf/machine/am65xx-evm.conf
 
 UBOOT_MACHINE = "am65x_hs_evm_a53_defconfig"
 
-UBOOT_ENTRYPOINT = "0x8008"
-UBOOT_LOADADDRESS = "0x8008"
-UBOOT_RD_LOADADDRESS = "0x8400"
-UBOOT_RD_ENTRYPOINT = "0x8400"
+UBOOT_ENTRYPOINT =   "0x8008"
+UBOOT_LOADADDRESS =  "0x8008"
+UBOOT_RD_LOADADDRESS =   "0x8400"
+UBOOT_RD_ENTRYPOINT ="0x8400"
+UBOOT_DTB_LOADADDRESS =  "0x8300"
+UBOOT_DTBO_LOADADDRESS = "0x8308"
+UBOOT_DTBO_OFFSET =  "0x0001"
 
 SPL_BINARY = "tispl.bin_HS"
 SPL_BINARYNAME = "tispl.bin"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH v2] ti-cgt-7x: Initial version of TI-CGT-C7000 recipe

2019-08-13 Thread Denys Dmytriyenko
On Tue, Aug 13, 2019 at 05:25:23PM -0400, Mahesh Radhakrishnan wrote:
> This tool is not publically fetchable yet and requires pre-downloading
> 
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  v2 - Changes to remove class-target (LIC_CHECKSUM),updated commit description
> 
>  recipes-ti/devtools/ti-cgt7x_1.1.0.bb | 50 
> +++
>  1 file changed, 50 insertions(+)
>  create mode 100644 recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> 
> diff --git a/recipes-ti/devtools/ti-cgt7x_1.1.0.bb 
> b/recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> new file mode 100644
> index 000..465857c
> --- /dev/null
> +++ b/recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> @@ -0,0 +1,50 @@
> +DESCRIPTION = "TI DSP Code Generation Tools"

SUMMARY ^


> +HOMEPAGE = 
> "https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm";
> +LICENSE = "(TI-TSPA & Thai-Open-Source-Software-Center) & BSD-3-Clause & 
> BSL-1.0 & Patrick-Powell & AFL-3.0 & MIT & BSD-2-Clause & PD"
> +
> +LIC_FILES_CHKSUM = 
> "file://usr/share/doc/ti/cgt-c7x/C7000_1.0.x_CodeGenerationTools_Manifest.htm;md5=3074e433c5d52657076d1d138dfbdaf8"
> +
> +require recipes-ti/includes/ti-unpack.inc
> +
> +# only x86_64 is supported
> +COMPATIBLE_HOST = "x86_64.*-linux"
> +COMPATIBLE_HOST_class-target = "null"
> +
> +BINFILE = "ti_cgt_c7000_${PV}_linux_installer_x86.bin"
> +BINFILE_NAME = "cgt7x_x86_installer"
> +
> +# Please note, "install.source.dir.local" is not a real URL, below files 
> need to be pre-downloaded
> +SRC_URI = "http://install.source.dir.local/${BINFILE};name=${BINFILE_NAME}";
> +
> +TI_BIN_UNPK_ARGS = "--prefix ${S}"
> +TI_BIN_UNPK_CMDS = ""
> +
> +BINFILE = "ti_cgt_c7000_${PV}_linux_installer_x86.bin"

Duplicate


> +BINFILE_MD5 = "feb668b4213403c661909adcf65d2ba8"
> +BINFILE_SHA256 = 
> "4a3954c973622c00a9b91fa90473cf921f4b763300b0e7c32735304867856ab8"

These 2 are not used


> +SRC_URI[cgt7x_x86_installer.md5sum]= "feb668b4213403c661909adcf65d2ba8"
> +SRC_URI[cgt7x_x86_installer.sha256sum] = 
> "4a3954c973622c00a9b91fa90473cf921f4b763300b0e7c32735304867856ab8"
> +
> +S = "${WORKDIR}/c7000_${PV}"
> +
> +do_install() {
> +install -d ${D}/${TI_CGT7X_INSTALL_DIR_RECIPE}
> +cp -rP --preserve=mode,links,timestamps --no-preserve=ownership 
> ${WORKDIR}/c7000_${PV}/. ${D}/${TI_CGT7X_INSTALL_DIR_RECIPE}
> +}
> +
> +do_install_class-target() {
> +${WORKDIR}/${BINFILE} --prefix ${D}
> +}

This is rather useless


> +FILES_${PN} += "${TI_CGT7X_INSTALL_DIR_RECIPE}"
> +
> +INSANE_SKIP_${PN} += "arch staticdev textrel"
> +
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIBIT_SYSROOT_STRIP = "1"
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +
> +BBCLASSEXTEND = "native nativesdk"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [thud/master][PATCH 1/2] ti-cgt-7x: Initial version of TI-CGT-C7000 recipe

2019-08-13 Thread Denys Dmytriyenko
On Tue, Aug 13, 2019 at 03:48:58PM -0400, Mahesh Radhakrishnan wrote:
> The tools are not available externally yet, hence the
> SRC_URI link
> "http://install.source.dir.local/${BINFILE};name=${BINFILE_NAME}";

Please don't phrase it like this! There's no such thing as internal or 
external at this level. Better say that it's not publicly fetchable yet 
and requires pre-downloading.


> ---
>  recipes-ti/devtools/ti-cgt7x_1.1.0.bb | 65 
> +++
>  1 file changed, 65 insertions(+)
>  create mode 100644 recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> 
> diff --git a/recipes-ti/devtools/ti-cgt7x_1.1.0.bb 
> b/recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> new file mode 100644
> index 000..19da698
> --- /dev/null
> +++ b/recipes-ti/devtools/ti-cgt7x_1.1.0.bb
> @@ -0,0 +1,65 @@
> +DESCRIPTION = "TI DSP Code Generation Tools"
> +HOMEPAGE = 
> "https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm";
> +LICENSE = "(TI-TSPA & Thai-Open-Source-Software-Center) & BSD-3-Clause & 
> BSL-1.0 & Patrick-Powell & AFL-3.0 & MIT & BSD-2-Clause & PD"
> +
> +LIC_FILES_CHKSUM_class-target = 
> "file://usr/share/doc/ti/cgt-c7x/C7000_1.0.x_CodeGenerationTools_Manifest.htm;md5=3074e433c5d52657076d1d138dfbdaf8"
> +
> +require recipes-ti/includes/ti-unpack.inc
> +
> +# only x86_64 is supported
> +COMPATIBLE_HOST = "x86_64.*-linux"
> +COMPATIBLE_HOST_class-target = "null"

So, target is not supported, but LIC_FILES_CHKSUM is only set for the target.


> +# For now we only have hardfp version for target class
> +python __anonymous() {
> +c = d.getVar("CLASSOVERRIDE")
> +
> +if c == "class-target":
> +tunes = d.getVar("TUNE_FEATURES")
> +if not tunes:
> +return
> +pkgn = d.getVar("PN")
> +pkgv = d.getVar("PV")
> +if "callconvention-hard" not in tunes:
> +bb.warn("%s-%s ONLY supports hardfp mode for now" % (pkgn, pkgv))
> +raise bb.parse.SkipPackage("%s-%s ONLY supports hardfp mode for 
> now" % (pkgn, pkgv))

Again, this check is also only valid for the target.


> +}
> +
> +BINFILE = "ti_cgt_c7000_${PV}_linux_installer_x86.bin"
> +BINFILE_NAME = "cgt7x_x86_installer"
> +
> +# Please note, "install.source.dir.local" is not a real URL, below files 
> need to be pre-downloaded
> +SRC_URI = "http://install.source.dir.local/${BINFILE};name=${BINFILE_NAME}";
> +
> +TI_BIN_UNPK_ARGS = "--prefix ${S}"
> +TI_BIN_UNPK_CMDS = ""
> +
> +BINFILE = "ti_cgt_c7000_${PV}_linux_installer_x86.bin"
> +
> +BINFILE_MD5 = "feb668b4213403c661909adcf65d2ba8"
> +BINFILE_SHA256 = 
> "4a3954c973622c00a9b91fa90473cf921f4b763300b0e7c32735304867856ab8"
> +
> +SRC_URI[cgt7x_x86_installer.md5sum]= "feb668b4213403c661909adcf65d2ba8"
> +SRC_URI[cgt7x_x86_installer.sha256sum] = 
> "4a3954c973622c00a9b91fa90473cf921f4b763300b0e7c32735304867856ab8"
> +
> +S = "${WORKDIR}/c7000_${PV}"
> +
> +do_install() {
> +install -d ${D}/${TI_CGT7X_INSTALL_DIR_RECIPE}
> +cp -rP --preserve=mode,links,timestamps --no-preserve=ownership 
> ${WORKDIR}/c7000_${PV}/. ${D}/${TI_CGT7X_INSTALL_DIR_RECIPE}
> +}
> +
> +do_install_class-target() {
> +${WORKDIR}/${BINFILE} --prefix ${D}
> +}
> +
> +
> +FILES_${PN} += "${TI_CGT7X_INSTALL_DIR_RECIPE}"
> +
> +INSANE_SKIP_${PN} += "arch staticdev textrel"
> +
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIBIT_SYSROOT_STRIP = "1"
> +INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> +
> +BBCLASSEXTEND = "native nativesdk"

How are native and nativesdk would work, if LIC_FILES_CHKSUM is only provided 
for target?


> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 2/2] pru-swuart-fw: add PRU Software UART Firmware recipe

2019-08-06 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 ...s_uart-add-Makefile-for-building-firmware.patch | 145 +
 ...01-icss_uart-remove-dependency-on-PDK-CSL.patch |  54 
 recipes-bsp/pru/pru-swuart-fw_git.bb   |  40 ++
 3 files changed, 239 insertions(+)
 create mode 100644 
recipes-bsp/pru/pru-swuart-fw/0001-icss_uart-add-Makefile-for-building-firmware.patch
 create mode 100644 
recipes-bsp/pru/pru-swuart-fw/0001-icss_uart-remove-dependency-on-PDK-CSL.patch
 create mode 100644 recipes-bsp/pru/pru-swuart-fw_git.bb

diff --git 
a/recipes-bsp/pru/pru-swuart-fw/0001-icss_uart-add-Makefile-for-building-firmware.patch
 
b/recipes-bsp/pru/pru-swuart-fw/0001-icss_uart-add-Makefile-for-building-firmware.patch
new file mode 100644
index 000..8414d94
--- /dev/null
+++ 
b/recipes-bsp/pru/pru-swuart-fw/0001-icss_uart-add-Makefile-for-building-firmware.patch
@@ -0,0 +1,145 @@
+From d37359e7b2bd26da4d04fc97a94967cf457558e9 Mon Sep 17 00:00:00 2001
+From: Denys Dmytriyenko 
+Date: Tue, 6 Aug 2019 19:50:59 -0400
+Subject: [PATCH] icss_uart: add Makefile for building firmware
+
+Signed-off-by: Denys Dmytriyenko 
+---
+ firmware/icss_uart/src/Makefile | 125 
+ 1 file changed, 125 insertions(+)
+ create mode 100644 firmware/icss_uart/src/Makefile
+
+diff --git a/firmware/icss_uart/src/Makefile b/firmware/icss_uart/src/Makefile
+new file mode 100644
+index 000..4764622
+--- /dev/null
 b/firmware/icss_uart/src/Makefile
+@@ -0,0 +1,125 @@
++# PRU_CGT environment variable must point to the TI PRU code gen tools 
directory. E.g.:
++#(Desktop Linux) export PRU_CGT=/path/to/pru/code/gen/tools/ti-cgt-pru_2.x.y
++#(Windows) set PRU_CGT=C:/path/to/pru/code/gen/tools/ti-cgt-pru_2.x.y
++#(ARM Linux*) export PRU_CGT=/usr/share/ti/cgt-pru
++#
++# *ARM Linux also needs to create a symbolic link to the /usr/bin/ directory 
in
++# order to use the same Makefile
++#(ARM Linux) ln -s /usr/bin/ /usr/share/ti/cgt-pru/bin
++
++ifndef PRU_CGT
++define ERROR_BODY
++
++***
++PRU_CGT environment variable is not set. Examples given:
++(Desktop Linux) export PRU_CGT=/path/to/pru/code/gen/tools/ti-cgt-pru_2.1.2
++(Windows) set PRU_CGT=C:/path/to/pru/code/gen/tools/ti-cgt-pru_2.1.2
++(ARM Linux*) export PRU_CGT=/usr/share/ti/cgt-pru
++
++*ARM Linux also needs to create a symbolic link to the /usr/bin/ directory in
++order to use the same Makefile
++(ARM Linux) ln -s /usr/bin/ /usr/share/ti/cgt-pru/bin
++***
++
++endef
++$(error $(ERROR_BODY))
++endif
++
++# PRU_SSP environment variable must point to the PRU Software Support 
Package. E.g.:
++#(Desktop Linux) export PRU_SSP=/path/to/pru_software_support_package
++#(Windows) set PRU_SSP=C:/path/to/pru_software_support_package
++#(ARM Linux*) export PRU_SSP=/path/to/pru_software_support_package
++
++ifndef PRU_SSP
++define ERROR_BODY
++
++***
++PRU_SSP environment variable must point to the PRU Software Support Package. 
E.g.:
++(Desktop Linux) export PRU_SSP=/path/to/pru_software_support_package
++(Windows) set PRU_SSP=C:/path/to/pru_software_support_package
++(ARM Linux*) export PRU_SSP=/path/to/pru_software_support_package
++PRU_CGT environment variable is not set. Examples given:
++***
++
++endef
++$(error $(ERROR_BODY))
++endif
++
++MKFILE_PATH := $(abspath $(lastword $(MAKEFILE_LIST)))
++CURRENT_DIR := $(notdir $(patsubst %/,%,$(dir $(MKFILE_PATH
++PROJ_NAME=$(CURRENT_DIR)
++LINKER_COMMAND_FILE=./AM335x_PRU.cmd
++LIBS=--library=$(PRU_SSP)/lib/rpmsg_lib.lib
++INCLUDE=--include_path=$(PRU_SSP)/include 
--include_path=$(PRU_SSP)/include/am335x
++STACK_SIZE=0x100
++HEAP_SIZE=0x100
++GEN_DIR=gen
++
++#Common compiler and linker flags (Defined in 'PRU Optimizing C/C++ Compiler 
User's Guide)
++CFLAGS=-v3 -o2 --display_error_number --endian=little --hardware_mac=on 
--asm_directory=$(GEN_DIR) --obj_directory=$(GEN_DIR) --pp_directory=$(GEN_DIR) 
-ppd -ppa -DICSS_REV2
++#Linker flags (Defined in 'PRU Optimizing C/C++ Compiler User's Guide)
++LFLAGS=--reread_libs --warn_sections --stack_size=$(STACK_SIZE) 
--heap_size=$(HEAP_SIZE)
++
++TARGET=$(GEN_DIR)/$(PROJ_NAME).out
++MAP=$(GEN_DIR)/$(PROJ_NAME).map
++OBJECTS=$(patsubst %.asm,$(GEN_DIR)/%.object,$(wildcard *.asm))
++OBJECTS+=$(patsubst %.c,$(GEN_DIR)/%.object,$(wildcard *.c))
++
++
++all: printStart $(TARGET) printEnd
++
++printStart:
++  @echo ''
++  @echo ''
++  @echo 'Building project: $(PROJ_NAME)'
++
++printEnd:
++  @echo ''
++  @echo 'Output files can be found in the "$(GEN_DIR)" directory'
++

[meta-ti] [thud/master][PATCH 1/2] pru-icss: also install headers and library into dev packages

2019-08-06 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/pru/pru-icss_git.bb | 8 
 1 file changed, 8 insertions(+)

diff --git a/recipes-bsp/pru/pru-icss_git.bb b/recipes-bsp/pru/pru-icss_git.bb
index a36bce0..812caae 100644
--- a/recipes-bsp/pru/pru-icss_git.bb
+++ b/recipes-bsp/pru/pru-icss_git.bb
@@ -50,9 +50,17 @@ do_compile() {
 }
 
 do_install() {
+CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
 install -d ${D}/lib/firmware/pru
+install -d ${D}${includedir}
+cp ${CP_ARGS} ${S}/include/* ${D}${includedir}
+install -d ${D}${libdir}
+install -m 0644 ${S}/lib/rpmsg_lib.lib ${D}${libdir}
 }
 
+FILES_${PN}-staticdev = "${libdir}"
+FILES_${PN}-dev = "${includedir}"
+
 do_install_append_ti33x() {
 install -m 644 ${S}/examples/${PLATFORM}/PRU_Halt/gen/PRU_Halt.out \
${D}/lib/firmware/pru
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] ipc-lld-fw: fix ALTERNATIVE use as package-specific

2019-08-06 Thread Denys Dmytriyenko
Previous commit, while adding support for another platform, extended
ALTERNATIVE variable (which is package-specific) with machine overrides,
accidentally dropping the necessary ${PN} suffix in the process.
Restore it to make update-alternatives system work again.

Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/ipc-lld/ipc-lld-fw_git.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb 
b/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
index 4c8743d..e794df6 100644
--- a/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
+++ b/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
@@ -74,11 +74,11 @@ do_install_append_j7-evm() {
 }
 
 # Set up names for the firmwares
-ALTERNATIVE_am65xx = "\
+ALTERNATIVE_${PN}_am65xx = "\
 am65x-mcu-r5f0_0-fw \
 am65x-mcu-r5f0_1-fw \
 "
-ALTERNATIVE_j7-evm = "\
+ALTERNATIVE_${PN}_j7-evm = "\
 j7-mcu-r5f0_0-fw \
 j7-mcu-r5f0_1-fw \
 j7-main-r5f0_0-fw \
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] Kernel config fragments not in deployed image.

2019-08-04 Thread Denys Dmytriyenko
On Sun, Aug 04, 2019 at 12:03:37PM +, Andy Pont wrote:
> I have created a linux-ti-staging_4.19.bbappend which contains the
> following:
> 
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:”
> 
> SRC_URI += “ \
>   file://rtl8192cu.cfg \
> “
> 
> KERNEL_CONFIG_FRAGMENTS_append = “ \
>   ${WORKDIR}/rtl8192cu.cfg \
> “
> 
> The rtl8192cu.cfg file enables a few options to build a kernel module for
> the RTL8192 USB WiFi module:
> 
> CONFIG_RTL8192CU=m
> CONFIG_RTLWIFI=m
> CONFIG_RTLWIFI_USB=m
> CONFIG_RTLWIFI_DEBUG=y
> CONFIG_RTL8192C_COMMON=m
> 
> After rebuilding the image I can find the resultant rtl8192cu.ko file in a
> number of directories under 
> tmp/work/beaglebone-poky-linux-gnueabi/linux-ti-staging/4.19.38+gitAUTOINC+c17c376661-r22a
> but it isn’t in the lib/modules/… directory in the deployed image.

> Subject: Kernel config fragments not in deployed image.

You are mixing few totally orthogonal things - config fragments, kernel 
modules and what gets added into a deployed image.

Config fragments change kernel configuration, which may or may not result in 
extra kernel modules. Definitely you should not expect config fragments to be 
deployed into an image, as you said in the Subject.

But once you get your modules built, you'd need to modify your image recipe to 
get those installed and be part of the corresponding image.

Depending on your image recipe, you either need to add the extra kernel module 
to RDEPENDS_${PN}, to a corresponding packagegroup or to IMAGE_INSTALL.

-- 
Denys
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH v3] ipc-lld: add AM65xx IPC echo_test firmware binaries

2019-08-02 Thread Denys Dmytriyenko
On Sat, Aug 03, 2019 at 12:10:14PM +1200, Ankur Tyagi wrote:
> On Sat, Aug 3, 2019 at 11:36 AM Jonathan Bergsagel  wrote:
> >
> > Use IPC/LLD based IPC echo test binaries as an
> > alternative for AM65X Linux IPC testing.
> > Updated location of J721E firmware binaries as well,
> > with latest IPC/LLD commit.
> >
> > Signed-off-by: Jonathan Bergsagel 
> > ---
> >  recipes-bsp/ipc-lld/ipc-lld-fw_git.bb | 198 --
> >  1 file changed, 124 insertions(+), 74 deletions(-)
> >
> > diff --git a/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb 
> > b/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
> > index f8157d8c6e5b..4c8743d021f3 100644
> > --- a/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
> > +++ b/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
> > @@ -6,67 +6,79 @@ LIC_FILES_CHKSUM = 
> > "file://LICENSE;md5=7eae093f2b09fd39307f30028a068b91"
> >  inherit deploy
> >  inherit update-alternatives
> >
> > +COMPATIBLE_MACHINE = "k3"
> > +
> >  PV = "1.0-git${SRCPV}"
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >
> >  PROTOCOL = "git"
> >  BRANCH = "master"
> > -SRCREV = "66764a5f063db606ea9db23380694bfd7d4aeafb"
> > +SRCREV = "81392da08fab2b5cfc23d63dbe71b7244a6af477"
> >
> >  SRC_URI = 
> > "git://git.ti.com/keystone-rtos/ipc-lld.git;protocol=${PROTOCOL};branch=${BRANCH}"
> >
> >  S = "${WORKDIR}/git"
> >
> > -R5_DSP_FW_DIR = "${S}/examples/echo_test/binaries"
> > +AM65X_R5_FW_DIR = "${S}/examples/echo_test/binaries/am65xx"
> > +J721E_R5_DSP_FW_DIR = "${S}/examples/echo_test/binaries/j721e"
> 
> Wouldn't it be nice to use machine overrides over here as well?
> R5_DSP_FW_DIR_am65xx = "${S}/examples/echo_test/binaries/am65xx"
> R5_DSP_FW_DIR_j7-evm = "${S}/examples/echo_test/binaries/j721e"

I kind of had the same comment earlier in the internal discussion - am65xx 
version doesn't provide DSP firmware, unlike J7, so it can't be named like 
that. The variable would need to be named more generic - i.e. FW_DIR and then 
have machine specific values. But regardless, it doesn't simplify or improve 
anything, as it will be the same number of lines. So I let it be the way the 
author intended...


> > +PLATFORM_am65xx = "am65xx"
> > +PLATFORM_j7-evm = "j7-evm"
> >
> >  # make sure that lib/firmware, and all its contents are part of the package
> >  FILES_${PN} += "${base_libdir}/firmware"
> >
> >  # install all R5 & DSP ipc echo test binaries in lib/firmware/pdk-ipc, 
> > with softlinks up a level
> >  do_install() {
> > -  install -d ${D}${base_libdir}/firmware/pdk-ipc
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_0_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_0_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_0_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_0_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_1_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_1_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_1_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_1_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_0_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_0_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_0_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_0_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_1_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_1_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_1_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_1_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu3_0_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_test_mcu3_0_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu3_0_release.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 
> > ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu3_0_release.strip.xer5f 
> > ${D}${base_libdir}/firmware/pdk-ipc/
> > -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu

Re: [meta-ti] [thud/master][PATCH] ti-cgt-pru: Update to version 2.3.2

2019-08-02 Thread Denys Dmytriyenko
This breaks nativesdk - please test.


On Fri, Aug 02, 2019 at 02:01:38PM -0400, Mahesh Radhakrishnan wrote:
> The License Checksum has changed due to version, the licenses have not
> changed
> Signed-off-by: Mahesh Radhakrishnan 
> ---
>  recipes-ti/devtools/{ti-cgt-pru_2.2.1.bb => ti-cgt-pru_2.3.2.bb} | 8 
>  1 file changed, 4 insertions(+), 4 deletions(-)
>  rename recipes-ti/devtools/{ti-cgt-pru_2.2.1.bb => ti-cgt-pru_2.3.2.bb} (83%)
> 
> diff --git a/recipes-ti/devtools/ti-cgt-pru_2.2.1.bb 
> b/recipes-ti/devtools/ti-cgt-pru_2.3.2.bb
> similarity index 83%
> rename from recipes-ti/devtools/ti-cgt-pru_2.2.1.bb
> rename to recipes-ti/devtools/ti-cgt-pru_2.3.2.bb
> index 8d3887e..73a767e 100644
> --- a/recipes-ti/devtools/ti-cgt-pru_2.2.1.bb
> +++ b/recipes-ti/devtools/ti-cgt-pru_2.3.2.bb
> @@ -2,8 +2,8 @@ DESCRIPTION = "TI PRU Code Generation Tools"
>  HOMEPAGE = 
> "https://www-a.ti.com/downloads/sds_support/TICodegenerationTools/download.htm";
>  LICENSE = "(TI-TSPA & Thai-Open-Source-Software-Center) & BSD-3-Clause & 
> BSL-1.0 & Hewlett-Packard & AFL-3.0 & MIT & BSD-2-Clause & PD"
>  
> -LIC_FILES_CHKSUM = 
> "file://ti-cgt-pru_${PV}/PRU_Code_Generation_Tools_2.2.x_manifest.html;md5=e84b4022808f66b075095cb896747758"
> -LIC_FILES_CHKSUM_class-target = 
> "file://usr/share/doc/ti/cgt-pru/PRU_Code_Generation_Tools_2.2.x_manifest.html;md5=e84b4022808f66b075095cb896747758"
> +LIC_FILES_CHKSUM = 
> "file://ti-cgt-pru_${PV}/PRU_Code_Generation_Tools_2.3.x_manifest.html;md5=e22f9d8240f7cca0c0aa5242d9ffa5bc"
> +LIC_FILES_CHKSUM_class-target = 
> "file://usr/share/doc/ti/cgt-pru/PRU_Code_Generation_Tools_2.3.x_manifest.html;md5=e22f9d8240f7cca0c0aa5242d9ffa5bc"
>  
>  require recipes-ti/includes/ti-paths.inc
>  require recipes-ti/includes/ti-unpack.inc
> @@ -18,8 +18,8 @@ BINFILE_NAME_class-target = "cgt-pru-arm"
>  
>  SRC_URI = 
> "http://software-dl.ti.com/codegen/esd/cgt_public_sw/PRU/${PV}/${BINFILE};name=${BINFILE_NAME}";
>  
> -SRC_URI[cgt-pru-x86.md5sum] = "749d75841eef7b465c7cb08beaa1d135"
> -SRC_URI[cgt-pru-x86.sha256sum] = 
> "7dc37fd689d1d506bf410d2a00af658b93a58d4bc10ac32c2210129dab617377"
> +SRC_URI[cgt-pru-x86.md5sum] = "270a0ecca383f66cad3a0e2a738c6ab0"
> +SRC_URI[cgt-pru-x86.sha256sum] = 
> "af1178a059d46d67d5672df053dd2fbebb0b89a513b17b8739dbe915b4a5d71a"
>  
>  SRC_URI[cgt-pru-arm.md5sum] = "389eef56777e30e6dab337efca4af2bf"
>  SRC_URI[cgt-pru-arm.sha256sum] = 
> "b47a032f67cb3a3e5bea8ee3ed1908038f42938dd08e2ff72fc64f7aae2c1ff8"
> -- 
> 1.9.1
> 
> -- 
> ___
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH v2] ipc-lld: add AM65xx IPC echo_test firmware binaries

2019-08-02 Thread Denys Dmytriyenko
On Fri, Aug 02, 2019 at 05:00:43PM -0500, Jonathan Bergsagel wrote:
> Use IPC/LLD based IPC echo test binaries as an
> alternative for AM65X Linux IPC testing.
> Updated location of J721E firmware binaries as well,
> with latest IPC/LLD commit.

Thanks! Overall looks good, few comments inside.


> Signed-off-by: Jonathan Bergsagel 
> ---
>  recipes-bsp/ipc-lld/ipc-lld-fw_git.bb | 213 --
>  1 file changed, 131 insertions(+), 82 deletions(-)
> 
> diff --git a/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb 
> b/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
> index f8157d8c6e5b..c58a04158287 100644
> --- a/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
> +++ b/recipes-bsp/ipc-lld/ipc-lld-fw_git.bb
> @@ -6,18 +6,24 @@ LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=7eae093f2b09fd39307f30028a068b91"
>  inherit deploy
>  inherit update-alternatives
>  
> +COMPATIBLE_MACHINE = "am65xx|j7-evm"

Can be combined and replaced by "k3" now.


> +
>  PV = "1.0-git${SRCPV}"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  
>  PROTOCOL = "git"
>  BRANCH = "master"
> -SRCREV = "66764a5f063db606ea9db23380694bfd7d4aeafb"
> +SRCREV = "81392da08fab2b5cfc23d63dbe71b7244a6af477"
>  
>  SRC_URI = 
> "git://git.ti.com/keystone-rtos/ipc-lld.git;protocol=${PROTOCOL};branch=${BRANCH}"
>  
>  S = "${WORKDIR}/git"
>  
> -R5_DSP_FW_DIR = "${S}/examples/echo_test/binaries"
> +AM65X_R5_FW_DIR = "${S}/examples/echo_test/binaries/am65xx"
> +J721E_R5_DSP_FW_DIR = "${S}/examples/echo_test/binaries/j721e"
> 
> +PLATFORM_am65xx = "am65xx"
> +PLATFORM_j7-evm = "j7-evm"
>  
>  # make sure that lib/firmware, and all its contents are part of the package
>  FILES_${PN} += "${base_libdir}/firmware"
> @@ -25,48 +31,54 @@ FILES_${PN} += "${base_libdir}/firmware"
>  # install all R5 & DSP ipc echo test binaries in lib/firmware/pdk-ipc, with 
> softlinks up a level
>  do_install() {
>install -d ${D}${base_libdir}/firmware/pdk-ipc
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_0_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_0_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_0_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_0_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_1_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu1_1_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_1_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu1_1_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_0_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_0_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_0_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_0_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_1_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu2_1_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_1_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu2_1_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu3_0_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu3_0_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu3_0_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu3_0_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu3_1_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_mcu3_1_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu3_1_release.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_testb_mcu3_1_release.strip.xer5f 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_c66xdsp_1_release.xe66 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 
> ${R5_DSP_FW_DIR}/ipc_echo_test_c66xdsp_1_release.strip.xe66 
> ${D}${base_libdir}/firmware/pdk-ipc/
> -  install -m 0644 ${R5_DSP_FW_DIR}/ipc_echo_test_c66xdsp_2_re

[meta-ti] [thud/master][PATCH 1/2] udma: suppress texrel warning, set correct PV version

2019-08-02 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-ti/udma/udma_git.bb | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/recipes-ti/udma/udma_git.bb b/recipes-ti/udma/udma_git.bb
index 0374d37..c905fa5 100644
--- a/recipes-ti/udma/udma_git.bb
+++ b/recipes-ti/udma/udma_git.bb
@@ -10,11 +10,13 @@ S = "${WORKDIR}/git"
 # Commit corresponds to UDMA.01.00.00.00
 SRCREV = "53d09fb0bc98c41c5eb43623097e363c497d6fd8"
 
+PV = "01.00.00.00"
+
 PACKAGES =+ "${PN}-test"
 
 FILES_${PN}-test = "${bindir}/udma_test"
 
-do_install_append() {
+do_install() {
install -d ${D}${bindir}/
install -d ${D}${libdir}/
install -d ${D}${includedir}/
@@ -26,3 +28,5 @@ do_install_append() {
ln -sf libudma.so.1.0.0 libudma.so
install -c -m 755 ${S}/include/* ${D}${includedir}/
 }
+
+INSANE_SKIP_${PN} += "textrel"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH 2/2] cuia: suppress texrel warning

2019-08-02 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/cuia/cuia_1.0.0.13.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb 
b/recipes-bsp/cuia/cuia_1.0.0.13.bb
index a7caf50..0422b0e 100644
--- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
+++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
@@ -26,3 +26,5 @@ do_install() {
 
 COMPATIBLE_HOST ?= "null"
 COMPATIBLE_HOST_ti-soc = "(.*)"
+
+INSANE_SKIP_${PN} += "textrel"
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


[meta-ti] [thud/master][PATCH] recipes: suppress potential host contamination warnings due to ownership

2019-08-02 Thread Denys Dmytriyenko
Signed-off-by: Denys Dmytriyenko 
---
 recipes-bsp/aif2-lld/aif2-lld_git.bb | 1 +
 recipes-bsp/hyplnk-lld/hyplnk-lld_git.bb | 1 +
 recipes-bsp/srio-lld/srio-lld_git.bb | 1 +
 recipes-ti/ipc/ipc-transport-srio_git.bb | 1 +
 4 files changed, 4 insertions(+)

diff --git a/recipes-bsp/aif2-lld/aif2-lld_git.bb 
b/recipes-bsp/aif2-lld/aif2-lld_git.bb
index f310b17..12b1d06 100644
--- a/recipes-bsp/aif2-lld/aif2-lld_git.bb
+++ b/recipes-bsp/aif2-lld/aif2-lld_git.bb
@@ -14,4 +14,5 @@ do_compile () {
 
 do_install () {
 oe_runmake install INSTALL_INC_BASE_DIR=${D}/${includedir} 
INSTALL_LIB_BASE_DIR=${D}${libdir}
+chown -R root:root ${D}
 }
diff --git a/recipes-bsp/hyplnk-lld/hyplnk-lld_git.bb 
b/recipes-bsp/hyplnk-lld/hyplnk-lld_git.bb
index 8ef3c82..08124d7 100644
--- a/recipes-bsp/hyplnk-lld/hyplnk-lld_git.bb
+++ b/recipes-bsp/hyplnk-lld/hyplnk-lld_git.bb
@@ -18,6 +18,7 @@ do_install () {
make -f makefile_armv7 install PDK_INSTALL_PATH="${STAGING_INCDIR}" \
INSTALL_INC_BASE_DIR="${D}/${includedir}" \
INSTALL_LIB_BASE_DIR="${D}${libdir}" HYPLNK_SRC_DIR="${S}"
+   chown -R root:root ${D}
 
# Set the generic device library symbolic link to default k2h
cd ${D}${libdir}
diff --git a/recipes-bsp/srio-lld/srio-lld_git.bb 
b/recipes-bsp/srio-lld/srio-lld_git.bb
index 48e7633..3797bef 100644
--- a/recipes-bsp/srio-lld/srio-lld_git.bb
+++ b/recipes-bsp/srio-lld/srio-lld_git.bb
@@ -17,4 +17,5 @@ do_compile () {
 
 do_install () {
oe_runmake install INSTALL_INC_BASE_DIR=${D}${includedir} 
INSTALL_LIB_BASE_DIR=${D}${libdir}
+   chown -R root:root ${D}
 }
diff --git a/recipes-ti/ipc/ipc-transport-srio_git.bb 
b/recipes-ti/ipc/ipc-transport-srio_git.bb
index f0586d8..ca7f7b6 100644
--- a/recipes-ti/ipc/ipc-transport-srio_git.bb
+++ b/recipes-ti/ipc/ipc-transport-srio_git.bb
@@ -13,4 +13,5 @@ do_compile () {
 do_install () {
oe_runmake install INSTALL_INC_BASE_DIR=${D}${includedir} \
INSTALL_LIB_BASE_DIR=${D}${libdir}
+   chown -R root:root ${D}
 }
-- 
2.7.4

-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH] ti-img-rogue-driver: Update recipe to pick newer version

2019-08-02 Thread Denys Dmytriyenko
Ah, you mean "thud" tag, Ok.

On Fri, Aug 02, 2019 at 03:32:28PM -0400, Denys Dmytriyenko wrote:
> It's automatic
> 
> On Fri, Aug 02, 2019 at 03:28:54PM -0400, Tammana, Gowtham wrote:
> > Missed on meta-ti tag in the subject. Will send v2.
> > 
> > Thanks,
> > Gowtham
> > 
> > >-Original Message-
> > >From: Tammana, Gowtham
> > >Sent: Friday, August 02, 2019 2:30 PM
> > >To: Dmytriyenko, Denys; meta-ti@yoctoproject.org
> > >Cc: Tammana, Gowtham
> > >Subject: [PATCH] ti-img-rogue-driver: Update recipe to pick newer version
> > >
> > >Updated the recipe to pick the newer version, 1.10.5371573, of rogue
> > >gpu kernel sources.
> > >
> > >Signed-off-by: Gowtham Tammana 
> > >---
> > > ...er_1.10.5187610.bb => ti-img-rogue-driver_1.10.5371573.bb} | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > rename recipes-bsp/powervr-drivers/{ti-img-rogue-driver_1.10.5187610.bb =>
> > >ti-img-rogue-driver_1.10.5371573.bb} (92%)
> > >
> > >diff --git 
> > >a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5187610.bb
> > >b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> > >similarity index 92%
> > >rename from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5187610.bb
> > >rename to recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> > >index 9ae60c4e..fcf35edc 100644
> > >--- a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5187610.bb
> > >+++ b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> > >@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM =
> > >"file://README;beginline=15;endline=20;md5=0403c7dea01a2b8232
> > >
> > > inherit module
> > >
> > >-MACHINE_KERNEL_PR_append = "e"
> > >+MACHINE_KERNEL_PR_append = "a"
> > > PR = "${MACHINE_KERNEL_PR}"
> > >
> > > PACKAGE_ARCH = "${MACHINE_ARCH}"
> > >@@ -20,7 +20,7 @@ BRANCH = "linuxws/thud/k4.19/${PV}"
> > > SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-
> > >driver.git;branch=${BRANCH}"
> > > S = "${WORKDIR}/git"
> > >
> > >-SRCREV = "976f73444ef86b231819052bba2020e5b00aeb06"
> > >+SRCREV = "1531b98ba602911359bfded2d683e49b3c731313"
> > >
> > > PVR_SOC = "j721e_linux"
> > > PVR_BVNC = "22.104.208.318"
> > >--
> > >2.22.0
> > 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


Re: [meta-ti] [PATCH] ti-img-rogue-driver: Update recipe to pick newer version

2019-08-02 Thread Denys Dmytriyenko
It's automatic

On Fri, Aug 02, 2019 at 03:28:54PM -0400, Tammana, Gowtham wrote:
> Missed on meta-ti tag in the subject. Will send v2.
> 
> Thanks,
> Gowtham
> 
> >-Original Message-
> >From: Tammana, Gowtham
> >Sent: Friday, August 02, 2019 2:30 PM
> >To: Dmytriyenko, Denys; meta-ti@yoctoproject.org
> >Cc: Tammana, Gowtham
> >Subject: [PATCH] ti-img-rogue-driver: Update recipe to pick newer version
> >
> >Updated the recipe to pick the newer version, 1.10.5371573, of rogue
> >gpu kernel sources.
> >
> >Signed-off-by: Gowtham Tammana 
> >---
> > ...er_1.10.5187610.bb => ti-img-rogue-driver_1.10.5371573.bb} | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> > rename recipes-bsp/powervr-drivers/{ti-img-rogue-driver_1.10.5187610.bb =>
> >ti-img-rogue-driver_1.10.5371573.bb} (92%)
> >
> >diff --git a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5187610.bb
> >b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> >similarity index 92%
> >rename from recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5187610.bb
> >rename to recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> >index 9ae60c4e..fcf35edc 100644
> >--- a/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5187610.bb
> >+++ b/recipes-bsp/powervr-drivers/ti-img-rogue-driver_1.10.5371573.bb
> >@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM =
> >"file://README;beginline=15;endline=20;md5=0403c7dea01a2b8232
> >
> > inherit module
> >
> >-MACHINE_KERNEL_PR_append = "e"
> >+MACHINE_KERNEL_PR_append = "a"
> > PR = "${MACHINE_KERNEL_PR}"
> >
> > PACKAGE_ARCH = "${MACHINE_ARCH}"
> >@@ -20,7 +20,7 @@ BRANCH = "linuxws/thud/k4.19/${PV}"
> > SRC_URI = "git://git.ti.com/graphics/ti-img-rogue-
> >driver.git;branch=${BRANCH}"
> > S = "${WORKDIR}/git"
> >
> >-SRCREV = "976f73444ef86b231819052bba2020e5b00aeb06"
> >+SRCREV = "1531b98ba602911359bfded2d683e49b3c731313"
> >
> > PVR_SOC = "j721e_linux"
> > PVR_BVNC = "22.104.208.318"
> >--
> >2.22.0
> 
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti


  1   2   3   4   5   6   7   8   9   10   >