[meta-ti] [PATCH] kselftests: Fix typo in COMPATIBLE_MACHINE

[Khem Raj]

Signed-off-by: Khem Raj 
---
 recipes-kernel/kselftests/kselftests_4.10.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/kselftests/kselftests_4.10.bb 
b/recipes-kernel/kselftests/kselftests_4.10.bb
index 115b0767..f478e56d 100644
--- a/recipes-kernel/kselftests/kselftests_4.10.bb
+++ b/recipes-kernel/kselftests/kselftests_4.10.bb
@@ -186,5 +186,5 @@ INSANE_SKIP_${PN}-ipc = "ldflags"
 INSANE_SKIP_${PN}-mount = "ldflags"
 INSANE_SKIP_${PN}-vm = "ldflags"
 
-COMAPTIBLE_MACHINE_riscv64 = "(null)"
-COMAPTIBLE_MACHINE_riscv32 = "(null)"
+COMPATIBLE_MACHINE_riscv64 = "(null)"
+COMPATIBLE_MACHINE_riscv32 = "(null)"
-- 
2.24.0

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

[meta-ti] [PATCH] kselftests: Disable for riscv

[Khem Raj]

4.10 did not have RISC-V support

Signed-off-by: Khem Raj 
---
 recipes-kernel/kselftests/kselftests_4.10.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-kernel/kselftests/kselftests_4.10.bb 
b/recipes-kernel/kselftests/kselftests_4.10.bb
index 96263875..115b0767 100644
--- a/recipes-kernel/kselftests/kselftests_4.10.bb
+++ b/recipes-kernel/kselftests/kselftests_4.10.bb
@@ -185,3 +185,6 @@ INSANE_SKIP_${PN}-exec = "ldflags"
 INSANE_SKIP_${PN}-ipc = "ldflags"
 INSANE_SKIP_${PN}-mount = "ldflags"
 INSANE_SKIP_${PN}-vm = "ldflags"
+
+COMAPTIBLE_MACHINE_riscv64 = "(null)"
+COMAPTIBLE_MACHINE_riscv32 = "(null)"
-- 
2.24.0

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

Re: [meta-ti] [master/thud][PATCH 01/42] ti-pdk-fetch: add class for common pdk sources

[Khem Raj]

On Fri, 2019-11-15 at 10:14 -0500, Jacob Stiffler wrote:
> Recently individual components and LLD sources have been combined
> into a single PDK repo. Use this class to specify the common source.
> Also use this class to keep the sources separate from each other when
> building. This keeps the build identical to previous recipes while
> keeping control on interdependencies.
> 
> Signed-off-by: Jacob Stiffler 
> ---
>  classes/ti-pdk-fetch.bbclass | 31 +++
>  1 file changed, 31 insertions(+)
>  create mode 100644 classes/ti-pdk-fetch.bbclass
> 
> diff --git a/classes/ti-pdk-fetch.bbclass b/classes/ti-pdk-
> fetch.bbclass
> new file mode 100644
> index 000..6e36e3b
> --- /dev/null
> +++ b/classes/ti-pdk-fetch.bbclass
> @@ -0,0 +1,31 @@
> +TI_PDK_GIT_URI ?= "git://git.ti.com/processor-sdk/pdk.git"
> +TI_PDK_GIT_BRANCH ?= "master"
> +TI_PDK_GIT_PROTOCOL ?= "git"
> +TI_PDK_SRCREV ?= "a609fa636c4d899e5dd3d7a89a1c070b854849b0"
> +
> +TI_PDK_VERSION ?= "2019.11.0+git${SRCPV}"
> +
> +TI_PDK_SRC = "_tmp_pdk"
> +SRC_URI =
> "${TI_PDK_GIT_URI};branch=${TI_PDK_GIT_BRANCH};protocol=${TI_PDK_GIT_
> PROTOCOL};destsuffix=${TI_PDK_SRC}"
> +SRCREV = "${TI_PDK_SRCREV}"
> +
> +PV = "${TI_PDK_VERSION}"
> +
> +TI_PDK_COMP ?= ""
> +TI_PDK_COMP_PATH = "${@'${TI_PDK_COMP}'.replace('.','/')}"
> +
> +S = "${WORKDIR}/git/${TI_PDK_COMP_PATH}"
> +
> +# Extract only required sources from PDK
> +python do_unpack_append() {
> +if len(d.getVar('TI_PDK_COMP') or '') > 0:
> +import subprocess
> +
> +src =
> os.path.join(d.getVar('TI_PDK_SRC'),'packages',d.getVar('TI_PDK_COMP_
> PATH'))
> +
> +# Package up only the required sources
> +cmd = 'tar -cf - -C %s -p -S . | tar -xf - -C %s' % (src,
> d.getVar('S'))
> +subprocess.check_output(cmd, shell=True,
> stderr=subprocess.STDOUT)
> +
> +bb.utils.remove(d.getVar('TI_PDK_SRC'), recurse=True)
> +}

perhaps looking in work-shared idea from kernel or gcc or clang
packages could make it better where, you only untar sources once

> -- 
> 2.7.4
> 

-- 
___
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

[Khem Raj]

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 ?

>  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

Re: [meta-ti] [thud][PATCH V1] cpsw9g-eth-fw: update ethernet firmware

[Khem Raj]

I am getting this error

Cloning into bare repository
'TOPDIR/downloads/git2/git.ti.com.glsdk.ti-eth-fw.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/glsdk/ti-eth-fw.git;protocol=git;branch=master'.
Unable to fetch URL from any source.

On Wed, Oct 16, 2019 at 11:41 AM Santhana Bharathi  wrote:
>
>  * Updated Ethernet firmware binary for 1.0 release
>
> Signed-off-by: Santhana Bharathi 
> ---
>  recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb 
> b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> index a521edf..5598e42 100644
> --- a/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> +++ b/recipes-bsp/cpsw9g-eth-fw/cpsw9g-eth-fw_git.bb
> @@ -11,7 +11,7 @@ inherit update-alternatives
>
>  PROTOCOL = "git"
>  BRANCH = "master"
> -SRCREV = "7f3af9b0b4c04edcb68c49cb64fcf0d65a860457"
> +SRCREV = "792c06d9a0f2b9d4b150bce4651bdaae2413b28d"
>
>  SRC_URI = 
> "git://git.ti.com/glsdk/ti-eth-fw.git;protocol=${PROTOCOL};branch=${BRANCH}"
>
> --
> 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] [PATCH] ion-tests: Fix build with musl

[Khem Raj]

Signed-off-by: Khem Raj 
---
 ...e-PAGE_SIZE-with-local-variable-name.patch | 69 +++
 recipes-devtools/ion/ion-tests_git.bb |  1 +
 2 files changed, 70 insertions(+)
 create mode 100644 
recipes-devtools/ion/ion-tests/0001-map_test-Replace-PAGE_SIZE-with-local-variable-name.patch

diff --git 
a/recipes-devtools/ion/ion-tests/0001-map_test-Replace-PAGE_SIZE-with-local-variable-name.patch
 
b/recipes-devtools/ion/ion-tests/0001-map_test-Replace-PAGE_SIZE-with-local-variable-name.patch
new file mode 100644
index ..8915c642
--- /dev/null
+++ 
b/recipes-devtools/ion/ion-tests/0001-map_test-Replace-PAGE_SIZE-with-local-variable-name.patch
@@ -0,0 +1,69 @@
+From f045cbf9aae0053e9e785e32b772e473aa892443 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Sun, 6 Oct 2019 16:08:36 -0700
+Subject: [PATCH] map_test: Replace PAGE_SIZE with local variable name
+
+PAGE_SIZE is already a define in libc implementations global namespace
+e.g. in musl. Therefore its best to use a unique variable name to not
+stamp on the global definition.
+
+Fixes
+src/map_test.cpp:59:23: error: expected unqualified-id
+unsigned long PAGE_SIZE = sysconf(_SC_PAGESIZE);
+^
+/usr/include/limits.h:89:19: note: expanded from macro 'PAGE_SIZE'
+^
+/usr/include/bits/limits.h:3:18: note: expanded from macro 'PAGESIZE'
+^
+
+Upstream-Status: Submitted [https://github.com/glneo/ion-tests/pull/1]
+
+Signed-off-by: Khem Raj 
+---
+ src/map_test.cpp | 18 +-
+ 1 file changed, 9 insertions(+), 9 deletions(-)
+
+diff --git a/src/map_test.cpp b/src/map_test.cpp
+index a7ce2c9..7b5746d 100644
+--- a/src/map_test.cpp
 b/src/map_test.cpp
+@@ -56,27 +56,27 @@ TEST_F(Map, MapOffset)
+ SCOPED_TRACE(::testing::Message() << "heap " << heapMask);
+ int map_fd = -1;
+ 
+-unsigned long PAGE_SIZE = sysconf(_SC_PAGESIZE);
++unsigned long psize = sysconf(_SC_PAGESIZE);
+ 
+-ASSERT_EQ(0, ion_alloc(m_ionFd, PAGE_SIZE * 2, heapMask, 0, _fd));
++ASSERT_EQ(0, ion_alloc(m_ionFd, psize * 2, heapMask, 0, _fd));
+ ASSERT_GE(map_fd, 0);
+ 
+ unsigned char *ptr;
+-ptr = (unsigned char *)mmap(NULL, PAGE_SIZE * 2, PROT_READ | 
PROT_WRITE, MAP_SHARED, map_fd, 0);
++ptr = (unsigned char *)mmap(NULL, psize * 2, PROT_READ | PROT_WRITE, 
MAP_SHARED, map_fd, 0);
+ ASSERT_TRUE(ptr != NULL);
+ 
+-memset(ptr, 0, PAGE_SIZE);
+-memset(ptr + PAGE_SIZE, 0xaa, PAGE_SIZE);
++memset(ptr, 0, psize);
++memset(ptr + psize, 0xaa, psize);
+ 
+-ASSERT_EQ(0, munmap(ptr, PAGE_SIZE * 2));
++ASSERT_EQ(0, munmap(ptr, psize * 2));
+ 
+-ptr = (unsigned char *)mmap(NULL, PAGE_SIZE, PROT_READ | PROT_WRITE, 
MAP_SHARED, map_fd, PAGE_SIZE);
++ptr = (unsigned char *)mmap(NULL, psize, PROT_READ | PROT_WRITE, 
MAP_SHARED, map_fd, psize);
+ ASSERT_TRUE(ptr != NULL);
+ 
+ ASSERT_EQ(ptr[0], 0xaa);
+-ASSERT_EQ(ptr[PAGE_SIZE - 1], 0xaa);
++ASSERT_EQ(ptr[psize - 1], 0xaa);
+ 
+-ASSERT_EQ(0, munmap(ptr, PAGE_SIZE));
++ASSERT_EQ(0, munmap(ptr, psize));
+ 
+ ASSERT_EQ(0, close(map_fd));
+ }
+-- 
+2.23.0
+
diff --git a/recipes-devtools/ion/ion-tests_git.bb 
b/recipes-devtools/ion/ion-tests_git.bb
index 831f5e8c..52346f1c 100644
--- a/recipes-devtools/ion/ion-tests_git.bb
+++ b/recipes-devtools/ion/ion-tests_git.bb
@@ -8,6 +8,7 @@ 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 \
+   file://0001-map_test-Replace-PAGE_SIZE-with-local-variable-name.patch \
 "
 SRCREV = "70d730cebca29e6fd37b21d9beac82ae645f3900"
 
-- 
2.23.0

-- 
___
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

[Khem Raj]

On 10/1/19 3:16 PM, Denys Dmytriyenko wrote:

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.

I think this is fine from submitter point of view, Probably, on the 
reviewer side, this should be considered as a test to accept a 
contribution. I am happy to test your master-next or any other staging 
branch that you use for testing meta-ti contribution, provided you will 
hold commits and wait for build results from Yoe Distro world builds.


--
___
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

[Khem Raj]

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

>
>
>
> > > +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 v2] recipes-bsp: ivshmem-uio: Add new recipe for ivshmem-uio driver

[Khem Raj]

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


> +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] [PATCH] vshmem-uio-driver: Make it ti-soc specific

[Khem Raj]

It rdepends on jailhouse package which is already marked at ti-soc
compatible only, so in a multi-BSP setup it ends up breaking builds

ERROR: Nothing RPROVIDES 'jailhouse' (but
/home/jenkins/oe/world/yoe/sources/meta-ti/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
RDEPENDS on or otherwise requires it)
jailhouse was skipped: incompatible with machine qemux86-64 (not in 
COMPATIBLE_MACHINE)
NOTE: Runtime target 'jailhouse' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['jailhouse']
NOTE: Runtime target 'ivshmem-uio-driver-dev' is unbuildable,
removing...
Missing or unbuildable dependency chain was: ['ivshmem-uio-driver-dev', 
'jailhouse']
ERROR: Nothing RPROVIDES 'ivshmem-uio-driver' (but 
/home/jenkins/oe/world/yoe/sources/meta-ti/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
 RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'ivshmem-uio-driver'
NOTE: Runtime target 'ivshmem-uio-driver' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['ivshmem-uio-driver']

Signed-off-by: Khem Raj 
---
 recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb 
b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
index a9f14552..39a75533 100644
--- a/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
+++ b/recipes-bsp/ivshmem-uio/ivshmem-uio-driver_git.bb
@@ -17,6 +17,8 @@ S = "${WORKDIR}/git"
 
 EXTRA_OEMAKE += 'KDIR="${STAGING_KERNEL_DIR}"'
 
+COMPATIBLE_MACHINE = "(ti-soc)"
+
 do_compile_prepend() {
 cd ${S}/kernel_module/uio
 }
-- 
2.23.0

-- 
___
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

[Khem Raj]

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.

>
> > > 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

[Khem Raj]

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.

> 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

[meta-ti] [PATCH] signgp.bb: Use SPDX short identifier for new BSD i.e. BSD-3-Clause

[Khem Raj]

Signed-off-by: Khem Raj 
---
 recipes-bsp/x-load/signgp.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-bsp/x-load/signgp.bb b/recipes-bsp/x-load/signgp.bb
index 9c3499f6..479e6f81 100644
--- a/recipes-bsp/x-load/signgp.bb
+++ b/recipes-bsp/x-load/signgp.bb
@@ -1,4 +1,4 @@
-LICENSE = "NewBSD"
+LICENSE = "BSD-3-Clause"
 DESCRIPTION = "Tool to sign omap3 x-loader images"
 LIC_FILES_CHKSUM = "file://signGP.c;md5=960f484fea13941ca88821366f9dade0"
 
-- 
2.23.0

-- 
___
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

[Khem Raj]

On Sun, Sep 29, 2019 at 9:40 AM Denys Dmytriyenko  wrote:
>
> 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.
>

hmm I guess not pretty but seems fine here. Lets drop this patch.

> 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

[meta-ti] [PATCH 2/3] recipes-ti: Use COMMON_LICENSE_DIR instead of COREBASE

[Khem Raj]

Fixes
beaglebone-capes-1.0-r4 do_populate_lic: ${COREBASE}/LICENSE is not a valid 
license file, please use '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in 
LIC_FILES_CHKSUM. This will become an error in the future

Signed-off-by: Khem Raj 
---
 recipes-ti/beagleboard/beaglebone-capes.bb | 2 +-
 recipes-ti/beagleboard/gadget-init.bb  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-ti/beagleboard/beaglebone-capes.bb 
b/recipes-ti/beagleboard/beaglebone-capes.bb
index 30b985b5..569a3e5a 100644
--- a/recipes-ti/beagleboard/beaglebone-capes.bb
+++ b/recipes-ti/beagleboard/beaglebone-capes.bb
@@ -1,7 +1,7 @@
 DESCRIPTION = "Userspace setup for beaglebone capes"
 
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=b97a012949927931feb7793eee5ed924 "
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
 
 PR = "r4"
 
diff --git a/recipes-ti/beagleboard/gadget-init.bb 
b/recipes-ti/beagleboard/gadget-init.bb
index 8b899c51..b546efbb 100644
--- a/recipes-ti/beagleboard/gadget-init.bb
+++ b/recipes-ti/beagleboard/gadget-init.bb
@@ -3,7 +3,7 @@ DESCRIPTION = "Units to initialize usb gadgets"
 PR = "r19"
 
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690"
+LIC_FILES_CHKSUM = 
"file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
 
 COMPATIBLE_MACHINE = "(ti33x)"
 PACKAGE_ARCH = "${MACHINE_ARCH}"
-- 
2.23.0

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

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

[Khem Raj]

This is as per
https://github.com/jadonk/beaglebone-getting-started/blob/master/LICENSE.txt

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] [PATCH 1/3] u-boot-ti: Drop using COREBASE

[Khem Raj]

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

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] [PATCH V3] rwmem: Update to 2.0-rc2+

[Khem Raj]

- New versions uses CMake and extra modules
- Correct detection of nm/ranlib/ar for LTO
- Fix build with clang/libc++
- depend on python3, needed during build

Signed-off-by: Khem Raj 
---
v2: Move to latest upstream and drop upstreamed patches
v3: depend on python3

 recipes-bsp/rwmem/rwmem_1.1.bb | 13 -
 recipes-bsp/rwmem/rwmem_1.2.bb | 27 +++
 2 files changed, 27 insertions(+), 13 deletions(-)
 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_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 ..0545b0cc
--- /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"
+
+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.23.0

-- 
___
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+

[Khem Raj]

On Thu, Sep 26, 2019 at 11:37 AM Denys Dmytriyenko  wrote:
>
> 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.

hmmm a clean build shows it here as well. Sending v3

>
>
> > >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: Includ

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

[Khem Raj]

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




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 \
+   

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

[Khem Raj]

- 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 
---
v2: Move to latest upstream and drop upstreamed patches

 recipes-bsp/rwmem/rwmem_1.1.bb | 13 -
 recipes-bsp/rwmem/rwmem_1.2.bb | 25 +
 2 files changed, 25 insertions(+), 13 deletions(-)
 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_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 ..7bd71da9
--- /dev/null
+++ b/recipes-bsp/rwmem/rwmem_1.2.bb
@@ -0,0 +1,25 @@
+SUMMARY = "A small tool to read/write memory"
+LICENSE = "GPLv2+"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=b234ee4d69f5fce4486a80fdaf4a4263"
+
+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 python3native
+
+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.23.0

-- 
___
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+

[Khem Raj]

On Thu, Sep 26, 2019 at 9:12 AM Denys Dmytriyenko  wrote:
>
> 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.
>

yeah I think this recipe should actually move out to a common layer
since there seems
to be nothing SOC specific in it.

>
> 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 sm

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

[Khem Raj]

- 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/inih
 \
+   
git://github.com/pybind/pybind11.git;protocol=https;name=pybind11;nobranch=1;destsuffix=git/ext/pybind11
 \
+   file://0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch \
+   
file://0001-librwmem-helpers.h-Include-cerrno-for-errno-definiti.p

[meta-ti] [PATCH] uim: Rename to uim-sysfs

[Khem Raj]

There is a uim recipe clash with meta-oe layer where uim recipe is
pre-existing see [1]

[1] 
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/uim/

Signed-off-by: Khem Raj 
---
 recipes-connectivity/uim/{uim_8.5.bb => uim-sysfs_8.5.bb} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-connectivity/uim/{uim_8.5.bb => uim-sysfs_8.5.bb} (100%)

diff --git a/recipes-connectivity/uim/uim_8.5.bb 
b/recipes-connectivity/uim/uim-sysfs_8.5.bb
similarity index 100%
rename from recipes-connectivity/uim/uim_8.5.bb
rename to recipes-connectivity/uim/uim-sysfs_8.5.bb
-- 
2.23.0

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

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

[Khem Raj]

I have submitted it https://github.com/glneo/libion/pull/1

On Mon, Sep 16, 2019 at 9:58 AM Denys Dmytriyenko  wrote:
>
> 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

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

[Khem Raj]

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

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

[Khem Raj]

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

[meta-ti] [PATCH] ti-unpack: Simplify the logic to detect 32bit glibc on build host

[Khem Raj]

Signed-off-by: Khem Raj 
---
 recipes-ti/includes/ti-unpack.inc | 5 +
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/recipes-ti/includes/ti-unpack.inc 
b/recipes-ti/includes/ti-unpack.inc
index 81fcf6a6..828f3d5a 100644
--- a/recipes-ti/includes/ti-unpack.inc
+++ b/recipes-ti/includes/ti-unpack.inc
@@ -20,10 +20,7 @@ python ti_bin_do_unpack() {
 import os
 
 # InstallJammer requires 32bit version of glibc
-lib32path = '/lib'
-if os.path.exists('/lib64') and (os.path.islink('/lib64') or 
os.path.islink('/lib') or os.path.exists('/lib32')):
-lib32path = '/lib32'
-if not os.path.exists('%s/libc.so.6' % lib32path) and not 
os.path.exists('%s/i386-linux-gnu/libc.so.6' % lib32path):
+if not os.path.exists('/lib/ld-linux.so.2'):
 bb.fatal("TI installer requires 32bit glibc libraries for proper 
operation\nrun 'yum install glibc.i686' on Fedora or 'apt-get install 
libc6:i386' on Ubuntu/Debian")
 
 localdata = bb.data.createCopy(d)
-- 
2.23.0

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

[meta-ti] WARNING: ti-cgt6x-1_8.3.2-r0 do_populate_lic: ti-cgt6x: No generic license file exists for: Patrick-Powell in any provider

[Khem Raj]

Hi

Couple of recipes list Patrick-Powell in LICENSE filed but there is no
file pertaining to this license
in the license/ folder. This is flagged by build

WARNING: ti-cgt6x-1_8.3.2-r0 do_populate_lic: ti-cgt6x: No generic
license file exists for: Patrick-Powell in any provider

here are recipes


recipes-ti/devtools/ti-cgt-arm.inc:LICENSE = "(TI-TSPA &
Thai-Open-Source-Software-Center) & BSD-3-Clause & BSL-1.0 &
Hewlett-Packard & Patrick-Powell & AFL-3.0 & MIT & BSD-2-Clause & PD &
BSD-4-Clause"
recipes-ti/devtools/ti-cgt6x_8.3.2.bb:LICENSE = "(TI-TSPA &
Thai-Open-Source-Software-Center) & BSD-3-Clause & BSL-1.0 &
Patrick-Powell & AFL-3.0 & MIT & BSD-2-Clause & PD"

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

Re: [meta-ti] [PATCH 2/2] amx3-cm3,u-boot-ti: Pin to gcc compiler

[Khem Raj]

On Mon, Jul 15, 2019 at 1:01 PM Denys Dmytriyenko  wrote:
>
> On Fri, Jul 12, 2019 at 05:59:55PM -0700, Khem Raj wrote:
> > Using clang as default compiler fails to build these
> > since these packages explicitly asks for gcc as compiler
> > this ensures that we meet that demand
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb | 2 ++
> >  recipes-bsp/u-boot/u-boot-ti.inc| 3 +++
> >  2 files changed, 5 insertions(+)
> >
> > diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb 
> > b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> > index 79166ca9..196b11b9 100644
> > --- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> > +++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> > @@ -26,3 +26,5 @@ do_install() {
> >  FILES_${PN} += "${base_libdir}/firmware"
> >
> >  COMPATIBLE_MACHINE = "(ti-soc)"
> > +TOOLCHAIN = "gcc"
> > +
> > diff --git a/recipes-bsp/u-boot/u-boot-ti.inc 
> > b/recipes-bsp/u-boot/u-boot-ti.inc
> > index b66a7a6f..36746826 100644
> > --- a/recipes-bsp/u-boot/u-boot-ti.inc
> > +++ b/recipes-bsp/u-boot/u-boot-ti.inc
> > @@ -370,3 +370,6 @@ do_deploy_append_keystone () {
> >   fi
> >   fi
> >  }
> > +
> > +TOOLCHAIN = "gcc"
> > +
>
> Applying: amx3-cm3,u-boot-ti: Pin to gcc compiler
> .git/rebase-apply/patch:15: new blank line at EOF.
> +
> .git/rebase-apply/patch:26: new blank line at EOF.
> +
> warning: 2 lines add whitespace errors.

usually git can squelch those
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH 3/4] jailhouse: Replace tabs with spaces in python code

[Khem Raj]

Ok, thanks. it works.

On Mon, Jul 15, 2019 at 1:12 PM Denys Dmytriyenko  wrote:
>
> I had to do this one differently, all others are now in "next" for testing.
> Thanks.
>
> Denys
>
>
> On Fri, Jul 12, 2019 at 05:43:23PM -0700, Khem Raj wrote:
> > Fixes
> > WARNING: python should use 4 spaces indentation, but found tabs in 
> > jailhouse_git.bb, line 85
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  recipes-kernel/jailhouse/jailhouse_git.bb | 8 
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
> > b/recipes-kernel/jailhouse/jailhouse_git.bb
> > index 753664ed..db31bb7d 100644
> > --- a/recipes-kernel/jailhouse/jailhouse_git.bb
> > +++ b/recipes-kernel/jailhouse/jailhouse_git.bb
> > @@ -82,10 +82,10 @@ do_compile() {
> >  }
> >
> >  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')
> > +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')
> >  }
> >
> >  do_install() {
> > --
> > 2.22.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] [PATCH 2/2] amx3-cm3,u-boot-ti: Pin to gcc compiler

[Khem Raj]

Using clang as default compiler fails to build these
since these packages explicitly asks for gcc as compiler
this ensures that we meet that demand

Signed-off-by: Khem Raj 
---
 recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb | 2 ++
 recipes-bsp/u-boot/u-boot-ti.inc| 3 +++
 2 files changed, 5 insertions(+)

diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb 
b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
index 79166ca9..196b11b9 100644
--- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
+++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
@@ -26,3 +26,5 @@ do_install() {
 FILES_${PN} += "${base_libdir}/firmware"
 
 COMPATIBLE_MACHINE = "(ti-soc)"
+TOOLCHAIN = "gcc"
+
diff --git a/recipes-bsp/u-boot/u-boot-ti.inc b/recipes-bsp/u-boot/u-boot-ti.inc
index b66a7a6f..36746826 100644
--- a/recipes-bsp/u-boot/u-boot-ti.inc
+++ b/recipes-bsp/u-boot/u-boot-ti.inc
@@ -370,3 +370,6 @@ do_deploy_append_keystone () {
fi
fi
 }
+
+TOOLCHAIN = "gcc"
+
-- 
2.22.0

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

[meta-ti] [PATCH 4/4] jailhouse: Pin to TI SOCs

[Khem Raj]

This needs to be ported and tested with non-TI SOCs
its better to limit this to just TI SOCs as of now
this makes sure that meta-ti can be used in a multi-BSP
distro

Signed-off-by: Khem Raj 
---
 recipes-kernel/jailhouse/jailhouse_git.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
b/recipes-kernel/jailhouse/jailhouse_git.bb
index db31bb7d..919c75d9 100644
--- a/recipes-kernel/jailhouse/jailhouse_git.bb
+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
@@ -32,6 +32,7 @@ require jailhouse-arch.inc
 inherit module pythonnative bash-completion deploy
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_MACHINE = "(ti-soc)"
 
 JH_DATADIR ?= "${datadir}/jailhouse"
 JH_EXEC_DIR ?= "${libexecdir}/jailhouse"
-- 
2.22.0

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

[meta-ti] [PATCH 3/4] jailhouse: Replace tabs with spaces in python code

[Khem Raj]

Fixes
WARNING: python should use 4 spaces indentation, but found tabs in 
jailhouse_git.bb, line 85

Signed-off-by: Khem Raj 
---
 recipes-kernel/jailhouse/jailhouse_git.bb | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/recipes-kernel/jailhouse/jailhouse_git.bb 
b/recipes-kernel/jailhouse/jailhouse_git.bb
index 753664ed..db31bb7d 100644
--- a/recipes-kernel/jailhouse/jailhouse_git.bb
+++ b/recipes-kernel/jailhouse/jailhouse_git.bb
@@ -82,10 +82,10 @@ do_compile() {
 }
 
 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')
+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')
 }
 
 do_install() {
-- 
2.22.0

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

[meta-ti] [PATCH 2/4] jailhouse: Limit OE architectures to supported ones

[Khem Raj]

Fixes
ERROR: cannot map 'mips' to a jailhouse supported architecture

Signed-off-by: Khem Raj 
---
 recipes-kernel/jailhouse/jailhouse-arch.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-kernel/jailhouse/jailhouse-arch.inc 
b/recipes-kernel/jailhouse/jailhouse-arch.inc
index e06ec231..0546fa26 100644
--- a/recipes-kernel/jailhouse/jailhouse-arch.inc
+++ b/recipes-kernel/jailhouse/jailhouse-arch.inc
@@ -18,3 +18,6 @@ def map_jh_arch(a, d):
 bb.error("cannot map '%s' to a jailhouse supported architecture" % a)
 
 export JH_ARCH = "${@map_jh_arch(d.getVar('TARGET_ARCH', True), d)}"
+
+COMPATIBLE_HOST = "(i.86|x86_64|arm|aarch64).*-linux"
+
-- 
2.22.0

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

[meta-ti] [PATCH 1/4] ti-display-sharing-fw: Do not strip during staging sysroot stage

[Khem Raj]

Fixes build with non arm architectures

Subprocess output:x86_64-yoe-linux-strip: Unable to recognise the format of the 
input file 
`TOPDIR/build/tmpfs/work/qemux86_64-yoe-linux/ti-display-sharing-fw/00.09.00.00-gitAUTOINC+4a86f16df9-r0/sysroot-destdir/lib/firmware/ti-display-sharing-j721e.bin'

Signed-off-by: Khem Raj 
---
 recipes-bsp/ti-display-sharing-fw/ti-display-sharing-fw_git.bb | 2 ++
 1 file changed, 2 insertions(+)

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 675b3f2c..db095d90 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
@@ -36,6 +36,8 @@ ALTERNATIVE_PRIORITY = "9"
 
 # This is used to prevent the build system to strip the executables
 INHIBIT_PACKAGE_STRIP = "1"
+INHIBIT_SYSROOT_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
-- 
2.22.0

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

Re: [meta-ti] [PATCH V3] ti-display-sharing: add recipe for fw integration

[Khem Raj]

This fails to build for mips arch see

https://errors.yoctoproject.org/Errors/Details/251213/

please mark this recipe either arm or ti soc specific

this will help meta-ti in multi-BSP distros.

On Tue, Jul 2, 2019 at 11:18 AM Subhajit Paul  wrote:
>
> Signed-off-by: Subhajit Paul 
> Reviewed-by: Dan Murphy 
> ---
>  .../ti-display-sharing-firmware_git.bb | 46 
> ++
>  1 file changed, 46 insertions(+)
>  create mode 100644 
> recipes-bsp/ti-display-sharing-fw/ti-display-sharing-firmware_git.bb
>
> diff --git 
> a/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-firmware_git.bb 
> b/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-firmware_git.bb
> new file mode 100644
> index 000..675b3f2
> --- /dev/null
> +++ b/recipes-bsp/ti-display-sharing-fw/ti-display-sharing-firmware_git.bb
> @@ -0,0 +1,46 @@
> +SUMMARY = "TI Display Sharing Firmware"
> +
> +LICENSE = "TI-TFL"
> +LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=b5aebf0668bdf95621259288c4a46d76"
> +
> +PV = "00.09.00.00-git${SRCPV}"
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +inherit deploy
> +inherit update-alternatives
> +
> +PROTOCOL = "git"
> +BRANCH = "ti-linux-firmware"
> +SRCREV = "4a86f16df9b44798851e51fa465825710cda76cf"
> +
> +SRC_URI = 
> "git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=${PROTOCOL};branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +TI_DISP_SHARE_FW_DIR = "${S}/ti-display-sharing/"
> +TI_DISP_SHARE_FW_FILENAME = "ti-display-sharing-j721e.bin"
> +
> +# 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 ${TI_DISP_SHARE_FW_DIR}/${TI_DISP_SHARE_FW_FILENAME} 
> ${D}${base_libdir}/firmware
> +}
> +
> +TARGET_MAIN_R5FSS0_1 = "j7-main-r5f0_1-fw"
> +ALTERNATIVE_${PN} = "j7-main-r5f0_1-fw"
> +ALTERNATIVE_LINK_NAME[j7-main-r5f0_1-fw] = 
> "${base_libdir}/firmware/${TARGET_MAIN_R5FSS0_1}"
> +ALTERNATIVE_TARGET[j7-main-r5f0_1-fw] = 
> "${base_libdir}/firmware/${TI_DISP_SHARE_FW_FILENAME}"
> +ALTERNATIVE_PRIORITY = "9"
> +
> +# 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"
> +
> +# we don't want to configure and build the source code
> +do_compile[noexec] = "1"
> +do_configure[noexec] = "1"
> --
> 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 v1] jailhouse: add recipe for Jailhouse module, FW, cells, inmates and basic demo

[Khem Raj]

Can we make this arm specific or ti soc specific whatever is relevant ?

This fails to build for mips arch see

https://errors.yoctoproject.org/Errors/Details/251212/

On Fri, Jul 5, 2019 at 1:57 AM Nikhil Devshatwar  wrote:
>
> From: Denys Dmytriyenko 
>
> Builds the Jailhouse kernel module, hypervisor binaries
> and all the cell configs for root cell and other demos.
> Generate the linux-demo loader script without initramfs.
>
> Supports am65x and j7-evm machines
>
> [nikhil...@ti.com: Update for public trees]
>
> Signed-off-by: Denys Dmytriyenko 
> Signed-off-by: Nikhil Devshatwar 
> ---
>  recipes-bsp/jailhouse/jailhouse-arch.inc   |  20 +++
>  .../jailhouse/0001-Makefile-fixes-for-yocto.patch  |  84 
>  recipes-bsp/jailhouse/jailhouse_git.bb | 144 
> +
>  3 files changed, 248 insertions(+)
>  create mode 100644 recipes-bsp/jailhouse/jailhouse-arch.inc
>  create mode 100644 
> recipes-bsp/jailhouse/jailhouse/0001-Makefile-fixes-for-yocto.patch
>  create mode 100644 recipes-bsp/jailhouse/jailhouse_git.bb
>
> diff --git a/recipes-bsp/jailhouse/jailhouse-arch.inc 
> b/recipes-bsp/jailhouse/jailhouse-arch.inc
> new file mode 100644
> index 000..e06ec23
> --- /dev/null
> +++ b/recipes-bsp/jailhouse/jailhouse-arch.inc
> @@ -0,0 +1,20 @@
> +# Set jailhouse architecture JH_ARCH variable
> +#
> +# return value must match one of architectures supported by jailhouse
> +#
> +valid_jh_archs = "x86 arm"
> +
> +def map_jh_arch(a, d):
> +import re
> +
> +valid_jh_archs = d.getVar('valid_jh_archs', True).split()
> +
> +if   re.match('(i.86|athlon|x86.64)$', a):  return 'x86'
> +elif re.match('armeb$', a): return 'arm'
> +elif re.match('aarch64$', a):   return 'arm64'
> +elif re.match('aarch64_be$', a):return 'arm64'
> +elif a in valid_jh_archs:   return a
> +else:
> +bb.error("cannot map '%s' to a jailhouse supported architecture" % a)
> +
> +export JH_ARCH = "${@map_jh_arch(d.getVar('TARGET_ARCH', True), d)}"
> diff --git 
> a/recipes-bsp/jailhouse/jailhouse/0001-Makefile-fixes-for-yocto.patch 
> b/recipes-bsp/jailhouse/jailhouse/0001-Makefile-fixes-for-yocto.patch
> new file mode 100644
> index 000..3f71761
> --- /dev/null
> +++ b/recipes-bsp/jailhouse/jailhouse/0001-Makefile-fixes-for-yocto.patch
> @@ -0,0 +1,84 @@
> +From a079feba07435c73b294202fb56b2d425d107ca5 Mon Sep 17 00:00:00 2001
> +From: Nikhil Devshatwar 
> +Date: Fri, 5 Jul 2019 13:35:25 +0530
> +Subject: [PATCH] Makefile fixes for yocto
> +
> +Fix some LDFLAG in the toplevel Kbuild
> +
> +Avoid building and installing tools.
> +It has many dependencies on python, pyjailhouse, man pages,
> +bash completion, etc
> +
> +Signed-off-by: Nikhil Devshatwar 
> +---
> + Kbuild | 2 +-
> + Makefile   | 4 
> + tools/Makefile | 8 
> + 3 files changed, 5 insertions(+), 9 deletions(-)
> +
> +diff --git a/Kbuild b/Kbuild
> +index 7cbde52..054e068 100644
> +--- a/Kbuild
>  b/Kbuild
> +@@ -51,7 +51,7 @@ GEN_PCI_DEFS_PY := $(obj)/pyjailhouse/pci_defs.py
> + $(GEN_PCI_DEFS_PY): $(src)/scripts/gen_pci_defs.sh
> +   $(call if_changed,gen_pci_defs)
> +
> +-subdir-y := driver hypervisor configs inmates tools
> ++subdir-y := driver hypervisor configs inmates
> +
> + subdir-ccflags-y := -Werror
> +
> +diff --git a/Makefile b/Makefile
> +index 7401739..546be35 100644
> +--- a/Makefile
>  b/Makefile
> +@@ -53,10 +53,6 @@ tool_inmates_install: $(DESTDIR)$(libexecdir)/jailhouse
> +   $(INSTALL_DATA) inmates/tools/$(ARCH)/*.bin $<
> +
> + install: modules_install firmware_install tool_inmates_install
> +-  $(Q)$(MAKE) -C tools $@ src=.
> +-ifeq ($(strip $(PYTHON_PIP_USABLE)), yes)
> +-  $(PIP) install --upgrade --force-reinstall $(PIP_ROOT) .
> +-endif
> +
> + .PHONY: modules_install install clean firmware_install modules tools docs \
> +   docs_clean
> +diff --git a/tools/Makefile b/tools/Makefile
> +index 08fd361..b5c117d 100644
> +--- a/tools/Makefile
>  b/tools/Makefile
> +@@ -23,7 +23,6 @@ KBUILD_CFLAGS := -g -O3 -DLIBEXECDIR=\"$(libexecdir)\" \
> +   -D__LINUX_COMPILER_TYPES_H \
> +   -DJAILHOUSE_VERSION=\"$(shell cat $(src)/../VERSION)\" $(EXTRA_CFLAGS)
> + # prior to 4.19
> +-LDFLAGS :=
> + # since 4.19
> + KBUILD_LDFLAGS :=
> +
> +@@ -101,7 +100,7 @@ endef
> + targets += jailhouse.o
> +
> + $(obj)/jailhouse: $(obj)/jailhouse.o
> +-  $(call if_changed,ld)
> ++  $(LD) $(LDFLAGS) -o $@ $^
> +
> + CFLAGS_jailhouse-gcov-extract.o   := -I$(src)/../hypervisor/include \
> +   -I$(src)/../hypervisor/arch/$(SRCARCH)/include
> +@@ -112,10 +111,11 @@ targets += jailhouse-gcov-extract.o
> + always += jailhouse-gcov-extract
> +
> + $(obj)/jailhouse-gcov-extract: $(obj)/jailhouse-gcov-extract.o
> +-  $(call if_changed,ld)
> ++  $(LD) $(LDFLAGS) -o $@ $^
> +
> + $(obj)/jailhouse-config-collect: $(src)/jailhouse-config-create 
> 

Re: [meta-ti] [thud][PATCH] ti-img-encode-decode: Add the ti-img-encode-decode recipe

[Khem Raj]

On Thu, Jun 20, 2019 at 6:37 PM Angela Stegmaier  wrote:
>
> Add the recipe for the video decoder driver.
>

this should be marked with TI specific COMPATIBLE_MACHINE as well.
Since it might not work well in a multi-BSP environment

> Signed-off-by: David Huang 
> Signed-off-by: Angela Stegmaier 
> ---
>
> Note: This recipe depends on the linux kernel having the patches from the
> multimedia feature tree merged.
>
>
>  .../ti-img-encode-decode_1.0.0.bb  | 23 
> ++
>  1 file changed, 23 insertions(+)
>  create mode 100644 
> recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb
>
> diff --git a/recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb 
> b/recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb
> new file mode 100644
> index 000..65c3b67
> --- /dev/null
> +++ b/recipes-bsp/ti-img-encode-decode/ti-img-encode-decode_1.0.0.bb
> @@ -0,0 +1,23 @@
> +SUMMARY = "Kernel drivers for the IMG VXE384 MP2 and D5520 encoder/decoder 
> found in TI SoCs"
> +LICENSE = "GPLv2"
> +LIC_FILES_CHKSUM = 
> "file://common/dq.c;beginline=1;endline=16;md5=e015e28ff5e88576dab9fdf641e3dbfe"
> +
> +inherit module
> +
> +MACHINE_KERNEL_PR_append = "a"
> +PR = "${MACHINE_KERNEL_PR}"
> +
> +SRCREV = "306e85edce7969a4e017e12759be7ed763fda95c"
> +
> +EXTRA_OEMAKE = "KPATH=${STAGING_KERNEL_DIR} KCONF=${STAGING_KERNEL_BUILDDIR}"
> +TARGET_CC_ARCH += "${LDFLAGS}"
> +
> +BRANCH = "master"
> +SRC_URI = 
> "git://git.ti.com/jacinto7_multimedia/ti-img-encode-decode.git;protocol=git;branch=${BRANCH}"
> +
> +S = "${WORKDIR}/git"
> +
> +do_install() {
> +   install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> +   install -m 644 ${S}/vxd-dec.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] [PATCH] beaglebone-capes: Update checksums for LICENSE

[Khem Raj]

OE-Core has reworded the license file see
https://git.openembedded.org/openembedded-core/commit/?id=f8c9c511b5f1b7dbd45b77f345cb6c048ae6763e

Signed-off-by: Khem Raj 
---
 recipes-ti/beagleboard/beaglebone-capes.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-ti/beagleboard/beaglebone-capes.bb 
b/recipes-ti/beagleboard/beaglebone-capes.bb
index e74033a1..30b985b5 100644
--- a/recipes-ti/beagleboard/beaglebone-capes.bb
+++ b/recipes-ti/beagleboard/beaglebone-capes.bb
@@ -1,7 +1,7 @@
 DESCRIPTION = "Userspace setup for beaglebone capes"
 
 LICENSE = "MIT"
-LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=4d92cd373abda3937c2bc47fbc49d690"
+LIC_FILES_CHKSUM = 
"file://${COREBASE}/LICENSE;md5=b97a012949927931feb7793eee5ed924 "
 
 PR = "r4"
 
-- 
2.21.0

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

Re: [meta-ti] [rocko/master][PATCH v2] gcc-arm-none-eabi: extend to nativesdk class

[Khem Raj]

On Fri, Mar 1, 2019 at 7:07 AM Denys Dmytriyenko  wrote:
>
> On Fri, Mar 01, 2019 at 06:54:50AM -0800, Khem Raj wrote:
> > On Fri, Feb 22, 2019 at 12:33 PM Jacob Stiffler  wrote:
> > >
> > > Signed-off-by: Jacob Stiffler 
> > > ---
> > > v2 changes:
> > > * Use COMPATIBLE_HOST instead of anonymous python to limit to x86_64-linux
> > >
> > >  ..._6-2017-q1-update.bb => gcc-arm-none-eabi_6-2017-q1-update.bb} | 8 
> > > ++--
> > >  1 file changed, 6 insertions(+), 2 deletions(-)
> > >  rename recipes-ti/devtools/{gcc-arm-none-eabi-native_6-2017-q1-update.bb 
> > > => gcc-arm-none-eabi_6-2017-q1-update.bb} (83%)
> > >
> > > diff --git 
> > > a/recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb 
> > > b/recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb
> > > similarity index 83%
> > > rename from 
> > > recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb
> > > rename to recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb
> > > index 1140f27..ae3d1d7 100644
> > > --- a/recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb
> > > +++ b/recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb
> > > @@ -3,7 +3,6 @@ LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
> > >
> > >  LIC_FILES_CHKSUM = 
> > > "file://share/doc/gcc-arm-none-eabi/license.txt;md5=c224e429f53a1a6ce70bf8986ea2990b"
> > >
> > > -inherit native
> >
> > this means it is also available as target package now.
>
> Yes, hence COMPATIBLE_HOST below. Also see earlier discussion on v1 of the
> patch for other considered options.
>
>
> > >  require recipes-ti/includes/ti-paths.inc
> > >
> > >  SRC_URI = 
> > > "https://developer.arm.com/-/media/Files/downloads/gnu-rm/6_1-2017q1/gcc-arm-none-eabi-6-2017-q1-update-linux.tar.bz2;name=gcc-arm-none;
> > > @@ -13,6 +12,9 @@ SRC_URI[gcc-arm-none.sha256sum] = 
> > > "e7aad2579f02e3b095c6d7899ca5e6a70cfa9b8a8cbd6
> > >
> > >  S = "${WORKDIR}/gcc-arm-none-eabi-6-2017-q1-update"
> > >
> > > +# only x86_64 is supported
> > > +COMPATIBLE_HOST = "x86_64.*-linux"
> > > +
> >
> > fails on qemux86-64
> > https://errors.yoctoproject.org/Errors/Details/230712/
>
> The errors are from package_qa and seem to be due to binary nature of the
> package and RDEPENDS between libraries.
>
>
> > you have to limit its availability to native and nativesdk only.
>
> While intension of COMPATIBLE_HOST was to limit it to native and nativesdk
> indirectly, x86-64 target does also match. And theoretically it can be a valid
> use case for this bare-metal Arm cross-compile toolchain... I wonder if simply
> skipping "file-rdeps" QA checks would be fine.
>

If you dont intend to support this usecase, then I would suggest to
keep it limited to what you intend to support. Either way this is a
regression which should be fixed

>
> > >  do_install() {
> > >  install -d ${D}${GCC_ARM_NONE_TOOLCHAIN_RECIPE}
> > >  cp -r ${S}/. ${D}${GCC_ARM_NONE_TOOLCHAIN_RECIPE}
> > > @@ -20,4 +22,6 @@ do_install() {
> > >
> > >  FILES_${PN} = "${GCC_ARM_NONE_TOOLCHAIN_RECIPE}/*"
> > >
> > > -INSANE_SKIP_${PN} = "already-stripped"
> > > +INSANE_SKIP_${PN} = "already-stripped libdir staticdev"
> > > +
> > > +BBCLASSEXTEND = "native nativesdk"
> > > --
> > > 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 mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [rocko/master][PATCH v2] gcc-arm-none-eabi: extend to nativesdk class

[Khem Raj]

On Fri, Feb 22, 2019 at 12:33 PM Jacob Stiffler  wrote:
>
> Signed-off-by: Jacob Stiffler 
> ---
> v2 changes:
> * Use COMPATIBLE_HOST instead of anonymous python to limit to x86_64-linux
>
>  ..._6-2017-q1-update.bb => gcc-arm-none-eabi_6-2017-q1-update.bb} | 8 
> ++--
>  1 file changed, 6 insertions(+), 2 deletions(-)
>  rename recipes-ti/devtools/{gcc-arm-none-eabi-native_6-2017-q1-update.bb => 
> gcc-arm-none-eabi_6-2017-q1-update.bb} (83%)
>
> diff --git a/recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb 
> b/recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb
> similarity index 83%
> rename from recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb
> rename to recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb
> index 1140f27..ae3d1d7 100644
> --- a/recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb
> +++ b/recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb
> @@ -3,7 +3,6 @@ LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
>
>  LIC_FILES_CHKSUM = 
> "file://share/doc/gcc-arm-none-eabi/license.txt;md5=c224e429f53a1a6ce70bf8986ea2990b"
>
> -inherit native

this means it is also available as target package now.

>  require recipes-ti/includes/ti-paths.inc
>
>  SRC_URI = 
> "https://developer.arm.com/-/media/Files/downloads/gnu-rm/6_1-2017q1/gcc-arm-none-eabi-6-2017-q1-update-linux.tar.bz2;name=gcc-arm-none;
> @@ -13,6 +12,9 @@ SRC_URI[gcc-arm-none.sha256sum] = 
> "e7aad2579f02e3b095c6d7899ca5e6a70cfa9b8a8cbd6
>
>  S = "${WORKDIR}/gcc-arm-none-eabi-6-2017-q1-update"
>
> +# only x86_64 is supported
> +COMPATIBLE_HOST = "x86_64.*-linux"
> +

fails on qemux86-64
https://errors.yoctoproject.org/Errors/Details/230712/

you have to limit its availability to native and nativesdk only.

>  do_install() {
>  install -d ${D}${GCC_ARM_NONE_TOOLCHAIN_RECIPE}
>  cp -r ${S}/. ${D}${GCC_ARM_NONE_TOOLCHAIN_RECIPE}
> @@ -20,4 +22,6 @@ do_install() {
>
>  FILES_${PN} = "${GCC_ARM_NONE_TOOLCHAIN_RECIPE}/*"
>
> -INSANE_SKIP_${PN} = "already-stripped"
> +INSANE_SKIP_${PN} = "already-stripped libdir staticdev"
> +
> +BBCLASSEXTEND = "native nativesdk"
> --
> 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] [PATCH V2] rwmem: Update to latest

[Khem Raj]

On Mon, Dec 17, 2018 at 11:07 AM Denys Dmytriyenko  wrote:
>
> On Mon, Dec 17, 2018 at 10:58:47AM -0800, Khem Raj wrote:
> > ping^1
>
> Yeah, I've been meaning to reply, just didn't have time.
>
> Mostly I'm fine with the update. But I don't like hidden submodules instead of
> direct dependencies. I already made pybind11 recipe for Tomi's kms++ some time
> ago (though upstreaming it to oe-core didn't work and I didn't find time to
> follow up). I haven't looked at "inih" module yet, but maybe should be a
> separate recipe as well?

thats ok but usually if they are doing static linking its better to keep
the gitsubmods or maybe at best use multiple SRC_URIs for each
component, I think its just inviting more work to keep different
recipes in sync otherwise. These new recipes may interfere with other
packages
etc.

>
> BTW, should it DEPENDS on python3 or inherit python3native?
>

its needed during runtime.

> Denys
>
>
> > On Sat, Dec 8, 2018 at 11:59 PM Khem Raj  wrote:
> > >
> > > New versions use CMake
> > > Correct detection of nm/ranlib/ar for LTO
> > >
> > > Signed-off-by: Khem Raj 
> > > ---
> > > v2: Fix nm/ar/ranlib detection needed for LTO
> > >
> > >  ...Make-provided-vars-for-ar-and-ranlib.patch | 34 +++
> > >  recipes-bsp/rwmem/rwmem_1.1.bb| 14 +---
> > >  2 files changed, 44 insertions(+), 4 deletions(-)
> > >  create mode 100644 
> > > recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
> > >
> > > 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 00000000..d72f427d
> > > --- /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: Pending
> > > +
> > > +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_1.1.bb 
> > > b/recipes-bsp/rwmem/rwmem_1.1.bb
> > > index 2848e1cd..62c33a3b 100644
> > > --- a/recipes-bsp/rwmem/rwmem_1.1.bb
> > > +++ b/recipes-bsp/rwmem/rwmem_1.1.bb
> > > @@ -2,12 +2,18 @@ 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"
> > > +SRCREV = "ad00619005654f9cde5c2ea2ed2277d1d3ad2f26"
> > > +SRC_URI = "gitsm://github.com/tomba/rwmem.git \
> > > +   file://0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch \
> > > +  "
> > >
> > >  S = "${WORKDIR}/git"
> > >
> > > +inherit cmake pkgconfig
> > > +
> > > +DEPENDS += "python3"
> > > +
> > >  do_install() {
> > > -   install -d ${D}${bindir}
> > > -   install -m 0755 rwmem ${D}${bindir}
> > > +   install -D -m 0755 ${B}/bin/rwmem ${D}${bindir}/rwmem
> > > +   install -D -m 0644 ${B}/lib/librwmem.a ${D}${libdir}/librwmem.a
> > >  }
> > > --
> > > 2.19.2
> > >
> > --
> > ___
> > 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] rwmem: Update to latest

[Khem Raj]

ping^1

On Sat, Dec 8, 2018 at 11:59 PM Khem Raj  wrote:
>
> New versions use CMake
> Correct detection of nm/ranlib/ar for LTO
>
> Signed-off-by: Khem Raj 
> ---
> v2: Fix nm/ar/ranlib detection needed for LTO
>
>  ...Make-provided-vars-for-ar-and-ranlib.patch | 34 +++
>  recipes-bsp/rwmem/rwmem_1.1.bb| 14 +---
>  2 files changed, 44 insertions(+), 4 deletions(-)
>  create mode 100644 
> recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch
>
> 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 ..d72f427d
> --- /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: Pending
> +
> +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_1.1.bb b/recipes-bsp/rwmem/rwmem_1.1.bb
> index 2848e1cd..62c33a3b 100644
> --- a/recipes-bsp/rwmem/rwmem_1.1.bb
> +++ b/recipes-bsp/rwmem/rwmem_1.1.bb
> @@ -2,12 +2,18 @@ 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"
> +SRCREV = "ad00619005654f9cde5c2ea2ed2277d1d3ad2f26"
> +SRC_URI = "gitsm://github.com/tomba/rwmem.git \
> +   file://0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch \
> +  "
>
>  S = "${WORKDIR}/git"
>
> +inherit cmake pkgconfig
> +
> +DEPENDS += "python3"
> +
>  do_install() {
> -   install -d ${D}${bindir}
> -   install -m 0755 rwmem ${D}${bindir}
> +   install -D -m 0755 ${B}/bin/rwmem ${D}${bindir}/rwmem
> +   install -D -m 0644 ${B}/lib/librwmem.a ${D}${libdir}/librwmem.a
>  }
> --
> 2.19.2
>
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [PATCH V2] rwmem: Update to latest

[Khem Raj]

New versions use CMake
Correct detection of nm/ranlib/ar for LTO

Signed-off-by: Khem Raj 
---
v2: Fix nm/ar/ranlib detection needed for LTO

 ...Make-provided-vars-for-ar-and-ranlib.patch | 34 +++
 recipes-bsp/rwmem/rwmem_1.1.bb| 14 +---
 2 files changed, 44 insertions(+), 4 deletions(-)
 create mode 100644 
recipes-bsp/rwmem/rwmem/0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch

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 ..d72f427d
--- /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: Pending
+
+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_1.1.bb b/recipes-bsp/rwmem/rwmem_1.1.bb
index 2848e1cd..62c33a3b 100644
--- a/recipes-bsp/rwmem/rwmem_1.1.bb
+++ b/recipes-bsp/rwmem/rwmem_1.1.bb
@@ -2,12 +2,18 @@ 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"
+SRCREV = "ad00619005654f9cde5c2ea2ed2277d1d3ad2f26"
+SRC_URI = "gitsm://github.com/tomba/rwmem.git \
+   file://0001-Use-CMake-provided-vars-for-ar-and-ranlib.patch \
+  "
 
 S = "${WORKDIR}/git"
 
+inherit cmake pkgconfig
+
+DEPENDS += "python3"
+
 do_install() {
-   install -d ${D}${bindir}
-   install -m 0755 rwmem ${D}${bindir}
+   install -D -m 0755 ${B}/bin/rwmem ${D}${bindir}/rwmem
+   install -D -m 0644 ${B}/lib/librwmem.a ${D}${libdir}/librwmem.a
 }
-- 
2.19.2

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

[meta-ti] [PATCH] rwmem: Update to latest

[Khem Raj]

New versions use CMake

Signed-off-by: Khem Raj 
---
 recipes-bsp/rwmem/rwmem_1.1.bb | 12 
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/recipes-bsp/rwmem/rwmem_1.1.bb b/recipes-bsp/rwmem/rwmem_1.1.bb
index 2848e1cd..24013abe 100644
--- a/recipes-bsp/rwmem/rwmem_1.1.bb
+++ b/recipes-bsp/rwmem/rwmem_1.1.bb
@@ -2,12 +2,16 @@ 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"
+SRCREV = "ad00619005654f9cde5c2ea2ed2277d1d3ad2f26"
+SRC_URI = "gitsm://github.com/tomba/rwmem.git"
 
 S = "${WORKDIR}/git"
 
+inherit cmake pkgconfig
+
+DEPENDS += "python3"
+
 do_install() {
-   install -d ${D}${bindir}
-   install -m 0755 rwmem ${D}${bindir}
+   install -D -m 0755 ${B}/bin/rwmem ${D}${bindir}/rwmem
+   install -D -m 0644 ${B}/lib/librwmem.a ${D}${libdir}/librwmem.a
 }
-- 
2.19.2

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

[meta-ti] [PATCH] uio-module-drv: Mark it to be ti SOC specific

[Khem Raj]

Fails to compile with non TI kernels

Signed-off-by: Khem Raj 
---
 recipes-bsp/uio-module-drv/uio-module-drv.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-bsp/uio-module-drv/uio-module-drv.inc 
b/recipes-bsp/uio-module-drv/uio-module-drv.inc
index 99d908ee..f483010e 100644
--- a/recipes-bsp/uio-module-drv/uio-module-drv.inc
+++ b/recipes-bsp/uio-module-drv/uio-module-drv.inc
@@ -14,3 +14,6 @@ SRC_URI = 
"${UIO_MODULE_DRV_GIT_URI};protocol=${UIO_MODULE_DRV_GIT_PROTOCOL};bra
 SRCREV = "${UIO_MODULE_DRV_SRCREV}"
 
 S = "${WORKDIR}/git"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
-- 
2.19.2

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

Re: [meta-ti] [PATCH] u-boot: Alawys build with disabled PIE

[Khem Raj]

Hi Tom

I think, it does for now. Eventually, it might be interesting to see if
u-boot could be compiled as static PIE, looking  at the code generated
by gcc for arm/beaglebone, there is additional penalty since arm gcc
is reloading pc-relative addresses, putting an extra slot in the
constant pool each time which can be significant if we use small
functions as seems to be the case in u-boot.

Thanks
-KhemOn Thu, Oct 18, 2018 at 7:09 AM Tom Rini  wrote:
>
> On Wed, Oct 17, 2018 at 10:49:46PM -0700, Khem Raj wrote:
> > some OE distros can default to hardened toolchains which means PIE is
> > added implicitly to compiler cmdline, here this options makes sure that
> > whattever the default toolchain are, u-boot is not impacted
> >
> > Fixes errors e.g.
> >
> > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not fit 
> > in region `.sram'
> > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> >
> > Signed-off-by: Khem Raj 
> > Cc: Tom Rini 
> > Cc: Denys Dmytriyenko 
> > ---
> >  .../0001-Always-build-with-fno-PIE.patch  | 35 +++
> >  .../u-boot/u-boot-ti-staging_2018.01.bb   |  2 ++
> >  2 files changed, 37 insertions(+)
> >  create mode 100644 
> > recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch
> >
> > diff --git a/recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch 
> > b/recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch
> > new file mode 100644
> > index ..dfd99c66
> > --- /dev/null
> > +++ b/recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch
> > @@ -0,0 +1,35 @@
> > +From ec81bbe3ea7e077512f4b9d2b4aa87e7f1494bcc Mon Sep 17 00:00:00 2001
> > +From: Khem Raj 
> > +Date: Wed, 17 Oct 2018 22:32:57 -0700
> > +Subject: [PATCH] Always build with -fno-PIE
> > +
> > +GNU Toolchains can be configured to generate PIE by default
> > +while PIE could be ok, it is known that u-boot/SPL on ARM starts to
> > +generate bigger code and starts to overflow the SRAM size, therefore
> > +disabling PIE explcitly insulates against toolchain intrinsic defaults
> > +
> > +Fixes errors like
> > +| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not fit 
> > in region `.sram'
> > +| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> > +
> > +Signed-off-by: Khem Raj 
> > +Cc: Tom Rini 
> > +---
> > + Makefile | 1 +
> > + 1 file changed, 1 insertion(+)
> > +
> > +diff --git a/Makefile b/Makefile
> > +index 45cd751ba3..9eb8ac564e 100644
> > +--- a/Makefile
> >  b/Makefile
> > +@@ -592,6 +592,7 @@ KBUILD_CFLAGS+= -O2
> > + endif
> > +
> > + KBUILD_CFLAGS += $(call cc-option,-fno-stack-protector)
> > ++KBUILD_CFLAGS += $(call cc-option,-fno-PIE)
> > + KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks)
> > +
> > + KBUILD_CFLAGS   += -g
> > +--
> > +2.19.1
> > +
> > diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
> > b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> > index cbb8857a..c9c97111 100644
> > --- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> > +++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> > @@ -5,3 +5,5 @@ PR = "r24"
> >  BRANCH = "ti-u-boot-2018.01"
> >
> >  SRCREV = "2cc52408bf1357f11b96548e78223a1df321c1ae"
> > +
> > +SRC_URI += "file://0001-Always-build-with-fno-PIE.patch"
>
> So does this end up being something that is appropriate to push
> upstream?  Thanks!
>
> --
> Tom
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

[meta-ti] [PATCH] u-boot: Alawys build with disabled PIE

[Khem Raj]

some OE distros can default to hardened toolchains which means PIE is
added implicitly to compiler cmdline, here this options makes sure that
whattever the default toolchain are, u-boot is not impacted

Fixes errors e.g.

| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not fit in 
region `.sram'
| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes

Signed-off-by: Khem Raj 
Cc: Tom Rini 
Cc: Denys Dmytriyenko 
---
 .../0001-Always-build-with-fno-PIE.patch  | 35 +++
 .../u-boot/u-boot-ti-staging_2018.01.bb   |  2 ++
 2 files changed, 37 insertions(+)
 create mode 100644 
recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch

diff --git a/recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch 
b/recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch
new file mode 100644
index ..dfd99c66
--- /dev/null
+++ b/recipes-bsp/u-boot/files/0001-Always-build-with-fno-PIE.patch
@@ -0,0 +1,35 @@
+From ec81bbe3ea7e077512f4b9d2b4aa87e7f1494bcc Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Wed, 17 Oct 2018 22:32:57 -0700
+Subject: [PATCH] Always build with -fno-PIE
+
+GNU Toolchains can be configured to generate PIE by default
+while PIE could be ok, it is known that u-boot/SPL on ARM starts to
+generate bigger code and starts to overflow the SRAM size, therefore
+disabling PIE explcitly insulates against toolchain intrinsic defaults
+
+Fixes errors like
+| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not fit in 
region `.sram'
+| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
+
+Signed-off-by: Khem Raj 
+Cc: Tom Rini 
+---
+ Makefile | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/Makefile b/Makefile
+index 45cd751ba3..9eb8ac564e 100644
+--- a/Makefile
 b/Makefile
+@@ -592,6 +592,7 @@ KBUILD_CFLAGS  += -O2
+ endif
+ 
+ KBUILD_CFLAGS += $(call cc-option,-fno-stack-protector)
++KBUILD_CFLAGS += $(call cc-option,-fno-PIE)
+ KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks)
+ 
+ KBUILD_CFLAGS += -g
+-- 
+2.19.1
+
diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
index cbb8857a..c9c97111 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
@@ -5,3 +5,5 @@ PR = "r24"
 BRANCH = "ti-u-boot-2018.01"
 
 SRCREV = "2cc52408bf1357f11b96548e78223a1df321c1ae"
+
+SRC_URI += "file://0001-Always-build-with-fno-PIE.patch"
-- 
2.19.1

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

Re: [meta-ti] [master][PATCH] ti-gc320-driver: workaround for gcc8 stringop-overflow error

[Khem Raj]

Ok, no problem. share errors may be I can help otherwise we do have workaround
On Wed, Oct 17, 2018 at 7:45 PM Denys Dmytriyenko  wrote:
>
> On Wed, Oct 17, 2018 at 06:53:50PM -0700, Khem Raj wrote:
> > On Wed, Oct 17, 2018 at 6:04 PM Denys Dmytriyenko  wrote:
> > >
> > > Signed-off-by: Denys Dmytriyenko 
> > > ---
> > >  ...build-bypass-gcc8-stringop-overflow-error.patch | 26 
> > > ++
> > >  .../gc320-drivers/ti-gc320-driver_5.0.11.p7.bb |  4 +++-
> > >  2 files changed, 29 insertions(+), 1 deletion(-)
> > >  create mode 100644 
> > > recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
> > >
> > > diff --git 
> > > a/recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
> > >  
> > > b/recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
> > > new file mode 100644
> > > index 000..431afa7
> > > --- /dev/null
> > > +++ 
> > > b/recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
> > > @@ -0,0 +1,26 @@
> > > +From c93a4217425ffebae1fb2d5c6c7fc957eb8aa18c Mon Sep 17 00:00:00 2001
> > > +From: Denys Dmytriyenko 
> > > +Date: Tue, 16 Oct 2018 21:16:48 -0400
> > > +Subject: [PATCH] Kbuild: bypass gcc8 stringop-overflow error
> > > +
> > > +Signed-off-by: Denys Dmytriyenko 
> > > +---
> > > + src/Kbuild | 2 +-
> > > + 1 file changed, 1 insertion(+), 1 deletion(-)
> > > +
> > > +diff --git a/src/Kbuild b/src/Kbuild
> > > +index 574a107..df4368d 100755
> > > +--- a/src/Kbuild
> > >  b/src/Kbuild
> > > +@@ -87,7 +87,7 @@ MODULE_NAME ?= galcore
> > > + CUSTOMER_ALLOCATOR_OBJS?=
> > > + ALLOCATOR_ARRAY_H_LOCATION ?= $(OS_KERNEL_DIR)/allocator/default/
> > > +
> > > +-EXTRA_CFLAGS += -Werror
> > > ++EXTRA_CFLAGS += -Werror -Wno-stringop-overflow
> > > +
> >
> > while its clear you are marking it as workaround, but this may be one
> > time when you can also fix it and it might be showing you a latent
> > issue that went unoticed in past unless you ran static analysers on
> > this code. So are
> > there many errors ? then the workaround might be ok. Otherwise may be
> > fixing the underlying cause might be a good option.
>
> Yes, I realize that. I tried fixing it, but since I'm not really familiar
> with this code, I wasn't sure about one place and decided to leave to the
> corresponding team to fix properly. For now I just needed to unbreak it.
>
>
> > > + OBJS := $(OS_KERNEL_DIR)/gc_hal_kernel_device.o \
> > > + $(OS_KERNEL_DIR)/gc_hal_kernel_linux.o \
> > > +--
> > > +2.7.4
> > > +
> > > diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb 
> > > b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > index 94485b6..e49a41f 100644
> > > --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > @@ -13,7 +13,9 @@ BRANCH = "ti-${PV}-k4.14"
> > >
> > >  SRCREV = "a36799d9329efcfff19e30e690156d5ebf7e0c55"
> > >
> > > -SRC_URI = 
> > > "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH}"
> > > +SRC_URI = 
> > > "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH}
> > >  \
> > > +   
> > > file://0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch;striplevel=2"
> > > +
> > >  S = "${WORKDIR}/git/src"
> > >
> > >  EXTRA_OEMAKE += "-f Kbuild AQROOT=${S} KERNEL_DIR=${STAGING_KERNEL_DIR} 
> > > TOOLCHAIN_PATH=${TOOLCHAIN_PATH} CROSS_COMPILE=${TARGET_PREFIX} 
> > > ARCH_TYPE=${TARGET_ARCH}"
> > > --
> > > 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][PATCH] ti-gc320-driver: workaround for gcc8 stringop-overflow error

[Khem Raj]

On Wed, Oct 17, 2018 at 6:04 PM Denys Dmytriyenko  wrote:
>
> Signed-off-by: Denys Dmytriyenko 
> ---
>  ...build-bypass-gcc8-stringop-overflow-error.patch | 26 
> ++
>  .../gc320-drivers/ti-gc320-driver_5.0.11.p7.bb |  4 +++-
>  2 files changed, 29 insertions(+), 1 deletion(-)
>  create mode 100644 
> recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
>
> diff --git 
> a/recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
>  
> b/recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
> new file mode 100644
> index 000..431afa7
> --- /dev/null
> +++ 
> b/recipes-bsp/gc320-drivers/ti-gc320-driver/0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch
> @@ -0,0 +1,26 @@
> +From c93a4217425ffebae1fb2d5c6c7fc957eb8aa18c Mon Sep 17 00:00:00 2001
> +From: Denys Dmytriyenko 
> +Date: Tue, 16 Oct 2018 21:16:48 -0400
> +Subject: [PATCH] Kbuild: bypass gcc8 stringop-overflow error
> +
> +Signed-off-by: Denys Dmytriyenko 
> +---
> + src/Kbuild | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/src/Kbuild b/src/Kbuild
> +index 574a107..df4368d 100755
> +--- a/src/Kbuild
>  b/src/Kbuild
> +@@ -87,7 +87,7 @@ MODULE_NAME ?= galcore
> + CUSTOMER_ALLOCATOR_OBJS?=
> + ALLOCATOR_ARRAY_H_LOCATION ?= $(OS_KERNEL_DIR)/allocator/default/
> +
> +-EXTRA_CFLAGS += -Werror
> ++EXTRA_CFLAGS += -Werror -Wno-stringop-overflow
> +

while its clear you are marking it as workaround, but this may be one
time when you can also fix it and it might be showing you a latent
issue that went unoticed in past unless you ran static analysers on
this code. So are
there many errors ? then the workaround might be ok. Otherwise may be
fixing the underlying cause might be a good option.

> + OBJS := $(OS_KERNEL_DIR)/gc_hal_kernel_device.o \
> + $(OS_KERNEL_DIR)/gc_hal_kernel_linux.o \
> +--
> +2.7.4
> +
> diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb 
> b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> index 94485b6..e49a41f 100644
> --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> @@ -13,7 +13,9 @@ BRANCH = "ti-${PV}-k4.14"
>
>  SRCREV = "a36799d9329efcfff19e30e690156d5ebf7e0c55"
>
> -SRC_URI = 
> "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH}"
> +SRC_URI = 
> "git://git.ti.com/graphics/ti-gc320-driver.git;protocol=git;branch=${BRANCH} \
> +   
> file://0001-Kbuild-bypass-gcc8-stringop-overflow-error.patch;striplevel=2"
> +
>  S = "${WORKDIR}/git/src"
>
>  EXTRA_OEMAKE += "-f Kbuild AQROOT=${S} KERNEL_DIR=${STAGING_KERNEL_DIR} 
> TOOLCHAIN_PATH=${TOOLCHAIN_PATH} CROSS_COMPILE=${TARGET_PREFIX} 
> ARCH_TYPE=${TARGET_ARCH}"
> --
> 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] [PATCH 3/5] u-boot: reduce the SPL `.rodata' size

[Khem Raj]

On Wed, Oct 17, 2018 at 3:34 PM Denys Dmytriyenko  wrote:

> On Wed, Oct 17, 2018 at 12:28:51PM -0700, Khem Raj wrote:
> > Fixes errors e.g.
> >
> > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
> fit in region `.sram'
> > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> >
> > Signed-off-by: Khem Raj 
> > Cc: Tom Rini 
> > Cc: Denys Dmytriyenko 
>
> Hmm, interesting email I got here... :)
>
>
> Anyway, I'm going to hold on this one for now. Let's see if we can patch
> U-boot build instead.


Just don’t hold it because of the name :)
Btw there is something in master u-boot which makes it work with gcc+pie so
we can look at that and see if there is something to be backported but it
could also mean that there are additional features that get compiled in
with ti fork which cause the size to grow and break the size barrier

>
>
>
> > ---
> >  ...vm_defconfig-Reduce-SPL-.rodata-size.patch | 36 +++
> >  .../u-boot/u-boot-ti-staging_2018.01.bb   |  2 ++
> >  2 files changed, 38 insertions(+)
> >  create mode 100644
> recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> >
> > diff --git
> a/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> > new file mode 100644
> > index ..6244a56a
> > --- /dev/null
> > +++
> b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> > @@ -0,0 +1,36 @@
> > +From 45ead566ebf63999f07e966fa4962bb9bbe3ed4a Mon Sep 17 00:00:00 2001
> > +From: Khem Raj 
> > +Date: Tue, 16 Oct 2018 17:11:13 -0700
> > +Subject: [PATCH] Disable usb-gadget usb-eth support in SPL
> > +
> > +This helps in shedding some size to fit in into SRAM
> > +
> > +Signed-off-by: Khem Raj 
> > +---
> > + configs/am335x_evm_defconfig | 5 ++---
> > + 1 file changed, 2 insertions(+), 3 deletions(-)
> > +
> > +diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
> > +index 4908099431..8342089dee 100644
> > +--- a/configs/am335x_evm_defconfig
> >  b/configs/am335x_evm_defconfig
> > +@@ -12,14 +12,13 @@ CONFIG_SYS_CONSOLE_INFO_QUIET=y
> > + CONFIG_VERSION_VARIABLE=y
> > + CONFIG_ARCH_MISC_INIT=y
> > + CONFIG_SPL=y
> > +-CONFIG_SPL_ETH_SUPPORT=y
> > ++# CONFIG_SPL_ENV_SUPPORT is not set
> > + CONFIG_SPL_MTD_SUPPORT=y
> > + CONFIG_SPL_MUSB_NEW_SUPPORT=y
> > + CONFIG_SPL_NET_SUPPORT=y
> > + CONFIG_SPL_NET_VCI_STRING="AM335x U-Boot SPL"
> > + CONFIG_SPL_OS_BOOT=y
> > +-CONFIG_SPL_USB_GADGET_SUPPORT=y
> > +-CONFIG_SPL_USBETH_SUPPORT=y
> > ++# CONFIG_SPL_YMODEM_SUPPORT is not set
> > + CONFIG_FASTBOOT=y
> > + CONFIG_CMD_SPL=y
> > + CONFIG_CMD_SPL_NAND_OFS=0x0008
> > +--
> > +2.19.1
> > +
> > diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> > index cbb8857a..46a26480 100644
> > --- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> > +++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
> > @@ -5,3 +5,5 @@ PR = "r24"
> >  BRANCH = "ti-u-boot-2018.01"
> >
> >  SRCREV = "2cc52408bf1357f11b96548e78223a1df321c1ae"
> > +
> > +SRC_URI +=
> "file://0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch"
> > --
> > 2.19.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 2/5] recips: Mark more recipes to be ti-soc specific

[Khem Raj]

On Wed, Oct 17, 2018 at 1:11 PM Denys Dmytriyenko  wrote:

> On Wed, Oct 17, 2018 at 12:28:50PM -0700, Khem Raj wrote:
> > Signed-off-by: Khem Raj 
> > ---
> >  recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb | 3 +++
> >  recipes-bsp/cmem/cmem.inc   | 2 ++
> >  recipes-ti/devtools/ti-xdctools-common.inc  | 5 +
> >  recipes-ti/osal/ti-osal.inc | 4 
> >  4 files changed, 14 insertions(+)
> >
> > diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> > index 93cebd71..e1f21054 100644
> > --- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> > +++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
> > @@ -24,3 +24,6 @@ do_install() {
> >  }
> >
> >  FILES_${PN} += "${base_libdir}/firmware"
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti33x = "(.*)"
>
> This is incorrect - it's not limited to ti33x soc, but multiple socs with
> Cortex-M3 used for PM...


Ok tell me which ones and we can add compatible host statements may be
ti-soc is right if it is on all socs

>
>
>
> > +
>
> I noticed bunch of "new blank line at EOF" from git, so I'm cleaning it up
> and
> while at it, I'll squash these 2 similar patches...
>
>
> > diff --git a/recipes-bsp/cmem/cmem.inc b/recipes-bsp/cmem/cmem.inc
> > index 11cebe8d..abbf2492 100644
> > --- a/recipes-bsp/cmem/cmem.inc
> > +++ b/recipes-bsp/cmem/cmem.inc
> > @@ -12,3 +12,5 @@ PV = "4.15.00.02+git${SRCPV}"
> >  SRC_URI = "git://git.ti.com/ipc/ludev.git;protocol=git;branch=${BRANCH}
> <http://git.ti.com/ipc/ludev.git;protocol=git;branch=$%7BBRANCH%7D>"
> >
> >  S = "${WORKDIR}/git"
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > diff --git a/recipes-ti/devtools/ti-xdctools-common.inc
> b/recipes-ti/devtools/ti-xdctools-common.inc
> > index a3949cad..0e86ef7a 100644
> > --- a/recipes-ti/devtools/ti-xdctools-common.inc
> > +++ b/recipes-ti/devtools/ti-xdctools-common.inc
> > @@ -61,3 +61,8 @@ libhpi.so \
> >  lib.so \
> >  libcairo.so.2 \
> >  "
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > +COMPATIBLE_HOST_class-native = "(.*)"
> > +COMPATIBLE_HOST_class-nativesdk = "(.*)"
> > +
> > diff --git a/recipes-ti/osal/ti-osal.inc b/recipes-ti/osal/ti-osal.inc
> > index cb8da354..bbbdf517 100644
> > --- a/recipes-ti/osal/ti-osal.inc
> > +++ b/recipes-ti/osal/ti-osal.inc
> > @@ -19,3 +19,7 @@ INSANE_SKIP_${PN}-dev = "staticdev"
> >
> >  ALLOW_EMPTY_${PN} = "1"
> >  FILES_${PN}-dev += "${OSAL_INSTALL_DIR_RECIPE}"
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > +
> > --
> > 2.19.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] [PATCH V2 4/5] beaglebone.conf: Package kernel and devicetree

[Khem Raj]

Use variables from upstream u-boot, makes it easy to switch to
mainline u-boot from oe-core if someone wants to

Use SPL_BINARY and UBOOT_SUFFIX to define IMAGE_BOOT_FILES

Signed-off-by: Khem Raj 
---
V2: Use SPL_BINARY var

 conf/machine/beaglebone.conf | 12 +---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 25147926..36920673 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -1,6 +1,6 @@
 #@TYPE: Machine
 #@NAME: BeagleBone machine
-#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board 
+#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
 require conf/machine/include/ti33x.inc
 
@@ -17,10 +17,16 @@ SERIAL_CONSOLE = "115200 ttyS0"
 #UBOOT_MACHINE = "am335x_boneblack_config"
 
 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"
+IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} ${SPL_BINARY}"
+
+IMAGE_FSTYPES += "tar.xz wic.xz"
 
 # Refine the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_BOARDS = "bbbAM335x"
+
+SPL_BINARY = "MLO"
+UBOOT_SUFFIX = "img"
+
+IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
-- 
2.19.1

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

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Wed, Oct 17, 2018 at 12:37 PM Denys Dmytriyenko  wrote:
>
> On Wed, Oct 17, 2018 at 12:27:19PM -0700, Khem Raj wrote:
> > On Wed, Oct 17, 2018 at 12:25 PM Denys Dmytriyenko  wrote:
> > > > > > Yeah I saw that but this patch is not their in 2018.01 release that 
> > > > > > TI
> > > > > fork
> > > > > > is based on regardless I backported this patch to this version it 
> > > > > > did not
> > > > > > bring the size below mark
> > > > > > I think it’s because we are using hardened toolchain and that 
> > > > > > enalbles
> > > > > > extra options to enable pie and ssp since these options get added 
> > > > > > to CC
> > > > > > they get passed into uboot straight
> > > > > >
> > > > > > I think we should just disable security flags for u boot in OE and 
> > > > > > may be
> > > > > > uboot make system should append fno-pie fno-stack-protector to 
> > > > > > nullify
> > > > > > these options
> > > > >
> > > > > OK, do you want to submit a patch for that or should I do one and just
> > > > > Suggested-by you?  Thanks!
> > > >
> > > >Yes, that's right.
> > > > This would not be acceptable change since it changes how we build gcc
> > > > itself secondly it does not happen for master uboot
> > > >
> > > > However if this works then we need to understand why it increas e the 
> > > > size
> > >
> > > Even if this change is not acceptable upstream, I would prefer it locally 
> > > in
> > > meta-ti recipe, instead of disabling more features to free up 5-6KB in 
> > > SPL.
> >
> > this is a distro level change. meta-ti is not appropriate place to decide 
> > that
>
> Are we talking about passing fno-pie and fno-stack-protector to U-boot build
> that you suggested above? That is what I'm referring here. It can be BBB
> specific patch. That is until we figure out why it grows code so much...
>
oh I confused it with GCCPIE

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

[meta-ti] [PATCH 4/5] beaglebone.conf: Package kernel and devicetree

[Khem Raj]

Use variables from upstream u-boot, makes it easy to switch to
mainline u-boot from oe-core if someone wants to

Signed-off-by: Khem Raj 
---
 conf/machine/beaglebone.conf | 12 +---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 25147926..9b656d01 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -1,6 +1,6 @@
 #@TYPE: Machine
 #@NAME: BeagleBone machine
-#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board 
+#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
 require conf/machine/include/ti33x.inc
 
@@ -17,10 +17,16 @@ SERIAL_CONSOLE = "115200 ttyS0"
 #UBOOT_MACHINE = "am335x_boneblack_config"
 
 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"
+IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO"
+
+IMAGE_FSTYPES += "tar.xz wic.xz"
 
 # Refine the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_BOARDS = "bbbAM335x"
+
+SPL_BINARY = "MLO"
+UBOOT_SUFFIX = "img"
+
+IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
-- 
2.19.1

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

[meta-ti] [PATCH 3/5] u-boot: reduce the SPL `.rodata' size

[Khem Raj]

Fixes errors e.g.

| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not fit in 
region `.sram'
| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes

Signed-off-by: Khem Raj 
Cc: Tom Rini 
Cc: Denys Dmytriyenko 
---
 ...vm_defconfig-Reduce-SPL-.rodata-size.patch | 36 +++
 .../u-boot/u-boot-ti-staging_2018.01.bb   |  2 ++
 2 files changed, 38 insertions(+)
 create mode 100644 
recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch

diff --git 
a/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
 
b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
new file mode 100644
index ..6244a56a
--- /dev/null
+++ 
b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
@@ -0,0 +1,36 @@
+From 45ead566ebf63999f07e966fa4962bb9bbe3ed4a Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Tue, 16 Oct 2018 17:11:13 -0700
+Subject: [PATCH] Disable usb-gadget usb-eth support in SPL
+
+This helps in shedding some size to fit in into SRAM
+
+Signed-off-by: Khem Raj 
+---
+ configs/am335x_evm_defconfig | 5 ++---
+ 1 file changed, 2 insertions(+), 3 deletions(-)
+
+diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
+index 4908099431..8342089dee 100644
+--- a/configs/am335x_evm_defconfig
 b/configs/am335x_evm_defconfig
+@@ -12,14 +12,13 @@ CONFIG_SYS_CONSOLE_INFO_QUIET=y
+ CONFIG_VERSION_VARIABLE=y
+ CONFIG_ARCH_MISC_INIT=y
+ CONFIG_SPL=y
+-CONFIG_SPL_ETH_SUPPORT=y
++# CONFIG_SPL_ENV_SUPPORT is not set
+ CONFIG_SPL_MTD_SUPPORT=y
+ CONFIG_SPL_MUSB_NEW_SUPPORT=y
+ CONFIG_SPL_NET_SUPPORT=y
+ CONFIG_SPL_NET_VCI_STRING="AM335x U-Boot SPL"
+ CONFIG_SPL_OS_BOOT=y
+-CONFIG_SPL_USB_GADGET_SUPPORT=y
+-CONFIG_SPL_USBETH_SUPPORT=y
++# CONFIG_SPL_YMODEM_SUPPORT is not set
+ CONFIG_FASTBOOT=y
+ CONFIG_CMD_SPL=y
+ CONFIG_CMD_SPL_NAND_OFS=0x0008
+-- 
+2.19.1
+
diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
index cbb8857a..46a26480 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
@@ -5,3 +5,5 @@ PR = "r24"
 BRANCH = "ti-u-boot-2018.01"
 
 SRCREV = "2cc52408bf1357f11b96548e78223a1df321c1ae"
+
+SRC_URI += "file://0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch"
-- 
2.19.1

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

[meta-ti] [PATCH 5/5] beaglebone.conf: SERIAL_CONSOLE has been deprecated

[Khem Raj]

Signed-off-by: Khem Raj 
---
 conf/machine/beaglebone.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 9b656d01..f1818578 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -11,7 +11,7 @@ KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblue.dtb \
 # Only has DVI connector for external screen
 MACHINE_GUI_CLASS = "bigscreen"
 
-SERIAL_CONSOLE = "115200 ttyS0"
+SERIAL_CONSOLES = "115200;ttyS0"
 
 # fall back on generic am335x_evm_config for now
 #UBOOT_MACHINE = "am335x_boneblack_config"
-- 
2.19.1

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

[meta-ti] [PATCH 2/5] recips: Mark more recipes to be ti-soc specific

[Khem Raj]

Signed-off-by: Khem Raj 
---
 recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb | 3 +++
 recipes-bsp/cmem/cmem.inc   | 2 ++
 recipes-ti/devtools/ti-xdctools-common.inc  | 5 +
 recipes-ti/osal/ti-osal.inc | 4 
 4 files changed, 14 insertions(+)

diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb 
b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
index 93cebd71..e1f21054 100644
--- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
+++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
@@ -24,3 +24,6 @@ do_install() {
 }
 
 FILES_${PN} += "${base_libdir}/firmware"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti33x = "(.*)"
+
diff --git a/recipes-bsp/cmem/cmem.inc b/recipes-bsp/cmem/cmem.inc
index 11cebe8d..abbf2492 100644
--- a/recipes-bsp/cmem/cmem.inc
+++ b/recipes-bsp/cmem/cmem.inc
@@ -12,3 +12,5 @@ PV = "4.15.00.02+git${SRCPV}"
 SRC_URI = "git://git.ti.com/ipc/ludev.git;protocol=git;branch=${BRANCH}"
 
 S = "${WORKDIR}/git"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-ti/devtools/ti-xdctools-common.inc 
b/recipes-ti/devtools/ti-xdctools-common.inc
index a3949cad..0e86ef7a 100644
--- a/recipes-ti/devtools/ti-xdctools-common.inc
+++ b/recipes-ti/devtools/ti-xdctools-common.inc
@@ -61,3 +61,8 @@ libhpi.so \
 lib.so \
 libcairo.so.2 \
 "
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
+COMPATIBLE_HOST_class-native = "(.*)"
+COMPATIBLE_HOST_class-nativesdk = "(.*)"
+
diff --git a/recipes-ti/osal/ti-osal.inc b/recipes-ti/osal/ti-osal.inc
index cb8da354..bbbdf517 100644
--- a/recipes-ti/osal/ti-osal.inc
+++ b/recipes-ti/osal/ti-osal.inc
@@ -19,3 +19,7 @@ INSANE_SKIP_${PN}-dev = "staticdev"
 
 ALLOW_EMPTY_${PN} = "1"
 FILES_${PN}-dev += "${OSAL_INSTALL_DIR_RECIPE}"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
+
-- 
2.19.1

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

[meta-ti] [PATCH 1/5] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

This helps in multi-BSP scenario, where other BSP layers are also
present in the layermix

Signed-off-by: Khem Raj 
---
 recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
 recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
 recipes-bsp/x-load/x-load_git.bb   | 3 +++
 recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
 recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
 recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
 recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
 recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
 recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
 recipes-ti/dsplib/dsplib.inc   | 2 ++
 recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
 recipes-ti/includes/ti-unpack.inc  | 5 +
 recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
 recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
 recipes-ti/mathlib/mathlib.inc | 2 ++
 recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
 recipes-ti/swtools/swtools_git.bb  | 2 ++
 17 files changed, 46 insertions(+)

diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb 
b/recipes-bsp/cuia/cuia_1.0.0.13.bb
index e048f6aa..a7caf504 100644
--- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
+++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
@@ -23,3 +23,6 @@ do_install() {
cd ${S}
oe_runmake DESTDIR=${D} libdir=${libdir} includedir=${includedir} 
install
 }
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb 
b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
index 94485b6a..d29b6496 100644
--- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
+++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
@@ -22,3 +22,6 @@ do_install() {
 install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
 install -m 644 ${S}/galcore.ko 
${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
 }
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-bsp/x-load/x-load_git.bb b/recipes-bsp/x-load/x-load_git.bb
index dd8bce2d..1ce1b0f0 100644
--- a/recipes-bsp/x-load/x-load_git.bb
+++ b/recipes-bsp/x-load/x-load_git.bb
@@ -17,3 +17,6 @@ CONFIG_HEADER_beagleboard = "1"
 XLOAD_MACHINE_omap3-touchbook = "omap3530beagle_config"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb 
b/recipes-graphics/gbm/libgbm_10.0.0.bb
index 38715ccf..9e3c7ed0 100644
--- a/recipes-graphics/gbm/libgbm_10.0.0.bb
+++ b/recipes-graphics/gbm/libgbm_10.0.0.bb
@@ -16,3 +16,6 @@ SRC_URI = 
"git://git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH} \
 
file://0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch"
 
 S = "${WORKDIR}/git"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
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 dafaac1e..a2f8f192 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
@@ -37,3 +37,6 @@ do_install() {
 }
 
 INSANE_SKIP_${PN} += "ldflags"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-graphics/omapfbplay/omapfbplay.inc 
b/recipes-graphics/omapfbplay/omapfbplay.inc
index df166dd3..744eb8f7 100644
--- a/recipes-graphics/omapfbplay/omapfbplay.inc
+++ b/recipes-graphics/omapfbplay/omapfbplay.inc
@@ -14,6 +14,8 @@ SRC_URI = "git://git.mansr.com/omapfbplay;protocol=git \
 S = "${WORKDIR}/git"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
 
 # We want a kernel header for armv7a, but we don't want to make mplayer 
machine specific for that
 STAGING_KERNEL_DIR = 
"${STAGING_DIR}/${MACHINE_ARCH}${TARGET_VENDOR}-${TARGET_OS}/kernel"
diff --git a/recipes-multimedia/libdce/libdce_3.00.14.00.bb 
b/recipes-multimedia/libdce/libdce_3.00.14.00.bb
index 04c0b718..0deec7ab 100644
--- a/recipes-multimedia/libdce/libdce_3.00.14.00.bb
+++ b/recipes-multimedia/libdce/libdce_3.00.14.00.bb
@@ -13,3 +13,5 @@ PR = "r1"
 
 S = "${WORKDIR}/git"
 EXTRA_OECONF += "IPC_HEADERS=${STAGING_INCDIR}/ti/ipc/mm"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-ti/bios/ti-biosutils_1.02.02.bb 
b/recipes-ti/bios/ti-biosutils_1.02.02.bb
index 5b6b4f43..01c070d7 100644
--- a/recipes-ti/bios/ti-biosutils_1.02.02.bb
+++ b/recipes-ti/bios/ti-biosutils_1.02.02.bb
@@ -7,3 +7,6 @@ SRC_URI[bio

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Wed, Oct 17, 2018 at 12:25 PM Denys Dmytriyenko  wrote:
>
> On Wed, Oct 17, 2018 at 08:00:52AM -0700, Khem Raj wrote:
> > On Wed, Oct 17, 2018 at 4:26 AM Tom Rini  wrote:
> >
> > > On Tue, Oct 16, 2018 at 09:06:27PM -0700, Khem Raj wrote:
> > > > On Tue, Oct 16, 2018 at 7:39 PM  wrote:
> > > >
> > > > > Hi.
> > > > >
> > > > > > -Original Message-
> > > > > > From: Tom Rini [mailto:tr...@konsulko.com]
> > > > > > Sent: Wednesday, October 17, 2018 3:59 AM
> > > > > > To: Denys Dmytriyenko ; Yamada, Masahiro/山田 真弘
> > > > > > 
> > > > > > Cc: Khem Raj ; meta-ti@yoctoproject.org
> > > > > > Subject: Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use
> > > generic
> > > > > > am335x_evm_config for U-boot
> > > > > >
> > > > > > On Tue, Oct 16, 2018 at 02:38:28PM -0400, Denys Dmytriyenko wrote:
> > > > > > > On Tue, Oct 16, 2018 at 02:29:00PM -0400, Denys Dmytriyenko wrote:
> > > > > > > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > > > > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini 
> > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko <
> > > > > de...@ti.com>
> > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj 
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko <
> > > > > de...@ti.com>
> > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > There have been reports recently that
> > > > > am335x_beaglebone_config
> > > > > > generates bad SPL.
> > > > > > > > > > > > > > Until that is debugged and fixed, use generic
> > > > > am335x_evm_config
> > > > > > that covers all
> > > > > > > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > it fails to link
> > > > > > > > > > > > >
> > > > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section
> > > > > `.rodata'
> > > > > > will not
> > > > > > > > > > > > > fit in region `.sram'
> > > > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram'
> > > overflowed
> > > > > > by 5772 bytes
> > > > > > > > > > > > > | make[2]: ***
> > > > > >
> > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-stag
> > > > > > ing/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > > > > > > spl/u-boot-spl] Error 1
> > > > > > > > > > > >
> > > > > > > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8
> > > from
> > > > > oe-core,
> > > > > > as well as
> > > > > > > > > > > > Linaro gcc7 - no problems.
> > > > > > > > > > >
> > > > > > > > > > > My distro inherits poky policies, and on master it now
> > > inherits
> > > > > > > > > > > hardening policies ( security flags) by defaults
> > > > > > > > > > > do you happen to test poky ?
> > > > > > > > > >
> > > > > > > > > > I think we want to take a look at which of the security 
> > > > > > > > > > flags
> > > > > really
> > > > > > > > > > make sense to use in this context.  Thanks!
> &

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Wed, Oct 17, 2018 at 4:26 AM Tom Rini  wrote:

> On Tue, Oct 16, 2018 at 09:06:27PM -0700, Khem Raj wrote:
> > On Tue, Oct 16, 2018 at 7:39 PM  wrote:
> >
> > > Hi.
> > >
> > > > -Original Message-
> > > > From: Tom Rini [mailto:tr...@konsulko.com]
> > > > Sent: Wednesday, October 17, 2018 3:59 AM
> > > > To: Denys Dmytriyenko ; Yamada, Masahiro/山田 真弘
> > > > 
> > > > Cc: Khem Raj ; meta-ti@yoctoproject.org
> > > > Subject: Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use
> generic
> > > > am335x_evm_config for U-boot
> > > >
> > > > On Tue, Oct 16, 2018 at 02:38:28PM -0400, Denys Dmytriyenko wrote:
> > > > > On Tue, Oct 16, 2018 at 02:29:00PM -0400, Denys Dmytriyenko wrote:
> > > > > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini 
> > > wrote:
> > > > > > > >
> > > > > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko <
> > > de...@ti.com>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko <
> > > de...@ti.com>
> > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > There have been reports recently that
> > > am335x_beaglebone_config
> > > > generates bad SPL.
> > > > > > > > > > > > Until that is debugged and fixed, use generic
> > > am335x_evm_config
> > > > that covers all
> > > > > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > it fails to link
> > > > > > > > > > >
> > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section
> > > `.rodata'
> > > > will not
> > > > > > > > > > > fit in region `.sram'
> > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram'
> overflowed
> > > > by 5772 bytes
> > > > > > > > > > > | make[2]: ***
> > > >
> [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-stag
> > > > ing/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > > > > spl/u-boot-spl] Error 1
> > > > > > > > > >
> > > > > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8
> from
> > > oe-core,
> > > > as well as
> > > > > > > > > > Linaro gcc7 - no problems.
> > > > > > > > >
> > > > > > > > > My distro inherits poky policies, and on master it now
> inherits
> > > > > > > > > hardening policies ( security flags) by defaults
> > > > > > > > > do you happen to test poky ?
> > > > > > > >
> > > > > > > > I think we want to take a look at which of the security flags
> > > really
> > > > > > > > make sense to use in this context.  Thanks!
> > > > > > > >
> > > > > > >
> > > > > > > there could be more to it, since the distro uses thumb2 ISA by
> > > > > > > default, I am not sure
> > > > > > > if u-boot overrides that and builds using arm mode ISA always
> but
> > > > > > > something to consider, I saw several reports about u-boot
> > > overflowing
> > > > > > > sram sections and most of
> > > > > > > the solutions were "oh it works for me" or at the best your
> > > toolchain
> > > > > > > is different then mine. here is mine use it and move on.
> > > > > >
> > > > > > Khem,
> > > > > >
> > > > > > Well, FWIW, Tom and I are very familiar with this issue. As a
> matter
> > 

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

try setting #GCCPIE = "" in local.conf
On Tue, Oct 16, 2018 at 9:37 PM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 16, 2018 at 09:06:27PM -0700, Khem Raj wrote:
> > On Tue, Oct 16, 2018 at 7:39 PM  wrote:
> >
> > > Hi.
> > >
> > > > -Original Message-
> > > > From: Tom Rini [mailto:tr...@konsulko.com]
> > > > Sent: Wednesday, October 17, 2018 3:59 AM
> > > > To: Denys Dmytriyenko ; Yamada, Masahiro/山田 真弘
> > > > 
> > > > Cc: Khem Raj ; meta-ti@yoctoproject.org
> > > > Subject: Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic
> > > > am335x_evm_config for U-boot
> > > >
> > > > On Tue, Oct 16, 2018 at 02:38:28PM -0400, Denys Dmytriyenko wrote:
> > > > > On Tue, Oct 16, 2018 at 02:29:00PM -0400, Denys Dmytriyenko wrote:
> > > > > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini 
> > > wrote:
> > > > > > > >
> > > > > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko <
> > > de...@ti.com>
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko <
> > > de...@ti.com>
> > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > There have been reports recently that
> > > am335x_beaglebone_config
> > > > generates bad SPL.
> > > > > > > > > > > > Until that is debugged and fixed, use generic
> > > am335x_evm_config
> > > > that covers all
> > > > > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > it fails to link
> > > > > > > > > > >
> > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section
> > > `.rodata'
> > > > will not
> > > > > > > > > > > fit in region `.sram'
> > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed
> > > > by 5772 bytes
> > > > > > > > > > > | make[2]: ***
> > > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-stag
> > > > ing/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > > > > spl/u-boot-spl] Error 1
> > > > > > > > > >
> > > > > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from
> > > oe-core,
> > > > as well as
> > > > > > > > > > Linaro gcc7 - no problems.
> > > > > > > > >
> > > > > > > > > My distro inherits poky policies, and on master it now 
> > > > > > > > > inherits
> > > > > > > > > hardening policies ( security flags) by defaults
> > > > > > > > > do you happen to test poky ?
> > > > > > > >
> > > > > > > > I think we want to take a look at which of the security flags
> > > really
> > > > > > > > make sense to use in this context.  Thanks!
> > > > > > > >
> > > > > > >
> > > > > > > there could be more to it, since the distro uses thumb2 ISA by
> > > > > > > default, I am not sure
> > > > > > > if u-boot overrides that and builds using arm mode ISA always but
> > > > > > > something to consider, I saw several reports about u-boot
> > > overflowing
> > > > > > > sram sections and most of
> > > > > > > the solutions were "oh it works for me" or at the best your
> > > toolchain
> > > > > > > is different then mine. here is mine use it and move on.
> > > > > >
> > > > > > Khem,
> > > > > >
> > > > > > Well, FWIW,

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Tue, Oct 16, 2018 at 7:39 PM  wrote:

> Hi.
>
> > -Original Message-
> > From: Tom Rini [mailto:tr...@konsulko.com]
> > Sent: Wednesday, October 17, 2018 3:59 AM
> > To: Denys Dmytriyenko ; Yamada, Masahiro/山田 真弘
> > 
> > Cc: Khem Raj ; meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic
> > am335x_evm_config for U-boot
> >
> > On Tue, Oct 16, 2018 at 02:38:28PM -0400, Denys Dmytriyenko wrote:
> > > On Tue, Oct 16, 2018 at 02:29:00PM -0400, Denys Dmytriyenko wrote:
> > > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini 
> wrote:
> > > > > >
> > > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko <
> de...@ti.com>
> > wrote:
> > > > > > > >
> > > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko <
> de...@ti.com>
> > wrote:
> > > > > > > > > >
> > > > > > > > > > There have been reports recently that
> am335x_beaglebone_config
> > generates bad SPL.
> > > > > > > > > > Until that is debugged and fixed, use generic
> am335x_evm_config
> > that covers all
> > > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > it fails to link
> > > > > > > > >
> > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section
> `.rodata'
> > will not
> > > > > > > > > fit in region `.sram'
> > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed
> > by 5772 bytes
> > > > > > > > > | make[2]: ***
> > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-stag
> > ing/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > > spl/u-boot-spl] Error 1
> > > > > > > >
> > > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from
> oe-core,
> > as well as
> > > > > > > > Linaro gcc7 - no problems.
> > > > > > >
> > > > > > > My distro inherits poky policies, and on master it now inherits
> > > > > > > hardening policies ( security flags) by defaults
> > > > > > > do you happen to test poky ?
> > > > > >
> > > > > > I think we want to take a look at which of the security flags
> really
> > > > > > make sense to use in this context.  Thanks!
> > > > > >
> > > > >
> > > > > there could be more to it, since the distro uses thumb2 ISA by
> > > > > default, I am not sure
> > > > > if u-boot overrides that and builds using arm mode ISA always but
> > > > > something to consider, I saw several reports about u-boot
> overflowing
> > > > > sram sections and most of
> > > > > the solutions were "oh it works for me" or at the best your
> toolchain
> > > > > is different then mine. here is mine use it and move on.
> > > >
> > > > Khem,
> > > >
> > > > Well, FWIW, Tom and I are very familiar with this issue. As a matter
> > of fact,
> > > > I first encountered it almost 2 years ago and had to prove there's
> such
> > an
> > > > issue, because everyone was saying it works for them, something must
> > be wrong
> > > > with my OE builds... :)
> > > >
> > > > While .sram region is very limited, the issue is exacerbated by the
> > fact that
> > > > all debug symbols from macros like __FILE__ are ended up in that
> section
> > as
> > > > well. So, the longer your build path, the larger the section becomes.
> > Once I
> > > > had instructions to reproduce the failure here internally with a
> series
> > of
> > > > long-named nested directories like aa and bb, Nishanth
> started
> > this
> > > > thread on U-boot mailing list:
> > > > https:

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Tue, Oct 16, 2018 at 5:37 PM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 16, 2018 at 08:26:45PM -0400, Denys Dmytriyenko wrote:
> > On Tue, Oct 16, 2018 at 02:19:36PM -0700, Khem Raj wrote:
> > > On Tue, Oct 16, 2018 at 12:20 PM Khem Raj  wrote:
> > > >
> > > > On Tue, Oct 16, 2018 at 12:00 PM Denys Dmytriyenko  wrote:
> > > > >
> > > > > On Tue, Oct 16, 2018 at 11:50:36AM -0700, Khem Raj wrote:
> > > > > > On Tue, Oct 16, 2018 at 11:29 AM Denys Dmytriyenko  
> > > > > > wrote:
> > > > > > >
> > > > > > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > > > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini  
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko 
> > > > > > > > > >  wrote:
> > > > > > > > > > >
> > > > > > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko 
> > > > > > > > > > > >  wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > There have been reports recently that 
> > > > > > > > > > > > > am335x_beaglebone_config generates bad SPL.
> > > > > > > > > > > > > Until that is debugged and fixed, use generic 
> > > > > > > > > > > > > am335x_evm_config that covers all
> > > > > > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > it fails to link
> > > > > > > > > > > >
> > > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section 
> > > > > > > > > > > > `.rodata' will not
> > > > > > > > > > > > fit in region `.sram'
> > > > > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' 
> > > > > > > > > > > > overflowed by 5772 bytes
> > > > > > > > > > > > | make[2]: *** 
> > > > > > > > > > > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > > > > > spl/u-boot-spl] Error 1
> > > > > > > > > > >
> > > > > > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 
> > > > > > > > > > > from oe-core, as well as
> > > > > > > > > > > Linaro gcc7 - no problems.
> > > > > > > > > >
> > > > > > > > > > My distro inherits poky policies, and on master it now 
> > > > > > > > > > inherits
> > > > > > > > > > hardening policies ( security flags) by defaults
> > > > > > > > > > do you happen to test poky ?
> > > > > > > > >
> > > > > > > > > I think we want to take a look at which of the security flags 
> > > > > > > > > really
> > > > > > > > > make sense to use in this context.  Thanks!
> > > > > > > > >
> > > > > > > >
> > > > > > > > there could be more to it, since the distro uses thumb2 ISA by
> > > > > > > > default, I am not sure
> > > > > > > > if u-boot overrides that and builds using arm mode ISA always 
> > > > > > > > but
> > > > > > > > something to consider, I saw several reports about u-boot 
> > > > > > > > overflowing
> > > > > > > > sram sections and most of
> > > > > > > > the solutions were "oh it works for me" or at the best your 
> > > > > > >

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Tue, Oct 16, 2018 at 12:20 PM Khem Raj  wrote:
>
> On Tue, Oct 16, 2018 at 12:00 PM Denys Dmytriyenko  wrote:
> >
> > On Tue, Oct 16, 2018 at 11:50:36AM -0700, Khem Raj wrote:
> > > On Tue, Oct 16, 2018 at 11:29 AM Denys Dmytriyenko  wrote:
> > > >
> > > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini  wrote:
> > > > > >
> > > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko  
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko 
> > > > > > > > >  wrote:
> > > > > > > > > >
> > > > > > > > > > There have been reports recently that 
> > > > > > > > > > am335x_beaglebone_config generates bad SPL.
> > > > > > > > > > Until that is debugged and fixed, use generic 
> > > > > > > > > > am335x_evm_config that covers all
> > > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > it fails to link
> > > > > > > > >
> > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' 
> > > > > > > > > will not
> > > > > > > > > fit in region `.sram'
> > > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 
> > > > > > > > > 5772 bytes
> > > > > > > > > | make[2]: *** 
> > > > > > > > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > > spl/u-boot-spl] Error 1
> > > > > > > >
> > > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from 
> > > > > > > > oe-core, as well as
> > > > > > > > Linaro gcc7 - no problems.
> > > > > > >
> > > > > > > My distro inherits poky policies, and on master it now inherits
> > > > > > > hardening policies ( security flags) by defaults
> > > > > > > do you happen to test poky ?
> > > > > >
> > > > > > I think we want to take a look at which of the security flags really
> > > > > > make sense to use in this context.  Thanks!
> > > > > >
> > > > >
> > > > > there could be more to it, since the distro uses thumb2 ISA by
> > > > > default, I am not sure
> > > > > if u-boot overrides that and builds using arm mode ISA always but
> > > > > something to consider, I saw several reports about u-boot overflowing
> > > > > sram sections and most of
> > > > > the solutions were "oh it works for me" or at the best your toolchain
> > > > > is different then mine. here is mine use it and move on.
> > > >
> > > > Khem,
> > > >
> > > > Well, FWIW, Tom and I are very familiar with this issue. As a matter of 
> > > > fact,
> > > > I first encountered it almost 2 years ago and had to prove there's such 
> > > > an
> > > > issue, because everyone was saying it works for them, something must be 
> > > > wrong
> > > > with my OE builds... :)
> > > >
> > > > While .sram region is very limited, the issue is exacerbated by the 
> > > > fact that
> > > > all debug symbols from macros like __FILE__ are ended up in that 
> > > > section as
> > > > well. So, the longer your build path, the larger the section becomes. 
> > > > Once I
> > > > had instructions to reproduce the failure here internally with a series 
> > > > of
> > > > long-named nested directories like aa and bb, Nishanth started 
> > > > this
> > > > thread on U-boot mailing list:
> > > > https://lists.denx.de/pipermail/u-boot/2017-March/285031.html
> > > >
> >

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

On Tue, Oct 16, 2018 at 1:55 PM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 16, 2018 at 01:36:12PM -0700, Khem Raj wrote:
> > On Tue, Oct 16, 2018 at 12:59 PM Denys Dmytriyenko  wrote:
> > >
> > > On Tue, Oct 16, 2018 at 12:35:50PM -0700, Khem Raj wrote:
> > > > On Tue, Oct 16, 2018 at 11:33 AM Denys Dmytriyenko  wrote:
> > > > >
> > > > > On Wed, Oct 10, 2018 at 12:56:50PM -0700, Khem Raj wrote:
> > > > > > Hi Denys
> > > > > >
> > > > > > On Wed, Oct 10, 2018 at 12:36 PM Denys Dmytriyenko  
> > > > > > wrote:
> > > > > > >
> > > > > > > On Tue, Oct 09, 2018 at 03:40:40PM -0700, Khem Raj wrote:
> > > > > > > > No, it doesn't AFAICT
> > > > > > > >
> > > > > > > > On Tue, Oct 9, 2018 at 1:49 PM Denys Dmytriyenko  
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Does this make packages machine-specific?
> > > > > > > > >
> > > > > > > > > On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> > > > > > > > > > This helps in multi-BSP scenario, where other BSP layers 
> > > > > > > > > > are also
> > > > > > > > > > present in the layermix
> > > > > > >
> > > > > > > I'm not specifically against this patch, but want to understand 
> > > > > > > better - are
> > > > > > > there any specific conflicts these packages have with other BSPs?
> > > > > > >
> > > > > >
> > > > > > There are couple of things
> > > > > > We do world builds where they cause issues
> > > > > > Secondly, some of these force to pin providers and since BSP layers
> > > > > > appear before
> > > > > > other layers they become providers, its better to keep them limited 
> > > > > > to SOC there
> > > > >
> > > > > Sorry for the delay. Would adding EXCLUDE_FROM_WORLD be a better 
> > > > > solution?
> > > > > Also, can you please provide an example of pinning provider issue? 
> > > > > Thanks!
> > > > >
> > > >
> > > > excluding from world builds doesn't prevent them from nosing around
> > > > when building
> > > > images e.g. for non-ti machines. e.g. libgbm but there are more which
> > > > can be selected where not intended.
> > >
> > > Fine, mesa now provides own libgbm - I can see how that cause conflicts.
> > >
> > > What about other packages? Many of them are unique and some even have ti-
> > > prefix in the name. What's the point in limiting them to ti-soc?
> >
> > unless they are common, we should keep them under soc override, because then
> > they wont get built for other SOCs in a multi-BSP config.
>
> I'm willing to make meta-ti play nice with other BSPs. But I'm a bit hesitant
> to limit most of the packages here to specific soc family. Even though those
> packages are somewhat TI specific, one might want to use them with platforms
> from outside meta-ti, e.g. beaglebone-yocto from meta-yocto-bsp, which does
> not declare itself being part of "ti-soc" family.
>
> I still believe marking most of them with EXCLUDE_FROM_WORLD would solve your
> issues (sans libgbm) and won't affect your builds, unless you pull them
> directly by name. What am I missing?
>
Forget about building world issue for a moment, its more of peaceful
co-existence issue. Lot of us who build products have multiple SOCs
from different vendors and we
would like to have single yocto project be able to build all of them.
yes provided they are useful to non TI socs I think you have a point,
but beaglebone in meta-yocto-bsp is not a good argument to have it.
The machine should define SOC_FAMILY to be same as meta-ti

>
> > > Also, why use COMPATIBLE_HOST vs. COMPATIBLE_MACHINE?
> > >
> >
> > COMAPTIBLE_MACHINE will mark them specific to machine, which we dont want.
>
> Ah, didn't know COMPATIBLE_HOST won't do that. Good to know.
>
>
> > > > > > we are putting an effort to make sure that we have a distro which 
> > > > > > can
> > > > > > build for various
> > > > > > SBCs from same sandbox.
> > > > > >
> > > > > > See https://github.com/YoeDistro
> > &g

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

On Tue, Oct 16, 2018 at 12:59 PM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 16, 2018 at 12:35:50PM -0700, Khem Raj wrote:
> > On Tue, Oct 16, 2018 at 11:33 AM Denys Dmytriyenko  wrote:
> > >
> > > On Wed, Oct 10, 2018 at 12:56:50PM -0700, Khem Raj wrote:
> > > > Hi Denys
> > > >
> > > > On Wed, Oct 10, 2018 at 12:36 PM Denys Dmytriyenko  wrote:
> > > > >
> > > > > On Tue, Oct 09, 2018 at 03:40:40PM -0700, Khem Raj wrote:
> > > > > > No, it doesn't AFAICT
> > > > > >
> > > > > > On Tue, Oct 9, 2018 at 1:49 PM Denys Dmytriyenko  
> > > > > > wrote:
> > > > > >
> > > > > > > Does this make packages machine-specific?
> > > > > > >
> > > > > > > On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> > > > > > > > This helps in multi-BSP scenario, where other BSP layers are 
> > > > > > > > also
> > > > > > > > present in the layermix
> > > > >
> > > > > I'm not specifically against this patch, but want to understand 
> > > > > better - are
> > > > > there any specific conflicts these packages have with other BSPs?
> > > > >
> > > >
> > > > There are couple of things
> > > > We do world builds where they cause issues
> > > > Secondly, some of these force to pin providers and since BSP layers
> > > > appear before
> > > > other layers they become providers, its better to keep them limited to 
> > > > SOC there
> > >
> > > Sorry for the delay. Would adding EXCLUDE_FROM_WORLD be a better solution?
> > > Also, can you please provide an example of pinning provider issue? Thanks!
> > >
> >
> > excluding from world builds doesn't prevent them from nosing around
> > when building
> > images e.g. for non-ti machines. e.g. libgbm but there are more which
> > can be selected where not intended.
>
> Fine, mesa now provides own libgbm - I can see how that cause conflicts.
>
> What about other packages? Many of them are unique and some even have ti-
> prefix in the name. What's the point in limiting them to ti-soc?
>

unless they are common, we should keep them under soc override, because then
they wont get built for other SOCs in a multi-BSP config.

> Also, why use COMPATIBLE_HOST vs. COMPATIBLE_MACHINE?
>

COMAPTIBLE_MACHINE will mark them specific to machine, which we dont want.

>
> > > > we are putting an effort to make sure that we have a distro which can
> > > > build for various
> > > > SBCs from same sandbox.
> > > >
> > > > See https://github.com/YoeDistro
> > > >
> > > >
> > > > >
> > > > > > > > Signed-off-by: Khem Raj 
> > > > > > > > ---
> > > > > > > >  recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
> > > > > > > >  recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
> > > > > > > >  recipes-bsp/x-load/x-load_git.bb   | 3 +++
> > > > > > > >  recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
> > > > > > > >  recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
> > > > > > > >  recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
> > > > > > > >  recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
> > > > > > > >  recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
> > > > > > > >  recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
> > > > > > > >  recipes-ti/dsplib/dsplib.inc   | 2 ++
> > > > > > > >  recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
> > > > > > > >  recipes-ti/includes/ti-unpack.inc  | 5 
> > > > > > > > +
> > > > > > > >  recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
> > > > > > > >  recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
> > > > > > > >  recipes-ti/mathlib/mathlib.inc | 2 ++
> > > > > > > >  recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
> > > > > > > >  recipes-ti/swtools/swtools_git.bb  

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

On Tue, Oct 16, 2018 at 11:33 AM Denys Dmytriyenko  wrote:
>
> On Wed, Oct 10, 2018 at 12:56:50PM -0700, Khem Raj wrote:
> > Hi Denys
> >
> > On Wed, Oct 10, 2018 at 12:36 PM Denys Dmytriyenko  wrote:
> > >
> > > On Tue, Oct 09, 2018 at 03:40:40PM -0700, Khem Raj wrote:
> > > > No, it doesn't AFAICT
> > > >
> > > > On Tue, Oct 9, 2018 at 1:49 PM Denys Dmytriyenko  wrote:
> > > >
> > > > > Does this make packages machine-specific?
> > > > >
> > > > > On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> > > > > > This helps in multi-BSP scenario, where other BSP layers are also
> > > > > > present in the layermix
> > >
> > > I'm not specifically against this patch, but want to understand better - 
> > > are
> > > there any specific conflicts these packages have with other BSPs?
> > >
> >
> > There are couple of things
> > We do world builds where they cause issues
> > Secondly, some of these force to pin providers and since BSP layers
> > appear before
> > other layers they become providers, its better to keep them limited to SOC 
> > there
>
> Sorry for the delay. Would adding EXCLUDE_FROM_WORLD be a better solution?
> Also, can you please provide an example of pinning provider issue? Thanks!
>

excluding from world builds doesn't prevent them from nosing around
when building
images e.g. for non-ti machines. e.g. libgbm but there are more which
can be selected where not intended.

>
> > we are putting an effort to make sure that we have a distro which can
> > build for various
> > SBCs from same sandbox.
> >
> > See https://github.com/YoeDistro
> >
> >
> > >
> > > > > > Signed-off-by: Khem Raj 
> > > > > > ---
> > > > > >  recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
> > > > > >  recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
> > > > > >  recipes-bsp/x-load/x-load_git.bb   | 3 +++
> > > > > >  recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
> > > > > >  recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
> > > > > >  recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
> > > > > >  recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
> > > > > >  recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
> > > > > >  recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
> > > > > >  recipes-ti/dsplib/dsplib.inc   | 2 ++
> > > > > >  recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
> > > > > >  recipes-ti/includes/ti-unpack.inc  | 5 +
> > > > > >  recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
> > > > > >  recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
> > > > > >  recipes-ti/mathlib/mathlib.inc | 2 ++
> > > > > >  recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
> > > > > >  recipes-ti/swtools/swtools_git.bb  | 2 ++
> > > > > >  17 files changed, 46 insertions(+)
> > > > > >
> > > > > > diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb b/recipes-bsp/cuia/
> > > > > cuia_1.0.0.13.bb
> > > > > > index e048f6aa..a7caf504 100644
> > > > > > --- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > > > > > +++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > > > > > @@ -23,3 +23,6 @@ do_install() {
> > > > > >   cd ${S}
> > > > > >   oe_runmake DESTDIR=${D} libdir=${libdir} 
> > > > > > includedir=${includedir}
> > > > > install
> > > > > >  }
> > > > > > +
> > > > > > +COMPATIBLE_HOST ?= "null"
> > > > > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > > > > diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > > b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > > > index 94485b6a..d29b6496 100644
> > > > > > --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > > > +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > > > @@ -22,3 +22,6 @@ do_install()

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Tue, Oct 16, 2018 at 12:00 PM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 16, 2018 at 11:50:36AM -0700, Khem Raj wrote:
> > On Tue, Oct 16, 2018 at 11:29 AM Denys Dmytriyenko  wrote:
> > >
> > > On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > > > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini  wrote:
> > > > >
> > > > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko  
> > > > > > wrote:
> > > > > > >
> > > > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko 
> > > > > > > >  wrote:
> > > > > > > > >
> > > > > > > > > There have been reports recently that 
> > > > > > > > > am335x_beaglebone_config generates bad SPL.
> > > > > > > > > Until that is debugged and fixed, use generic 
> > > > > > > > > am335x_evm_config that covers all
> > > > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > > > >
> > > > > > > >
> > > > > > > > it fails to link
> > > > > > > >
> > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' 
> > > > > > > > will not
> > > > > > > > fit in region `.sram'
> > > > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 
> > > > > > > > 5772 bytes
> > > > > > > > | make[2]: *** 
> > > > > > > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > > > spl/u-boot-spl] Error 1
> > > > > > >
> > > > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from 
> > > > > > > oe-core, as well as
> > > > > > > Linaro gcc7 - no problems.
> > > > > >
> > > > > > My distro inherits poky policies, and on master it now inherits
> > > > > > hardening policies ( security flags) by defaults
> > > > > > do you happen to test poky ?
> > > > >
> > > > > I think we want to take a look at which of the security flags really
> > > > > make sense to use in this context.  Thanks!
> > > > >
> > > >
> > > > there could be more to it, since the distro uses thumb2 ISA by
> > > > default, I am not sure
> > > > if u-boot overrides that and builds using arm mode ISA always but
> > > > something to consider, I saw several reports about u-boot overflowing
> > > > sram sections and most of
> > > > the solutions were "oh it works for me" or at the best your toolchain
> > > > is different then mine. here is mine use it and move on.
> > >
> > > Khem,
> > >
> > > Well, FWIW, Tom and I are very familiar with this issue. As a matter of 
> > > fact,
> > > I first encountered it almost 2 years ago and had to prove there's such an
> > > issue, because everyone was saying it works for them, something must be 
> > > wrong
> > > with my OE builds... :)
> > >
> > > While .sram region is very limited, the issue is exacerbated by the fact 
> > > that
> > > all debug symbols from macros like __FILE__ are ended up in that section 
> > > as
> > > well. So, the longer your build path, the larger the section becomes. 
> > > Once I
> > > had instructions to reproduce the failure here internally with a series of
> > > long-named nested directories like aa and bb, Nishanth started 
> > > this
> > > thread on U-boot mailing list:
> > > https://lists.denx.de/pipermail/u-boot/2017-March/285031.html
> > >
> > > We've had the corresponding bug open internally all this time, while 
> > > adding
> > > workarounds to limit .sram section size by other means, like disabling 
> > > some
> > > options to reduce the code size. Your patch is one of those workarounds...
> > >
> > > But we've been patiently waiting for the following feature to come into 
> > > gcc to
> > > fix the issue properly:
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70268
> > >
> > > Since it's now part of gcc8, we should be able to use it. Not sure how to 
> > > keep
> > > gcc7 backward compatibility though...
> >
> > dumping absolute file name strings into SPL seems a waste of space to
> > me, but I will leave that out for now. Moreover it exposes build paths
> > into binaries that user may not be interested to share
> >
> > -ffile-prefix-map has been in OE toolchains since gcc6 and I think we
> > are already using it for kernel builds. We can probably enhance uboot
> > recipes in OE-Core to
> > use this option if compiler supports it. That solves my problem.
>
> Yeah, extending that from kernel to u-boot would be nice.
> Unfortunately, our products use Linaro gcc7 on rocko for now. Planning to
> migrate to gcc8 on thud soon...

we can check for the option before using it so atleast it will not
break older toolchains more than what they are already broken.
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Tue, Oct 16, 2018 at 11:29 AM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 16, 2018 at 11:11:36AM -0700, Khem Raj wrote:
> > On Tue, Oct 16, 2018 at 9:42 AM Tom Rini  wrote:
> > >
> > > On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > > > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko  wrote:
> > > > >
> > > > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko  
> > > > > > wrote:
> > > > > > >
> > > > > > > There have been reports recently that am335x_beaglebone_config 
> > > > > > > generates bad SPL.
> > > > > > > Until that is debugged and fixed, use generic am335x_evm_config 
> > > > > > > that covers all
> > > > > > > AM335x platforms, including BeagleBone variants.
> > > > > > >
> > > > > >
> > > > > > it fails to link
> > > > > >
> > > > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will 
> > > > > > not
> > > > > > fit in region `.sram'
> > > > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 
> > > > > > bytes
> > > > > > | make[2]: *** 
> > > > > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > > > spl/u-boot-spl] Error 1
> > > > >
> > > > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from oe-core, 
> > > > > as well as
> > > > > Linaro gcc7 - no problems.
> > > >
> > > > My distro inherits poky policies, and on master it now inherits
> > > > hardening policies ( security flags) by defaults
> > > > do you happen to test poky ?
> > >
> > > I think we want to take a look at which of the security flags really
> > > make sense to use in this context.  Thanks!
> > >
> >
> > there could be more to it, since the distro uses thumb2 ISA by
> > default, I am not sure
> > if u-boot overrides that and builds using arm mode ISA always but
> > something to consider, I saw several reports about u-boot overflowing
> > sram sections and most of
> > the solutions were "oh it works for me" or at the best your toolchain
> > is different then mine. here is mine use it and move on.
>
> Khem,
>
> Well, FWIW, Tom and I are very familiar with this issue. As a matter of fact,
> I first encountered it almost 2 years ago and had to prove there's such an
> issue, because everyone was saying it works for them, something must be wrong
> with my OE builds... :)
>
> While .sram region is very limited, the issue is exacerbated by the fact that
> all debug symbols from macros like __FILE__ are ended up in that section as
> well. So, the longer your build path, the larger the section becomes. Once I
> had instructions to reproduce the failure here internally with a series of
> long-named nested directories like aa and bb, Nishanth started this
> thread on U-boot mailing list:
> https://lists.denx.de/pipermail/u-boot/2017-March/285031.html
>
> We've had the corresponding bug open internally all this time, while adding
> workarounds to limit .sram section size by other means, like disabling some
> options to reduce the code size. Your patch is one of those workarounds...
>
> But we've been patiently waiting for the following feature to come into gcc to
> fix the issue properly:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70268
>
> Since it's now part of gcc8, we should be able to use it. Not sure how to keep
> gcc7 backward compatibility though...

dumping absolute file name strings into SPL seems a waste of space to
me, but I will leave that out for now. Moreover it exposes build paths
into binaries that user may not be interested to share

-ffile-prefix-map has been in OE toolchains since gcc6 and I think we
are already using it for kernel builds. We can probably enhance uboot
recipes in OE-Core to
use this option if compiler supports it. That solves my problem.
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH 1/3] u-boot: reduce the SPL `.rodata' size

[Khem Raj]

On Tue, Oct 16, 2018 at 9:39 AM Tom Rini  wrote:
>
> On Tue, Oct 16, 2018 at 12:47:43AM -0700, Khem Raj wrote:
> > Fixes errors e.g.
> >
> > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
> > fit in region `.sram'
> > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  ...vm_defconfig-Reduce-SPL-.rodata-size.patch | 73 +++
> >  .../u-boot/u-boot-ti-staging_2018.01.bb   |  2 +
> >  2 files changed, 75 insertions(+)
> >  create mode 100644 
> > recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> >
> > diff --git 
> > a/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> >  
> > b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> > new file mode 100644
> > index ..47597b28
> > --- /dev/null
> > +++ 
> > b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
> > @@ -0,0 +1,73 @@
> > +From 56dce6462e60e2aa5b87c97c5a2c43a4d834e251 Mon Sep 17 00:00:00 2001
> > +From: "Kemal R. Shakir" 
> > +Date: Wed, 3 Oct 2018 15:56:37 +0300
> > +Subject: [PATCH 1/1] am335x_evm_defconfig: Reduce SPL `.rodata' size
> > +
> > +---
> > + configs/am335x_evm_defconfig | 54 
> > + 1 file changed, 54 insertions(+)
> > +
> > +diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
> > +index 4908099431..568a4f535e 100644
> > +--- a/configs/am335x_evm_defconfig
> >  b/configs/am335x_evm_defconfig
> > +@@ -63,3 +63,57 @@ CONFIG_DYNAMIC_CRC_TABLE=y
> > + CONFIG_SPL_TINY_MEMSET=y
> > + CONFIG_RSA=y
> > + CONFIG_LZO=y
> > ++
> > ++#
> > ++# SPL / TPL
> > ++#
> > ++CONFIG_SUPPORT_SPL=y
> > ++CONFIG_SPL=y
> > ++CONFIG_SPL_BOARD_INIT=y
> > ++# CONFIG_SPL_BOOTROM_SUPPORT is not set
> > ++CONFIG_SPL_RAW_IMAGE_SUPPORT=y
> > ++CONFIG_SPL_LEGACY_IMAGE_SUPPORT=y
> > ++CONFIG_SPL_SYS_MALLOC_SIMPLE=y
> > ++# CONFIG_TPL_SYS_MALLOC_SIMPLE is not set
> > ++CONFIG_SPL_STACK_R=y
> > ++CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x10
> > ++CONFIG_SPL_SEPARATE_BSS=y
> > ++# CONFIG_SPL_DISPLAY_PRINT is not set
> > ++CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
> > ++CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x300
> > ++# CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION is not set
> > ++# CONFIG_SPL_CRC32_SUPPORT is not set
> > ++# CONFIG_SPL_MD5_SUPPORT is not set
> > ++# CONFIG_SPL_SHA1_SUPPORT is not set
> > ++# CONFIG_SPL_SHA256_SUPPORT is not set
> > ++# CONFIG_SPL_FIT_IMAGE_TINY is not set
> > ++# CONFIG_SPL_CPU_SUPPORT is not set
> > ++# CONFIG_SPL_CRYPTO_SUPPORT is not set
> > ++# CONFIG_SPL_HASH_SUPPORT is not set
> > ++# CONFIG_SPL_DMA_SUPPORT is not set
> > ++# CONFIG_SPL_ENV_SUPPORT is not set
> > ++CONFIG_SPL_EXT_SUPPORT=y
> > ++# CONFIG_SPL_FPGA_SUPPORT is not set
> > ++CONFIG_SPL_I2C_SUPPORT=y
> > ++# CONFIG_SPL_MMC_WRITE is not set
> > ++# CONFIG_SPL_MPC8XXX_INIT_DDR_SUPPORT is not set
> > ++CONFIG_SPL_MTD_SUPPORT=y
> > ++CONFIG_SPL_MUSB_NEW_SUPPORT=y
> > ++CONFIG_SPL_NET_SUPPORT=y
> > ++CONFIG_SPL_NET_VCI_STRING="AM335x U-Boot SPL"
> > ++# CONFIG_SPL_NO_CPU_SUPPORT is not set
> > ++# CONFIG_SPL_NOR_SUPPORT is not set
> > ++# CONFIG_SPL_XIP_SUPPORT is not set
> > ++# CONFIG_SPL_ONENAND_SUPPORT is not set
> > ++CONFIG_SPL_OS_BOOT=y
> > ++# CONFIG_SPL_PCI_SUPPORT is not set
> > ++# CONFIG_SPL_PCH_SUPPORT is not set
> > ++# CONFIG_SPL_POST_MEM_SUPPORT is not set
> > ++CONFIG_SPL_POWER_SUPPORT=y
> > ++# CONFIG_SPL_RAM_SUPPORT is not set
> > ++# CONFIG_SPL_RTC_SUPPORT is not set
> > ++# CONFIG_SPL_SATA_SUPPORT is not set
> > ++# CONFIG_SPL_THERMAL is not set
> > ++# CONFIG_SPL_USB_HOST_SUPPORT is not set
> > ++# CONFIG_SPL_USB_GADGET_SUPPORT is not set
> > ++# CONFIG_SPL_YMODEM_SUPPORT is not set
>
> The original patch isn't yours, but, what?  Apply this patch, run 'make
> am335x_evm_defconfig savedefconfig', copy 'defconfig' back over to
> configs/am335x_evm_defconfig and see what actually changed vs top of
> tree.  We really want to know what you're now turning off compared with
> the regular config and perhaps look into why that's now overflowing, and
> with what compiler?  That's some rather large growth.  Thanks!
>

I can try that now that I have it in buildable state, but since master
works fine on both
accounts ( defconfig and sram issue) I will see when I can get to it.

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

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Tue, Oct 16, 2018 at 9:42 AM Tom Rini  wrote:
>
> On Sun, Oct 14, 2018 at 10:07:45PM -0700, Khem Raj wrote:
> > On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko  wrote:
> > >
> > > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko  wrote:
> > > > >
> > > > > There have been reports recently that am335x_beaglebone_config 
> > > > > generates bad SPL.
> > > > > Until that is debugged and fixed, use generic am335x_evm_config that 
> > > > > covers all
> > > > > AM335x platforms, including BeagleBone variants.
> > > > >
> > > >
> > > > it fails to link
> > > >
> > > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
> > > > fit in region `.sram'
> > > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> > > > | make[2]: *** 
> > > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > > spl/u-boot-spl] Error 1
> > >
> > > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from oe-core, as 
> > > well as
> > > Linaro gcc7 - no problems.
> >
> > My distro inherits poky policies, and on master it now inherits
> > hardening policies ( security flags) by defaults
> > do you happen to test poky ?
>
> I think we want to take a look at which of the security flags really
> make sense to use in this context.  Thanks!
>

there could be more to it, since the distro uses thumb2 ISA by
default, I am not sure
if u-boot overrides that and builds using arm mode ISA always but
something to consider, I saw several reports about u-boot overflowing
sram sections and most of
the solutions were "oh it works for me" or at the best your toolchain
is different then mine. here is mine use it and move on.

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

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Sun, Oct 14, 2018 at 10:07 PM Khem Raj  wrote:
>
> On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko  wrote:
> >
> > On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko  wrote:
> > > >
> > > > There have been reports recently that am335x_beaglebone_config 
> > > > generates bad SPL.
> > > > Until that is debugged and fixed, use generic am335x_evm_config that 
> > > > covers all
> > > > AM335x platforms, including BeagleBone variants.
> > > >
> > >
> > > it fails to link
> > >
> > > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
> > > fit in region `.sram'
> > > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> > > | make[2]: *** 
> > > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > > spl/u-boot-spl] Error 1
> >
> > FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from oe-core, as well 
> > as
> > Linaro gcc7 - no problems.
>
> My distro inherits poky policies, and on master it now inherits
> hardening policies ( security flags) by defaults
> do you happen to test poky ?

It seems I am not alone, there has been other reports of similar
issues and some combos work some dont
I have ported this patch

http://e2e.ti.com/support/processors/f/791/t/733651?PROCESSOR-SDK-AM335X-MLO-and-U-boot-issues-u-boot-spl-section-rodata-will-not-fit-in-region-sram-

and now my build problems are gone,

Added couple of other patches on top for beaglebone, and now I can
boot bbb using meta-ti BSP


> >
> >
> > > > Signed-off-by: Denys Dmytriyenko 
> > > > ---
> > > >  conf/machine/beaglebone.conf | 3 ++-
> > > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
> > > > index 49edfd6..2514792 100644
> > > > --- a/conf/machine/beaglebone.conf
> > > > +++ b/conf/machine/beaglebone.conf
> > > > @@ -13,7 +13,8 @@ MACHINE_GUI_CLASS = "bigscreen"
> > > >
> > > >  SERIAL_CONSOLE = "115200 ttyS0"
> > > >
> > > > -UBOOT_MACHINE = "am335x_boneblack_config"
> > > > +# fall back on generic am335x_evm_config for now
> > > > +#UBOOT_MACHINE = "am335x_boneblack_config"
> > > >
> > > >  WKS_FILE = "sdimage-bootpart.wks"
> > > >  IMAGE_BOOT_FILES = "MLO u-boot.img"
> > > > --
> > > > 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] [PATCH 2/3] beaglebone.wks: Add beaglebone wic template

[Khem Raj]

Signed-off-by: Khem Raj 
---
 wic/beaglebone.wks | 6 ++
 1 file changed, 6 insertions(+)
 create mode 100644 wic/beaglebone.wks

diff --git a/wic/beaglebone.wks b/wic/beaglebone.wks
new file mode 100644
index ..b75f238d
--- /dev/null
+++ b/wic/beaglebone.wks
@@ -0,0 +1,6 @@
+# short-description: Create SD card image for Beaglebone
+# long-description: Creates a partitioned SD card image for Beaglebone.
+# Boot files are located in the first vfat partition.
+
+part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label 
boot --active --align 4 --size 16 --sourceparams="loader=u-boot" --use-uuid
+part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4 
--use-uuid
-- 
2.19.1

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

[meta-ti] [PATCH 1/3] u-boot: reduce the SPL `.rodata' size

[Khem Raj]

Fixes errors e.g.

| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
fit in region `.sram'
| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes

Signed-off-by: Khem Raj 
---
 ...vm_defconfig-Reduce-SPL-.rodata-size.patch | 73 +++
 .../u-boot/u-boot-ti-staging_2018.01.bb   |  2 +
 2 files changed, 75 insertions(+)
 create mode 100644 
recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch

diff --git 
a/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
 
b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
new file mode 100644
index ..47597b28
--- /dev/null
+++ 
b/recipes-bsp/u-boot/files/0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch
@@ -0,0 +1,73 @@
+From 56dce6462e60e2aa5b87c97c5a2c43a4d834e251 Mon Sep 17 00:00:00 2001
+From: "Kemal R. Shakir" 
+Date: Wed, 3 Oct 2018 15:56:37 +0300
+Subject: [PATCH 1/1] am335x_evm_defconfig: Reduce SPL `.rodata' size
+
+---
+ configs/am335x_evm_defconfig | 54 
+ 1 file changed, 54 insertions(+)
+
+diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig
+index 4908099431..568a4f535e 100644
+--- a/configs/am335x_evm_defconfig
 b/configs/am335x_evm_defconfig
+@@ -63,3 +63,57 @@ CONFIG_DYNAMIC_CRC_TABLE=y
+ CONFIG_SPL_TINY_MEMSET=y
+ CONFIG_RSA=y
+ CONFIG_LZO=y
++
++#
++# SPL / TPL
++#
++CONFIG_SUPPORT_SPL=y
++CONFIG_SPL=y
++CONFIG_SPL_BOARD_INIT=y
++# CONFIG_SPL_BOOTROM_SUPPORT is not set
++CONFIG_SPL_RAW_IMAGE_SUPPORT=y
++CONFIG_SPL_LEGACY_IMAGE_SUPPORT=y
++CONFIG_SPL_SYS_MALLOC_SIMPLE=y
++# CONFIG_TPL_SYS_MALLOC_SIMPLE is not set
++CONFIG_SPL_STACK_R=y
++CONFIG_SPL_STACK_R_MALLOC_SIMPLE_LEN=0x10
++CONFIG_SPL_SEPARATE_BSS=y
++# CONFIG_SPL_DISPLAY_PRINT is not set
++CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
++CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x300
++# CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_PARTITION is not set
++# CONFIG_SPL_CRC32_SUPPORT is not set
++# CONFIG_SPL_MD5_SUPPORT is not set
++# CONFIG_SPL_SHA1_SUPPORT is not set
++# CONFIG_SPL_SHA256_SUPPORT is not set
++# CONFIG_SPL_FIT_IMAGE_TINY is not set
++# CONFIG_SPL_CPU_SUPPORT is not set
++# CONFIG_SPL_CRYPTO_SUPPORT is not set
++# CONFIG_SPL_HASH_SUPPORT is not set
++# CONFIG_SPL_DMA_SUPPORT is not set
++# CONFIG_SPL_ENV_SUPPORT is not set
++CONFIG_SPL_EXT_SUPPORT=y
++# CONFIG_SPL_FPGA_SUPPORT is not set
++CONFIG_SPL_I2C_SUPPORT=y
++# CONFIG_SPL_MMC_WRITE is not set
++# CONFIG_SPL_MPC8XXX_INIT_DDR_SUPPORT is not set
++CONFIG_SPL_MTD_SUPPORT=y
++CONFIG_SPL_MUSB_NEW_SUPPORT=y
++CONFIG_SPL_NET_SUPPORT=y
++CONFIG_SPL_NET_VCI_STRING="AM335x U-Boot SPL"
++# CONFIG_SPL_NO_CPU_SUPPORT is not set
++# CONFIG_SPL_NOR_SUPPORT is not set
++# CONFIG_SPL_XIP_SUPPORT is not set
++# CONFIG_SPL_ONENAND_SUPPORT is not set
++CONFIG_SPL_OS_BOOT=y
++# CONFIG_SPL_PCI_SUPPORT is not set
++# CONFIG_SPL_PCH_SUPPORT is not set
++# CONFIG_SPL_POST_MEM_SUPPORT is not set
++CONFIG_SPL_POWER_SUPPORT=y
++# CONFIG_SPL_RAM_SUPPORT is not set
++# CONFIG_SPL_RTC_SUPPORT is not set
++# CONFIG_SPL_SATA_SUPPORT is not set
++# CONFIG_SPL_THERMAL is not set
++# CONFIG_SPL_USB_HOST_SUPPORT is not set
++# CONFIG_SPL_USB_GADGET_SUPPORT is not set
++# CONFIG_SPL_YMODEM_SUPPORT is not set
+--
+2.17.1
diff --git a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb 
b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
index cbb8857a..46a26480 100644
--- a/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
+++ b/recipes-bsp/u-boot/u-boot-ti-staging_2018.01.bb
@@ -5,3 +5,5 @@ PR = "r24"
 BRANCH = "ti-u-boot-2018.01"
 
 SRCREV = "2cc52408bf1357f11b96548e78223a1df321c1ae"
+
+SRC_URI += "file://0001-am335x_evm_defconfig-Reduce-SPL-.rodata-size.patch"
-- 
2.19.1

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

[meta-ti] [PATCH 3/3] beaglebone.conf: Use beaglebone sample wic template

[Khem Raj]

Add kernel and devicetree files to image install

Signed-off-by: Khem Raj 
---
 conf/machine/beaglebone.conf | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 25147926..a9383c5a 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -1,6 +1,6 @@
 #@TYPE: Machine
 #@NAME: BeagleBone machine
-#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board 
+#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
 require conf/machine/include/ti33x.inc
 
@@ -16,11 +16,17 @@ SERIAL_CONSOLE = "115200 ttyS0"
 # fall back on generic am335x_evm_config for now
 #UBOOT_MACHINE = "am335x_boneblack_config"
 
-WKS_FILE = "sdimage-bootpart.wks"
-IMAGE_BOOT_FILES = "MLO u-boot.img"
-IMAGE_FSTYPES += "tar.xz wic.xz"
+WKS_FILE = "beaglebone.wks"
 
 do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO zImage am335x-bone.dtb 
am335x-boneblack.dtb am335x-bonegreen.dtb"
+
+IMAGE_FSTYPES += "tar.xz wic.xz"
 
 # Refine the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_BOARDS = "bbbAM335x"
+
+SPL_BINARY = "MLO"
+UBOOT_SUFFIX = "img"
+
+IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
-- 
2.19.1

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

Re: [meta-ti] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Sun, Oct 14, 2018 at 12:24 PM Denys Dmytriyenko  wrote:
>
> On Sat, Oct 13, 2018 at 01:17:12AM -0700, Khem Raj wrote:
> > On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko  wrote:
> > >
> > > There have been reports recently that am335x_beaglebone_config generates 
> > > bad SPL.
> > > Until that is debugged and fixed, use generic am335x_evm_config that 
> > > covers all
> > > AM335x platforms, including BeagleBone variants.
> > >
> >
> > it fails to link
> >
> > | arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
> > fit in region `.sram'
> > | arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
> > | make[2]: *** 
> > [/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
> > spl/u-boot-spl] Error 1
>
> FWIW, just built u-boot-ti-staging with gcc7 and gcc8 from oe-core, as well as
> Linaro gcc7 - no problems.

My distro inherits poky policies, and on master it now inherits
hardening policies ( security flags) by defaults
do you happen to test poky ?
>
>
> > > Signed-off-by: Denys Dmytriyenko 
> > > ---
> > >  conf/machine/beaglebone.conf | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
> > > index 49edfd6..2514792 100644
> > > --- a/conf/machine/beaglebone.conf
> > > +++ b/conf/machine/beaglebone.conf
> > > @@ -13,7 +13,8 @@ MACHINE_GUI_CLASS = "bigscreen"
> > >
> > >  SERIAL_CONSOLE = "115200 ttyS0"
> > >
> > > -UBOOT_MACHINE = "am335x_boneblack_config"
> > > +# fall back on generic am335x_evm_config for now
> > > +#UBOOT_MACHINE = "am335x_boneblack_config"
> > >
> > >  WKS_FILE = "sdimage-bootpart.wks"
> > >  IMAGE_BOOT_FILES = "MLO u-boot.img"
> > > --
> > > 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] [PATCH] beaglebone.conf: temporarily use generic am335x_evm_config for U-boot

[Khem Raj]

On Fri, Oct 12, 2018 at 8:00 PM Denys Dmytriyenko  wrote:
>
> There have been reports recently that am335x_beaglebone_config generates bad 
> SPL.
> Until that is debugged and fixed, use generic am335x_evm_config that covers 
> all
> AM335x platforms, including BeagleBone variants.
>

it fails to link

| arm-yoe-linux-gnueabi-ld.bfd: u-boot-spl section `.rodata' will not
fit in region `.sram'
| arm-yoe-linux-gnueabi-ld.bfd: region `.sram' overflowed by 5772 bytes
| make[2]: *** 
[/mnt/a/yoe/build/tmp/work/beaglebone-yoe-linux-gnueabi/u-boot-ti-staging/2018.01+gitAUTOINC+2cc52408bf-r24/git/scripts/Makefile.spl:349:
spl/u-boot-spl] Error 1
|

> Signed-off-by: Denys Dmytriyenko 
> ---
>  conf/machine/beaglebone.conf | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
> index 49edfd6..2514792 100644
> --- a/conf/machine/beaglebone.conf
> +++ b/conf/machine/beaglebone.conf
> @@ -13,7 +13,8 @@ MACHINE_GUI_CLASS = "bigscreen"
>
>  SERIAL_CONSOLE = "115200 ttyS0"
>
> -UBOOT_MACHINE = "am335x_boneblack_config"
> +# fall back on generic am335x_evm_config for now
> +#UBOOT_MACHINE = "am335x_boneblack_config"
>
>  WKS_FILE = "sdimage-bootpart.wks"
>  IMAGE_BOOT_FILES = "MLO u-boot.img"
> --
> 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] [PATCH 1/2] beaglebone.wks: Add beaglebone wic template

[Khem Raj]

Signed-off-by: Khem Raj 
---
 wic/beaglebone.wks | 6 ++
 1 file changed, 6 insertions(+)
 create mode 100644 wic/beaglebone.wks

diff --git a/wic/beaglebone.wks b/wic/beaglebone.wks
new file mode 100644
index ..b75f238d
--- /dev/null
+++ b/wic/beaglebone.wks
@@ -0,0 +1,6 @@
+# short-description: Create SD card image for Beaglebone
+# long-description: Creates a partitioned SD card image for Beaglebone.
+# Boot files are located in the first vfat partition.
+
+part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label 
boot --active --align 4 --size 16 --sourceparams="loader=u-boot" --use-uuid
+part / --source rootfs --ondisk mmcblk --fstype=ext4 --label root --align 4 
--use-uuid
-- 
2.19.1

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

[meta-ti] [PATCH 2/2] beaglebone.conf: Switch u-boot provider to mainline from oe-core

[Khem Raj]

use beaglebone specific wic template

Signed-off-by: Khem Raj 
---
 conf/machine/beaglebone.conf | 22 --
 1 file changed, 16 insertions(+), 6 deletions(-)

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 49edfd61..25b9998a 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -1,6 +1,6 @@
 #@TYPE: Machine
 #@NAME: BeagleBone machine
-#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board 
+#@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
 
 require conf/machine/include/ti33x.inc
 
@@ -11,15 +11,25 @@ KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblue.dtb \
 # Only has DVI connector for external screen
 MACHINE_GUI_CLASS = "bigscreen"
 
-SERIAL_CONSOLE = "115200 ttyS0"
+SERIAL_CONSOLES = "115200;ttyS0 115200;ttyO0"
 
 UBOOT_MACHINE = "am335x_boneblack_config"
 
-WKS_FILE = "sdimage-bootpart.wks"
-IMAGE_BOOT_FILES = "MLO u-boot.img"
-IMAGE_FSTYPES += "tar.xz wic.xz"
+WKS_FILE = "beaglebone.wks"
 
-do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} MLO zImage am335x-bone.dtb 
am335x-boneblack.dtb am335x-bonegreen.dtb"
+
+IMAGE_FSTYPES += "tar.xz wic.xz"
 
 # Refine the list of device targets for ti-pdk class recipes
 TI_PDK_LIMIT_BOARDS = "bbbAM335x"
+
+SPL_BINARY = "MLO"
+UBOOT_SUFFIX = "img"
+
+IMAGE_INSTALL_append = " kernel-devicetree kernel-image-zimage"
+do_image_wic[depends] += "mtools-native:do_populate_sysroot 
dosfstools-native:do_populate_sysroot"
+
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot"
+PREFERRED_PROVIDER_u-boot = "u-boot"
+
-- 
2.19.1

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

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Khem Raj]

On Fri, Oct 12, 2018 at 2:01 PM Denys Dmytriyenko  wrote:
>
> On Fri, Oct 12, 2018 at 01:49:05PM -0700, Khem Raj wrote:
> > On Fri, Oct 12, 2018 at 1:37 PM Denys Dmytriyenko  wrote:
> > >
> > > On Fri, Oct 12, 2018 at 01:34:13PM -0700, Khem Raj wrote:
> > > > On Fri, Oct 12, 2018 at 1:31 PM Denys Dmytriyenko  wrote:
> > > > >
> > > > > On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> > > > > > On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  
> > > > > > wrote:
> > > > > > >
> > > > > > > Are you still trying to do world builds? :)
> > > > > > >
> > > > > >
> > > > > > yes. with the patches I send in this week meta-ti seems to behave in
> > > > > > multi-BSP setup
> > > > > > I will soon add it to bblayers.conf for Yoe distro and it will start
> > > > > > testing on meta-openembedded CI builds, atleast for not nosing other
> > > > > > BSPs, I dont have infra to do world build for all the machines
> > > > > >
> > > > > > but if you were to pick Yoe distro and run with it for machines you
> > > > > > are interested in
> > > > > > that would be awesome.
> > > > > >
> > > > > > See. https://github.com/YoeDistro/yoe-distro, everyone having 
> > > > > > interesting boards
> > > > > > is welcome to run world builds using that and report problems.
> > > > >
> > > > > I can probably add it to my CI loop as well - I already do extensive 
> > > > > builds
> > > > > and tests on Arago, Poky and distroless.
> > > >
> > > > Cool thanks. Although you wont need all of above
> > > > after this :)
> > >
> > > Meaning?
> >
> > Yoe is a superset
>
> Uhm, hardly. Do you mean just BSP pieces?

not only that but we have added lot
of common layers too
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Khem Raj]

On Fri, Oct 12, 2018 at 1:37 PM Denys Dmytriyenko  wrote:
>
> On Fri, Oct 12, 2018 at 01:34:13PM -0700, Khem Raj wrote:
> > On Fri, Oct 12, 2018 at 1:31 PM Denys Dmytriyenko  wrote:
> > >
> > > On Fri, Oct 12, 2018 at 01:01:41PM -0700, Khem Raj wrote:
> > > > On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  wrote:
> > > > >
> > > > > Are you still trying to do world builds? :)
> > > > >
> > > >
> > > > yes. with the patches I send in this week meta-ti seems to behave in
> > > > multi-BSP setup
> > > > I will soon add it to bblayers.conf for Yoe distro and it will start
> > > > testing on meta-openembedded CI builds, atleast for not nosing other
> > > > BSPs, I dont have infra to do world build for all the machines
> > > >
> > > > but if you were to pick Yoe distro and run with it for machines you
> > > > are interested in
> > > > that would be awesome.
> > > >
> > > > See. https://github.com/YoeDistro/yoe-distro, everyone having 
> > > > interesting boards
> > > > is welcome to run world builds using that and report problems.
> > >
> > > I can probably add it to my CI loop as well - I already do extensive 
> > > builds
> > > and tests on Arago, Poky and distroless.
> >
> > Cool thanks. Although you wont need all of above
> > after this :)
>
> Meaning?

Yoe is a superset
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Khem Raj]

On Fri, Oct 12, 2018 at 12:58 PM Denys Dmytriyenko  wrote:
>
> Are you still trying to do world builds? :)
>

yes. with the patches I send in this week meta-ti seems to behave in
multi-BSP setup
I will soon add it to bblayers.conf for Yoe distro and it will start
testing on meta-openembedded CI builds, atleast for not nosing other
BSPs, I dont have infra to do world build for all the machines

but if you were to pick Yoe distro and run with it for machines you
are interested in
that would be awesome.

See. https://github.com/YoeDistro/yoe-distro, everyone having interesting boards
is welcome to run world builds using that and report problems.

> Most of the places with this QA warning that are part of our builds were fixed
> before, but there are some outdated recipes like this one which were left out.
>
>
> On Fri, Oct 12, 2018 at 12:50:00PM -0700, Khem Raj wrote:
> > Fixes do_package_qa warnings
> >  is owned by uid 1000, which is the same as the user running bitbake. 
> > This may be due to host contamination
> >
> > 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 603a01a7..6c61a4e9 100644
> > --- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > +++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
> > @@ -14,7 +14,7 @@ S = "${WORKDIR}/git"
> >
> >  do_install() {
> >   install -d ${D}${datadir}/${PN}
> > - cp -a ${S}/* ${D}${datadir}/${PN}
> > + cp -R --no-dereference --preserve=mode,links ${S}/* 
> > ${D}${datadir}/${PN}
> >  }
> >
> >  FILES_${PN} += "${datadir}/${PN}"
> > --
> > 2.19.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] [PATCH] beaglebone-getting-started: Use cp options to not alter file mode

[Khem Raj]

Fixes do_package_qa warnings
 is owned by uid 1000, which is the same as the user running bitbake. 
This may be due to host contamination

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 603a01a7..6c61a4e9 100644
--- a/recipes-ti/beagleboard/beaglebone-getting-started.bb
+++ b/recipes-ti/beagleboard/beaglebone-getting-started.bb
@@ -14,7 +14,7 @@ S = "${WORKDIR}/git"
 
 do_install() {
install -d ${D}${datadir}/${PN}
-   cp -a ${S}/* ${D}${datadir}/${PN}
+   cp -R --no-dereference --preserve=mode,links ${S}/* ${D}${datadir}/${PN}
 }
 
 FILES_${PN} += "${datadir}/${PN}"
-- 
2.19.1

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

[meta-ti] [PATCH] recips: Mark more recipes to be ti-soc specific

[Khem Raj]

Signed-off-by: Khem Raj 
---
 recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb | 3 +++
 recipes-bsp/cmem/cmem.inc   | 2 ++
 recipes-ti/devtools/ti-xdctools-common.inc  | 5 +
 recipes-ti/osal/ti-osal.inc | 4 
 4 files changed, 14 insertions(+)

diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb 
b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
index 3572638d..29fff504 100644
--- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
+++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
@@ -26,3 +26,6 @@ do_install() {
 }
 
 FILES_${PN} += "${base_libdir}/firmware"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti33x = "(.*)"
+
diff --git a/recipes-bsp/cmem/cmem.inc b/recipes-bsp/cmem/cmem.inc
index 11cebe8d..abbf2492 100644
--- a/recipes-bsp/cmem/cmem.inc
+++ b/recipes-bsp/cmem/cmem.inc
@@ -12,3 +12,5 @@ PV = "4.15.00.02+git${SRCPV}"
 SRC_URI = "git://git.ti.com/ipc/ludev.git;protocol=git;branch=${BRANCH}"
 
 S = "${WORKDIR}/git"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-ti/devtools/ti-xdctools-common.inc 
b/recipes-ti/devtools/ti-xdctools-common.inc
index a3949cad..0e86ef7a 100644
--- a/recipes-ti/devtools/ti-xdctools-common.inc
+++ b/recipes-ti/devtools/ti-xdctools-common.inc
@@ -61,3 +61,8 @@ libhpi.so \
 lib.so \
 libcairo.so.2 \
 "
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
+COMPATIBLE_HOST_class-native = "(.*)"
+COMPATIBLE_HOST_class-nativesdk = "(.*)"
+
diff --git a/recipes-ti/osal/ti-osal.inc b/recipes-ti/osal/ti-osal.inc
index cb8da354..bbbdf517 100644
--- a/recipes-ti/osal/ti-osal.inc
+++ b/recipes-ti/osal/ti-osal.inc
@@ -19,3 +19,7 @@ INSANE_SKIP_${PN}-dev = "staticdev"
 
 ALLOW_EMPTY_${PN} = "1"
 FILES_${PN}-dev += "${OSAL_INSTALL_DIR_RECIPE}"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
+
-- 
2.19.1

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

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

Hi Denys

On Wed, Oct 10, 2018 at 12:36 PM Denys Dmytriyenko  wrote:
>
> On Tue, Oct 09, 2018 at 03:40:40PM -0700, Khem Raj wrote:
> > No, it doesn't AFAICT
> >
> > On Tue, Oct 9, 2018 at 1:49 PM Denys Dmytriyenko  wrote:
> >
> > > Does this make packages machine-specific?
> > >
> > > On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> > > > This helps in multi-BSP scenario, where other BSP layers are also
> > > > present in the layermix
>
> I'm not specifically against this patch, but want to understand better - are
> there any specific conflicts these packages have with other BSPs?
>

There are couple of things
We do world builds where they cause issues
Secondly, some of these force to pin providers and since BSP layers
appear before
other layers they become providers, its better to keep them limited to SOC there

we are putting an effort to make sure that we have a distro which can
build for various
SBCs from same sandbox.

See https://github.com/YoeDistro


>
> > > > Signed-off-by: Khem Raj 
> > > > ---
> > > >  recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
> > > >  recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
> > > >  recipes-bsp/x-load/x-load_git.bb   | 3 +++
> > > >  recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
> > > >  recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
> > > >  recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
> > > >  recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
> > > >  recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
> > > >  recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
> > > >  recipes-ti/dsplib/dsplib.inc   | 2 ++
> > > >  recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
> > > >  recipes-ti/includes/ti-unpack.inc  | 5 +
> > > >  recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
> > > >  recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
> > > >  recipes-ti/mathlib/mathlib.inc | 2 ++
> > > >  recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
> > > >  recipes-ti/swtools/swtools_git.bb  | 2 ++
> > > >  17 files changed, 46 insertions(+)
> > > >
> > > > diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb b/recipes-bsp/cuia/
> > > cuia_1.0.0.13.bb
> > > > index e048f6aa..a7caf504 100644
> > > > --- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > > > +++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > > > @@ -23,3 +23,6 @@ do_install() {
> > > >   cd ${S}
> > > >   oe_runmake DESTDIR=${D} libdir=${libdir} includedir=${includedir}
> > > install
> > > >  }
> > > > +
> > > > +COMPATIBLE_HOST ?= "null"
> > > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > > diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > index 94485b6a..d29b6496 100644
> > > > --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > > > @@ -22,3 +22,6 @@ do_install() {
> > > >  install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > > >  install -m 644 ${S}/galcore.ko
> > > ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> > > >  }
> > > > +
> > > > +COMPATIBLE_HOST ?= "null"
> > > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > > diff --git a/recipes-bsp/x-load/x-load_git.bb b/recipes-bsp/x-load/
> > > x-load_git.bb
> > > > index dd8bce2d..1ce1b0f0 100644
> > > > --- a/recipes-bsp/x-load/x-load_git.bb
> > > > +++ b/recipes-bsp/x-load/x-load_git.bb
> > > > @@ -17,3 +17,6 @@ CONFIG_HEADER_beagleboard = "1"
> > > >  XLOAD_MACHINE_omap3-touchbook = "omap3530beagle_config"
> > > >
> > > >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> > > > +
> > > > +COMPATIBLE_HOST ?= "null"
> > > > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > > > diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb
> > > b/recipes-graphics/gbm/libgbm_10.0.0.bb
> > > > index 38715ccf..9e3c7ed0 100644
> > > > --- 

Re: [meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

No, it doesn't AFAICT

On Tue, Oct 9, 2018 at 1:49 PM Denys Dmytriyenko  wrote:

> Does this make packages machine-specific?
>
> On Tue, Oct 09, 2018 at 01:45:03PM -0700, Khem Raj wrote:
> > This helps in multi-BSP scenario, where other BSP layers are also
> > present in the layermix
> >
> > Signed-off-by: Khem Raj 
> > ---
> >  recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
> >  recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
> >  recipes-bsp/x-load/x-load_git.bb   | 3 +++
> >  recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
> >  recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
> >  recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
> >  recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
> >  recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
> >  recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
> >  recipes-ti/dsplib/dsplib.inc   | 2 ++
> >  recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
> >  recipes-ti/includes/ti-unpack.inc  | 5 +
> >  recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
> >  recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
> >  recipes-ti/mathlib/mathlib.inc | 2 ++
> >  recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
> >  recipes-ti/swtools/swtools_git.bb  | 2 ++
> >  17 files changed, 46 insertions(+)
> >
> > diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb b/recipes-bsp/cuia/
> cuia_1.0.0.13.bb
> > index e048f6aa..a7caf504 100644
> > --- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > +++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
> > @@ -23,3 +23,6 @@ do_install() {
> >   cd ${S}
> >   oe_runmake DESTDIR=${D} libdir=${libdir} includedir=${includedir}
> install
> >  }
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > index 94485b6a..d29b6496 100644
> > --- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > +++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
> > @@ -22,3 +22,6 @@ do_install() {
> >  install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> >  install -m 644 ${S}/galcore.ko
> ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
> >  }
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > diff --git a/recipes-bsp/x-load/x-load_git.bb b/recipes-bsp/x-load/
> x-load_git.bb
> > index dd8bce2d..1ce1b0f0 100644
> > --- a/recipes-bsp/x-load/x-load_git.bb
> > +++ b/recipes-bsp/x-load/x-load_git.bb
> > @@ -17,3 +17,6 @@ CONFIG_HEADER_beagleboard = "1"
> >  XLOAD_MACHINE_omap3-touchbook = "omap3530beagle_config"
> >
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb
> b/recipes-graphics/gbm/libgbm_10.0.0.bb
> > index 38715ccf..9e3c7ed0 100644
> > --- a/recipes-graphics/gbm/libgbm_10.0.0.bb
> > +++ b/recipes-graphics/gbm/libgbm_10.0.0.bb
> > @@ -16,3 +16,6 @@ SRC_URI = "git://
> git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH}
> <http://git.ti.com/glsdk/libgbm.git;protocol=git;branch=$%7BBRANCH%7D> \
> >
> file://0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch"
> >
> >  S = "${WORKDIR}/git"
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > 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 dafaac1e..a2f8f192 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
> > @@ -37,3 +37,6 @@ do_install() {
> >  }
> >
> >  INSANE_SKIP_${PN} += "ldflags"
> > +
> > +COMPATIBLE_HOST ?= "null"
> > +COMPATIBLE_HOST_ti-soc = "(.*)"
> > diff --git a/recipes-graphics/omapfbplay/omapfbplay.inc
> b/recipes-graphics/omapfbplay/omapfbplay.inc
> > index df166dd3..744eb8f7 100644
> > --- a/recipes-graphics/omapfbplay/omapfbplay.inc
> > +++ b/recipes-graphics/omapfbplay/omapfbplay.inc
> > @@ -14,6 +14,8 @@ SRC_URI =

[meta-ti] [PATCH] recipes: Limit ti specific recipes under ti-soc override

[Khem Raj]

This helps in multi-BSP scenario, where other BSP layers are also
present in the layermix

Signed-off-by: Khem Raj 
---
 recipes-bsp/cuia/cuia_1.0.0.13.bb  | 3 +++
 recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb | 3 +++
 recipes-bsp/x-load/x-load_git.bb   | 3 +++
 recipes-graphics/gbm/libgbm_10.0.0.bb  | 3 +++
 recipes-graphics/libgal/ti-gc320-libs_5.0.11.p7.bb | 3 +++
 recipes-graphics/omapfbplay/omapfbplay.inc | 2 ++
 recipes-multimedia/libdce/libdce_3.00.14.00.bb | 2 ++
 recipes-ti/bios/ti-biosutils_1.02.02.bb| 3 +++
 recipes-ti/dmai/ti-dmai_svn.bb | 3 +++
 recipes-ti/dsplib/dsplib.inc   | 2 ++
 recipes-ti/hdvpss/ti-hdvpss_01.00.01.27.bb | 2 ++
 recipes-ti/includes/ti-unpack.inc  | 5 +
 recipes-ti/ipc/ti-ipc-common.inc   | 2 ++
 recipes-ti/linuxutils/ti-linuxutils_2.26.01.02.bb  | 3 +++
 recipes-ti/mathlib/mathlib.inc | 2 ++
 recipes-ti/ndk/ti-ndk_3.40.01.01.bb| 3 +++
 recipes-ti/swtools/swtools_git.bb  | 2 ++
 17 files changed, 46 insertions(+)

diff --git a/recipes-bsp/cuia/cuia_1.0.0.13.bb 
b/recipes-bsp/cuia/cuia_1.0.0.13.bb
index e048f6aa..a7caf504 100644
--- a/recipes-bsp/cuia/cuia_1.0.0.13.bb
+++ b/recipes-bsp/cuia/cuia_1.0.0.13.bb
@@ -23,3 +23,6 @@ do_install() {
cd ${S}
oe_runmake DESTDIR=${D} libdir=${libdir} includedir=${includedir} 
install
 }
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb 
b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
index 94485b6a..d29b6496 100644
--- a/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
+++ b/recipes-bsp/gc320-drivers/ti-gc320-driver_5.0.11.p7.bb
@@ -22,3 +22,6 @@ do_install() {
 install -d ${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
 install -m 644 ${S}/galcore.ko 
${D}/${base_libdir}/modules/${KERNEL_VERSION}/extra
 }
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-bsp/x-load/x-load_git.bb b/recipes-bsp/x-load/x-load_git.bb
index dd8bce2d..1ce1b0f0 100644
--- a/recipes-bsp/x-load/x-load_git.bb
+++ b/recipes-bsp/x-load/x-load_git.bb
@@ -17,3 +17,6 @@ CONFIG_HEADER_beagleboard = "1"
 XLOAD_MACHINE_omap3-touchbook = "omap3530beagle_config"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-graphics/gbm/libgbm_10.0.0.bb 
b/recipes-graphics/gbm/libgbm_10.0.0.bb
index 38715ccf..9e3c7ed0 100644
--- a/recipes-graphics/gbm/libgbm_10.0.0.bb
+++ b/recipes-graphics/gbm/libgbm_10.0.0.bb
@@ -16,3 +16,6 @@ SRC_URI = 
"git://git.ti.com/glsdk/libgbm.git;protocol=git;branch=${BRANCH} \
 
file://0001-gbm.c-include-sys-sysmacros.h-for-minor-major-in-new.patch"
 
 S = "${WORKDIR}/git"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
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 dafaac1e..a2f8f192 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
@@ -37,3 +37,6 @@ do_install() {
 }
 
 INSANE_SKIP_${PN} += "ldflags"
+
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-graphics/omapfbplay/omapfbplay.inc 
b/recipes-graphics/omapfbplay/omapfbplay.inc
index df166dd3..744eb8f7 100644
--- a/recipes-graphics/omapfbplay/omapfbplay.inc
+++ b/recipes-graphics/omapfbplay/omapfbplay.inc
@@ -14,6 +14,8 @@ SRC_URI = "git://git.mansr.com/omapfbplay;protocol=git \
 S = "${WORKDIR}/git"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
 
 # We want a kernel header for armv7a, but we don't want to make mplayer 
machine specific for that
 STAGING_KERNEL_DIR = 
"${STAGING_DIR}/${MACHINE_ARCH}${TARGET_VENDOR}-${TARGET_OS}/kernel"
diff --git a/recipes-multimedia/libdce/libdce_3.00.14.00.bb 
b/recipes-multimedia/libdce/libdce_3.00.14.00.bb
index 04c0b718..0deec7ab 100644
--- a/recipes-multimedia/libdce/libdce_3.00.14.00.bb
+++ b/recipes-multimedia/libdce/libdce_3.00.14.00.bb
@@ -13,3 +13,5 @@ PR = "r1"
 
 S = "${WORKDIR}/git"
 EXTRA_OECONF += "IPC_HEADERS=${STAGING_INCDIR}/ti/ipc/mm"
+COMPATIBLE_HOST ?= "null"
+COMPATIBLE_HOST_ti-soc = "(.*)"
diff --git a/recipes-ti/bios/ti-biosutils_1.02.02.bb 
b/recipes-ti/bios/ti-biosutils_1.02.02.bb
index 5b6b4f43..01c070d7 100644
--- a/recipes-ti/bios/ti-biosutils_1.02.02.bb
+++ b/recipes-ti/bios/ti-biosutils_1.02.02.bb
@@ -7,3 +7,6 @@ SRC_URI[bio

[meta-ti] [PATCH] doxygen: Set DISABLE_STATIC to be empty

[Khem Raj]

by default its set like this
DISABLE_STATIC ?= " --disable-static"

but doxygen configure is not typical autoconf
generated so this option is not available, its
better to keep it empty so it can work with
dustros which disable static libs as policy

Signed-off-by: Khem Raj 
---
 recipes-devtools/doxygen/doxygen_1.8.9.1.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/recipes-devtools/doxygen/doxygen_1.8.9.1.bb 
b/recipes-devtools/doxygen/doxygen_1.8.9.1.bb
index 27560fdd..eb43e741 100644
--- a/recipes-devtools/doxygen/doxygen_1.8.9.1.bb
+++ b/recipes-devtools/doxygen/doxygen_1.8.9.1.bb
@@ -14,6 +14,8 @@ SRC_URI[sha256sum] = 
"d4ab6e28d4d45d8956cad17470aade3fbe2356e8f64b92167e738c1887
 
 EXTRA_OECONF = "--prefix ${prefix}"
 
+DISABLE_STATIC = ""
+
 do_configure () {
./configure ${EXTRA_OECONF}
 
-- 
2.19.1

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

[meta-ti] [PATCH] cm3-pm-firmware: Use ffreestanding in cflags

[Khem Raj]

This helps it compile when we use hard-float ABI for linux
and want to build this standlone app using same toolchain for
cortex-m3 ( which does not have FPU )

Signed-off-by: Khem Raj 
---
 recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb   |  8 ++--
 .../files/0001-Use-ffreestanding.patch| 39 +++
 2 files changed, 43 insertions(+), 4 deletions(-)
 create mode 100644 
recipes-bsp/cm3-pm-firmware/files/0001-Use-ffreestanding.patch

diff --git a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb 
b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
index 1dcc021c..3572638d 100644
--- a/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
+++ b/recipes-bsp/cm3-pm-firmware/amx3-cm3_git.bb
@@ -9,14 +9,14 @@ PR = "r0"
 SRCREV = "7eb9c0856a9e8b3b42bf64f761da135852b8eea7"
 BRANCH ?= "ti-v4.1.y"
 
-SRC_URI = 
"git://git.ti.com/processor-firmware/ti-amx3-cm3-pm-firmware.git;protocol=git;branch=${BRANCH}"
+SRC_URI = 
"git://git.ti.com/processor-firmware/ti-amx3-cm3-pm-firmware.git;protocol=git;branch=${BRANCH}
 \
+   file://0001-Use-ffreestanding.patch \
+  "
 
 S = "${WORKDIR}/git"
 
-FLOATABI = "${@bb.utils.contains("TUNE_FEATURES", "vfp", 
bb.utils.contains("TUNE_FEATURES", "callconvention-hard", " -mfloat-abi=hard", 
" -mfloat-abi=softfp", d), "" ,d)}"
-
 do_compile() {
-   make CROSS_COMPILE="${TARGET_PREFIX}" CC="${TARGET_PREFIX}gcc 
${TOOLCHAIN_OPTIONS} ${FLOATABI} ${SECURITY_NOPIE_CFLAGS}"
+   make CROSS_COMPILE="${TARGET_PREFIX}" CC="${TARGET_PREFIX}gcc 
${TOOLCHAIN_OPTIONS} ${SECURITY_NOPIE_CFLAGS}"
 }
 
 do_install() {
diff --git a/recipes-bsp/cm3-pm-firmware/files/0001-Use-ffreestanding.patch 
b/recipes-bsp/cm3-pm-firmware/files/0001-Use-ffreestanding.patch
new file mode 100644
index ..701d2956
--- /dev/null
+++ b/recipes-bsp/cm3-pm-firmware/files/0001-Use-ffreestanding.patch
@@ -0,0 +1,39 @@
+From 8f19f63a6fa65ce0fc4de2162d6aaeb6a92fedd9 Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Mon, 8 Oct 2018 18:15:13 -0700
+Subject: [PATCH] Use -ffreestanding
+
+When compiled using hosted toolchains e.g. default Linux targetted
+toolchains from OpenEmbedded, we need to ensure that none of hosted
+nature of toolchain is manifested and its compiled as a standalone
+baremetal application. In addition to using -nostdlib we also need to
+specify -ffreestanding so it does not include linux specific compiler
+headers etc.
+
+This means that the floating point config defaults of toolchain is not
+looking for platform specific headers e.g. gnu/stubs-soft.h or
+gnu/stubs-hard.h, since OE make it free choice to use hard-fp calling
+convention ABI choice, this change ensures it does not affect compiling
+this baremetal application
+
+Signed-off-by: Khem Raj 
+---
+ Makefile | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/Makefile b/Makefile
+index f1c10ae..3fd9f23 100644
+--- a/Makefile
 b/Makefile
+@@ -13,7 +13,7 @@ SRCDIR = src
+ BINDIR = bin
+ 
+ INCLUDES = $(SRCDIR)/include
+-CFLAGS =-mcpu=cortex-m3 -mthumb -nostdlib -Wall -Wundef \
++CFLAGS =-mcpu=cortex-m3 -mthumb -nostdlib -ffreestanding -Wall -Wundef \
+   -Werror-implicit-function-declaration -Wstrict-prototypes \
+   -Wdeclaration-after-statement -fno-delete-null-pointer-checks \
+   -Wempty-body -fno-strict-overflow  -g -I$(INCLUDES) -O2 -MD
+-- 
+2.19.1
+
-- 
2.19.1

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

[meta-ti] [PATCH] layer.conf: Add thud to compatible layer series

[Khem Raj]

Signed-off-by: Khem Raj 
---
 conf/layer.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/layer.conf b/conf/layer.conf
index cfa97783..824443d4 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "meta-ti"
 BBFILE_PATTERN_meta-ti := "^${LAYERDIR}/"
 BBFILE_PRIORITY_meta-ti = "6"
 
-LAYERSERIES_COMPAT_meta-ti = "sumo"
+LAYERSERIES_COMPAT_meta-ti = "sumo thud"
 
 LICENSE_PATH += "${LAYERDIR}/licenses"
 
-- 
2.19.0

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

Re: [meta-ti] [master][PATCH] beaglebone: drop check for meta-yocto-bsp collision

[Khem Raj]

On 2/5/18 5:43 PM, Denys Dmytriyenko wrote:

From: Denys Dmytriyenko 

Now that meta-yocto-bsp renamed reference machine to beaglebone-yocto


thats a good move finally.



Signed-off-by: Denys Dmytriyenko 
---
  conf/machine/beaglebone.conf|  1 -
  conf/machine/include/beaglebone.inc | 12 
  2 files changed, 13 deletions(-)
  delete mode 100644 conf/machine/include/beaglebone.inc

diff --git a/conf/machine/beaglebone.conf b/conf/machine/beaglebone.conf
index 715d2f2..a73bf22 100644
--- a/conf/machine/beaglebone.conf
+++ b/conf/machine/beaglebone.conf
@@ -3,7 +3,6 @@
  #@DESCRIPTION: Machine configuration for the http://beagleboard.org/bone board
  
  require conf/machine/include/ti33x.inc

-require conf/machine/include/beaglebone.inc
  
  KERNEL_DEVICETREE = "am335x-bone.dtb am335x-boneblack.dtb am335x-bonegreen.dtb"
  
diff --git a/conf/machine/include/beaglebone.inc b/conf/machine/include/beaglebone.inc

deleted file mode 100644
index b10146d..000
--- a/conf/machine/include/beaglebone.inc
+++ /dev/null
@@ -1,12 +0,0 @@
-python () {
-layers = d.getVar("BBFILE_COLLECTIONS", True)
-if not layers:
-return
-if "yoctobsp" in layers:
-bb.fatal("\nmeta-yocto-bsp has been detected in bblayers.conf, which 
provides basic reference BSP for beaglebone platform. " \
-"\nSince meta-ti provides official comprehensive BSP for TI SoCs, 
including beaglebone, there could be potential conflicts " \
-"\nbetween beaglebone machine definitions available in 
meta-yocto-bsp and meta-ti layers. It is recommended to remove " \
-"\nor disable meta-yocto-bsp in bblayers.conf, when using meta-ti 
and building for beaglebone platform. Alternatively, " \
-"\nit is possible to build for am335x-evm with meta-ti, which is a 
more generic platform for Sitara AM335x SoC and " \
-"\nalso covers beaglebone variants.")
-}


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

Re: [meta-ti] [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency

[Khem Raj]

On Fri, Mar 17, 2017 at 1:08 PM, Denys Dmytriyenko <de...@ti.com> wrote:
> On Fri, Mar 17, 2017 at 12:12:24PM -0700, Khem Raj wrote:
>> On Fri, Mar 17, 2017 at 12:04 PM, Denys Dmytriyenko <de...@ti.com> wrote:
>> > On Fri, Mar 17, 2017 at 11:57:04AM -0700, Khem Raj wrote:
>> >> On Fri, Mar 17, 2017 at 10:14 AM, Fathi Boudra <fathi.bou...@linaro.org> 
>> >> wrote:
>> >> > On 17 March 2017 at 19:06, Denys Dmytriyenko <de...@denix.org> wrote:
>> >> >> On Fri, Mar 17, 2017 at 07:03:55PM +0200, Fathi Boudra wrote:
>> >> >>> On 17 March 2017 at 18:59, Denys Dmytriyenko <de...@denix.org> wrote:
>> >> >>> > On Fri, Mar 17, 2017 at 04:47:59PM +, Khem Raj wrote:
>> >> >>> >> On Fri, Mar 17, 2017 at 9:37 AM Fathi Boudra 
>> >> >>> >> <fathi.bou...@linaro.org>
>> >> >>> >> wrote:
>> >> >>> >>
>> >> >>> >> > libpcap-ng is required to build capabilities tests.
>> >> >>> >> >
>> >> >>> >> > Signed-off-by: Fathi Boudra <fathi.bou...@linaro.org>
>> >> >>> >> > ---
>> >> >>> >> >  recipes-kernel/kselftests/kselftests_4.9.bb | 4 +---
>> >> >>> >> >  1 file changed, 1 insertion(+), 3 deletions(-)
>> >> >>> >> >
>> >> >>> >> > diff --git a/recipes-kernel/kselftests/kselftests_4.9.bb
>> >> >>> >> > b/recipes-kernel/kselftests/kselftests_4.9.bb
>> >> >>> >> > index a7b4ba67..dd94a65b 100644
>> >> >>> >> > --- a/recipes-kernel/kselftests/kselftests_4.9.bb
>> >> >>> >> > +++ b/recipes-kernel/kselftests/kselftests_4.9.bb
>> >> >>> >> > @@ -11,7 +11,7 @@ S = "${WORKDIR}/linux-${PV}"
>> >> >>> >> >
>> >> >>> >> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
>> >> >>> >> >
>> >> >>> >> > -DEPENDS = "libcap popt rsync-native"
>> >> >>> >> > +DEPENDS = "libcap libcap-ng popt rsync-native"
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> Would ng replace old libcap
>> >> >>> >
>> >> >>> > Are you asking in general or in this particular case?
>> >> >>> >
>> >> >>> > kselftests-capabilities does use libcap-ng and includes cap-ng.h 
>> >> >>> > header file,
>> >> >>> > as I mentioned here:
>> >> >>> > https://lists.yoctoproject.org/pipermail/meta-ti/2017-March/009766.html
>> >> >>> >
>> >> >>> > Fathi's fix is indeed better, even though adding another dependency.
>> >> >>>
>> >> >>> In this particular case, it doesn't replace libcap.
>> >> >>> Upstream managed to use libcap-ng in capabilities test and libpcap in
>> >> >>> bpf test...
>> >> >>> I'm currently queuing patches for upstream.
>> >> >>
>> >> >> What the status of the old libcap? Is it being deprecated everywhere?
>> >> >
>> >> > The traditional libcap is still mainly used. I don't think it's going
>> >> > to be deprecated soon, systemd is using it for example.
>> >> >
>> >>
>> >> can both libs live together without stepping on each other ?
>> >
>> > FWIW, I haven't tested on all platforms yet (still crunching), but the 
>> > initial
>> > results I'm getting here show no build, stage or run-time issues with 
>> > images
>> > that include both kselftests and systemd...
>> >
>>
>> OK you might want to compare the contents of both packages
>> and see if there are any changes that can have effect on behavior subtly.
>
> Looked at all the packaged stuff - cap-ng is very careful to maintain separate
> namespace. There are no conflicts in packaged files - headers, libraries,
> aclocal, pkgconfig, etc. all have cap-ng in the name. Even the new API in the
> header file uses CAPNG_* enums and capng_*() functions:
> https://sourcecodebrowser.com/libcap-ng/0.6.5/cap-ng_8h.html
>

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

Re: [meta-ti] [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency

[Khem Raj]

On Fri, Mar 17, 2017 at 12:04 PM, Denys Dmytriyenko <de...@ti.com> wrote:
> On Fri, Mar 17, 2017 at 11:57:04AM -0700, Khem Raj wrote:
>> On Fri, Mar 17, 2017 at 10:14 AM, Fathi Boudra <fathi.bou...@linaro.org> 
>> wrote:
>> > On 17 March 2017 at 19:06, Denys Dmytriyenko <de...@denix.org> wrote:
>> >> On Fri, Mar 17, 2017 at 07:03:55PM +0200, Fathi Boudra wrote:
>> >>> On 17 March 2017 at 18:59, Denys Dmytriyenko <de...@denix.org> wrote:
>> >>> > On Fri, Mar 17, 2017 at 04:47:59PM +, Khem Raj wrote:
>> >>> >> On Fri, Mar 17, 2017 at 9:37 AM Fathi Boudra <fathi.bou...@linaro.org>
>> >>> >> wrote:
>> >>> >>
>> >>> >> > libpcap-ng is required to build capabilities tests.
>> >>> >> >
>> >>> >> > Signed-off-by: Fathi Boudra <fathi.bou...@linaro.org>
>> >>> >> > ---
>> >>> >> >  recipes-kernel/kselftests/kselftests_4.9.bb | 4 +---
>> >>> >> >  1 file changed, 1 insertion(+), 3 deletions(-)
>> >>> >> >
>> >>> >> > diff --git a/recipes-kernel/kselftests/kselftests_4.9.bb
>> >>> >> > b/recipes-kernel/kselftests/kselftests_4.9.bb
>> >>> >> > index a7b4ba67..dd94a65b 100644
>> >>> >> > --- a/recipes-kernel/kselftests/kselftests_4.9.bb
>> >>> >> > +++ b/recipes-kernel/kselftests/kselftests_4.9.bb
>> >>> >> > @@ -11,7 +11,7 @@ S = "${WORKDIR}/linux-${PV}"
>> >>> >> >
>> >>> >> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
>> >>> >> >
>> >>> >> > -DEPENDS = "libcap popt rsync-native"
>> >>> >> > +DEPENDS = "libcap libcap-ng popt rsync-native"
>> >>> >>
>> >>> >>
>> >>> >> Would ng replace old libcap
>> >>> >
>> >>> > Are you asking in general or in this particular case?
>> >>> >
>> >>> > kselftests-capabilities does use libcap-ng and includes cap-ng.h 
>> >>> > header file,
>> >>> > as I mentioned here:
>> >>> > https://lists.yoctoproject.org/pipermail/meta-ti/2017-March/009766.html
>> >>> >
>> >>> > Fathi's fix is indeed better, even though adding another dependency.
>> >>>
>> >>> In this particular case, it doesn't replace libcap.
>> >>> Upstream managed to use libcap-ng in capabilities test and libpcap in
>> >>> bpf test...
>> >>> I'm currently queuing patches for upstream.
>> >>
>> >> What the status of the old libcap? Is it being deprecated everywhere?
>> >
>> > The traditional libcap is still mainly used. I don't think it's going
>> > to be deprecated soon, systemd is using it for example.
>> >
>>
>> can both libs live together without stepping on each other ?
>
> FWIW, I haven't tested on all platforms yet (still crunching), but the initial
> results I'm getting here show no build, stage or run-time issues with images
> that include both kselftests and systemd...
>

OK you might want to compare the contents of both packages
and see if there are any changes that can have effect on behavior subtly.

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

Re: [meta-ti] [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency

[Khem Raj]

On Fri, Mar 17, 2017 at 10:14 AM, Fathi Boudra <fathi.bou...@linaro.org> wrote:
> On 17 March 2017 at 19:06, Denys Dmytriyenko <de...@denix.org> wrote:
>> On Fri, Mar 17, 2017 at 07:03:55PM +0200, Fathi Boudra wrote:
>>> On 17 March 2017 at 18:59, Denys Dmytriyenko <de...@denix.org> wrote:
>>> > On Fri, Mar 17, 2017 at 04:47:59PM +, Khem Raj wrote:
>>> >> On Fri, Mar 17, 2017 at 9:37 AM Fathi Boudra <fathi.bou...@linaro.org>
>>> >> wrote:
>>> >>
>>> >> > libpcap-ng is required to build capabilities tests.
>>> >> >
>>> >> > Signed-off-by: Fathi Boudra <fathi.bou...@linaro.org>
>>> >> > ---
>>> >> >  recipes-kernel/kselftests/kselftests_4.9.bb | 4 +---
>>> >> >  1 file changed, 1 insertion(+), 3 deletions(-)
>>> >> >
>>> >> > diff --git a/recipes-kernel/kselftests/kselftests_4.9.bb
>>> >> > b/recipes-kernel/kselftests/kselftests_4.9.bb
>>> >> > index a7b4ba67..dd94a65b 100644
>>> >> > --- a/recipes-kernel/kselftests/kselftests_4.9.bb
>>> >> > +++ b/recipes-kernel/kselftests/kselftests_4.9.bb
>>> >> > @@ -11,7 +11,7 @@ S = "${WORKDIR}/linux-${PV}"
>>> >> >
>>> >> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
>>> >> >
>>> >> > -DEPENDS = "libcap popt rsync-native"
>>> >> > +DEPENDS = "libcap libcap-ng popt rsync-native"
>>> >>
>>> >>
>>> >> Would ng replace old libcap
>>> >
>>> > Are you asking in general or in this particular case?
>>> >
>>> > kselftests-capabilities does use libcap-ng and includes cap-ng.h header 
>>> > file,
>>> > as I mentioned here:
>>> > https://lists.yoctoproject.org/pipermail/meta-ti/2017-March/009766.html
>>> >
>>> > Fathi's fix is indeed better, even though adding another dependency.
>>>
>>> In this particular case, it doesn't replace libcap.
>>> Upstream managed to use libcap-ng in capabilities test and libpcap in
>>> bpf test...
>>> I'm currently queuing patches for upstream.
>>
>> What the status of the old libcap? Is it being deprecated everywhere?
>
> The traditional libcap is still mainly used. I don't think it's going
> to be deprecated soon, systemd is using it for example.
>

can both libs live together without stepping on each other ?
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency

[Khem Raj]

On Fri, Mar 17, 2017 at 9:37 AM Fathi Boudra 
wrote:

> libpcap-ng is required to build capabilities tests.
>
> Signed-off-by: Fathi Boudra 
> ---
>  recipes-kernel/kselftests/kselftests_4.9.bb | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/recipes-kernel/kselftests/kselftests_4.9.bb
> b/recipes-kernel/kselftests/kselftests_4.9.bb
> index a7b4ba67..dd94a65b 100644
> --- a/recipes-kernel/kselftests/kselftests_4.9.bb
> +++ b/recipes-kernel/kselftests/kselftests_4.9.bb
> @@ -11,7 +11,7 @@ S = "${WORKDIR}/linux-${PV}"
>
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>
> -DEPENDS = "libcap popt rsync-native"
> +DEPENDS = "libcap libcap-ng popt rsync-native"


Would ng replace old libcap

>
>
>  inherit kernel-arch
>
> @@ -139,8 +139,6 @@ FILES_${PN}-x86 = "${bindir}/kselftests/x86"
>  FILES_${PN}-zram = "${bindir}/kselftests/zram"
>  FILES_${PN}-dbg += "${bindir}/kselftests/*/.debug"
>
> -ALLOW_EMPTY_${PN}-capabilities = "1"
> -
>  RDEPENDS_${PN}-cpu-hotplug += "bash"
>  RDEPENDS_${PN}-efivarfs += "bash"
>  RDEPENDS_${PN}-memory-hotplug += "bash"
> --
> 2.11.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] Getting TI tools into [host] SDK

[Khem Raj]

On 3/10/17 6:27 PM, Denys Dmytriyenko wrote:
> On Fri, Mar 10, 2017 at 06:00:20PM -0800, Khem Raj wrote:
>>
>>
>> On 3/10/17 5:47 PM, Denys Dmytriyenko wrote:
>>> On Wed, Mar 08, 2017 at 09:03:28AM -0800, Khem Raj wrote:
>>>> On 17-03-08 09:10:18, Gary Thomas wrote:
>>>>> I'm trying to build a [host] SDK for my target which uses some
>>>>> TI tools, via -c populate_sdk_ext
>>>
>>> Gary,
>>>
>>> We don't use -c populate_sdk to produce SDKs. Instead, we still rely on the 
>>> old meta-toolchain mechanism. First, because it can be incorporated into 
>>> other 
>>> recipes - i.e. we have a recipe that combines rootfs and SDK into one 
>>> tarball. 
>>> Second, it provides more control to what get's packaged into SDK. Third, it 
>>> doesn't have this undefined magic to packaging stuff - i.e. this post is an 
>>> example of it failing. And only one slight drawback - requires keeping 
>>> rootfs 
>>> image recipe in sync with meta-toolchain SDK recipe...
>>>
>>>
>>>>> In particular, I'm using recipes-ti/devtools/ti-cgt-pru_2.1.4.bb
>>>>> I include ti-cgt-pru-native to use the tools in my bitbake recipes - that 
>>>>> works fine.
>>>>> I include ti-cgt-pru in my target image to get the tools on my board - 
>>>>> that also works.
>>>>>
>>>>> The problem is that in my SDK, none of the binaries are included, 
>>>>> including clpru:
>>>>>
>>>>> $ ls -l 
>>>>> /home/gthomas/my_ti_sdk/tmp/sysroots/rainier-p8701/usr/share/ti/cgt-pru
>>>>> total 16
>>>>> drwxrwxr-x 2 gthomas gthomas 12288 Mar  8 08:22 include
>>>>> drwxrwxr-x 3 gthomas gthomas  4096 Mar  8 08:22 lib
>>>>>
>>>>> I added this to try and include the files:
>>>>>   TOOLCHAIN_HOST_TASK += "'nativesdk-ti-cgt-pru"
>>>>> and I can see that there was a nativesdk-ti-cgt-pru built which does have 
>>>>> all the
>>>>> executables included, they just aren't being packaged.
>>>>>
>>>>> $ ls 
>>>>> tmp/work/x86_64-nativesdk-mysdk-linux/nativesdk-ti-cgt-pru/2.1.4-r0/image/opt/mydistro/2.2+snapshot/sysroots/x86_64-amltdsdk-linux/usr/share/ti/cgt-pru/bin
>>>>
>>>> perhaps you need to correct the install location for nativesdk may be
>>>> via overriding do_install
>>>
>>> Why?
>>
>> because  /usr/share doesnt look normal place for putting executables.
> 
> True in general, but that shouldn't matter. FILES_${PN} lists those and that 
> should be enough. It appears you are just guessing...
> 
> Sidenote:
> This PRU CodeGen toolchain is kind of weird - it targets PRUs (Programmable 
> Real-time Units http://elinux.org/Ti_AM33XX_PRUSSv2) and provides binaries in 
> bin/, headers in include/ and libraries in lib/ directories. Some of the 
> names 
> collide with system (e.g. libc.a) and hence cannot be installed in standard 
> locations, thus /usr/share. In fact, many of non-Linux specific components 
> that deal with specialized cores (i.e. non-general-purpose ARM, such as DSP, 
> PRU, IPU, numerous Cortex-M accelerators, etc.) are in fact as weird and are 
> also getting installed in /usr/share to not confuse people and not conflict 
> with the rest of the system...
> 

it would be better to have multiple sysroots for all these variants
would be way simpler and understandable, but why do I care.

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

Re: [meta-ti] Getting TI tools into [host] SDK

[Khem Raj]

On 3/10/17 5:47 PM, Denys Dmytriyenko wrote:
> On Wed, Mar 08, 2017 at 09:03:28AM -0800, Khem Raj wrote:
>> On 17-03-08 09:10:18, Gary Thomas wrote:
>>> I'm trying to build a [host] SDK for my target which uses some
>>> TI tools, via -c populate_sdk_ext
> 
> Gary,
> 
> We don't use -c populate_sdk to produce SDKs. Instead, we still rely on the 
> old meta-toolchain mechanism. First, because it can be incorporated into 
> other 
> recipes - i.e. we have a recipe that combines rootfs and SDK into one 
> tarball. 
> Second, it provides more control to what get's packaged into SDK. Third, it 
> doesn't have this undefined magic to packaging stuff - i.e. this post is an 
> example of it failing. And only one slight drawback - requires keeping rootfs 
> image recipe in sync with meta-toolchain SDK recipe...
> 
> 
>>> In particular, I'm using recipes-ti/devtools/ti-cgt-pru_2.1.4.bb
>>> I include ti-cgt-pru-native to use the tools in my bitbake recipes - that 
>>> works fine.
>>> I include ti-cgt-pru in my target image to get the tools on my board - that 
>>> also works.
>>>
>>> The problem is that in my SDK, none of the binaries are included, including 
>>> clpru:
>>>
>>> $ ls -l 
>>> /home/gthomas/my_ti_sdk/tmp/sysroots/rainier-p8701/usr/share/ti/cgt-pru
>>> total 16
>>> drwxrwxr-x 2 gthomas gthomas 12288 Mar  8 08:22 include
>>> drwxrwxr-x 3 gthomas gthomas  4096 Mar  8 08:22 lib
>>>
>>> I added this to try and include the files:
>>>   TOOLCHAIN_HOST_TASK += "'nativesdk-ti-cgt-pru"
>>> and I can see that there was a nativesdk-ti-cgt-pru built which does have 
>>> all the
>>> executables included, they just aren't being packaged.
>>>
>>> $ ls 
>>> tmp/work/x86_64-nativesdk-mysdk-linux/nativesdk-ti-cgt-pru/2.1.4-r0/image/opt/mydistro/2.2+snapshot/sysroots/x86_64-amltdsdk-linux/usr/share/ti/cgt-pru/bin
>>
>> perhaps you need to correct the install location for nativesdk may be
>> via overriding do_install
> 
> Why?
> 

because  /usr/share doesnt look normal place for putting executables.
-- 
___
meta-ti mailing list
meta-ti@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-ti

Re: [meta-ti] Getting TI tools into [host] SDK

[Khem Raj]

On 17-03-08 09:10:18, Gary Thomas wrote:
> I'm trying to build a [host] SDK for my target which uses some
> TI tools, via -c populate_sdk_ext
> 
> In particular, I'm using recipes-ti/devtools/ti-cgt-pru_2.1.4.bb
> I include ti-cgt-pru-native to use the tools in my bitbake recipes - that 
> works fine.
> I include ti-cgt-pru in my target image to get the tools on my board - that 
> also works.
> 
> The problem is that in my SDK, none of the binaries are included, including 
> clpru:
> 
> $ ls -l 
> /home/gthomas/my_ti_sdk/tmp/sysroots/rainier-p8701/usr/share/ti/cgt-pru
> total 16
> drwxrwxr-x 2 gthomas gthomas 12288 Mar  8 08:22 include
> drwxrwxr-x 3 gthomas gthomas  4096 Mar  8 08:22 lib
> 
> I added this to try and include the files:
>   TOOLCHAIN_HOST_TASK += "'nativesdk-ti-cgt-pru"
> and I can see that there was a nativesdk-ti-cgt-pru built which does have all 
> the
> executables included, they just aren't being packaged.
> 
> $ ls 
> tmp/work/x86_64-nativesdk-mysdk-linux/nativesdk-ti-cgt-pru/2.1.4-r0/image/opt/mydistro/2.2+snapshot/sysroots/x86_64-amltdsdk-linux/usr/share/ti/cgt-pru/bin

perhaps you need to correct the install location for nativesdk may be
via overriding do_install

> abspruarpru   cgpru clpru   dispruhexpru  libinfopru  nmpru   
> optpruxrefpru
> acpiapru  asmpru  clistpru  dempru  embedpru  ilkpru  lnkpru  ofdpru  
> strippru
> 
> Any ideas on what I need to do to get the binary executables into my SDK?
> 
> Note: I copied just those (bin) files into my SDK target sysroot usr/bin and 
> the compiler
> runs just fine.  I just need to figure out the recipe magic to make this 
> happen.
> 
> Thanks
> 
> -- 
> 
> Gary Thomas |  Consulting for the
> MLB Associates  |Embedded world
> 
> -- 
> ___
> 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