Skip to contentSkip to conversation

packagegroup-arago-tisdk-addons-sdk-target: Add ti-rpmsg-char dev packages

PATCH Superseded Suman Anna 4 participants 15 messages Oct 27, 2020 – Nov 9, 2020

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore

Suman Anna

author
#0 lore raw

PATCH 1/1 packagegroup-arago-tisdk-addons-sdk-target: Add ti-rpmsg-char dev packages

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

---
 .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                         elfutils-staticdev \
 "
 UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
 EXTRA_LIBS = ""
 EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0
#1 lore raw
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Quoted 33 lines
---
 .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                         elfutils-staticdev \
 "
 UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
 EXTRA_LIBS = ""
 EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0
author
#2 lore raw
Quoted 7 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs correcting?

regards
Suman

Quoted 35 lines
Quoted 35 lines
---
 .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                         elfutils-staticdev \
 "
 UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
 EXTRA_LIBS = ""
 EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0
#3 lore raw
Quoted 11 lines · Suman Anna
Quoted 7 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs correcting?

It depends on what you actually need.

Quoted 34 lines
Quoted 33 lines
Quoted 33 lines
---
 .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                         elfutils-staticdev \
 "
 UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
 EXTRA_LIBS = ""
 EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0
author
#4 lore raw

Hi Denys,

Quoted 7 lines · Denys Dmytriyenko
Quoted 6 lines · Suman Anna
Quoted 5 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs correcting?

It depends on what you actually need.

I want the files from the ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

regards
Suman

Quoted 36 lines
Quoted 36 lines
Quoted 35 lines
Quoted 35 lines
---
 .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                         elfutils-staticdev \
 "
 UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
 EXTRA_LIBS = ""
 EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0
#5 lore raw
Quoted 13 lines · Suman Anna

Hi Denys,

Quoted 10 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna
Quoted 7 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

Hmm, is this supposed to go into a different file or my patch description needs correcting?

It depends on what you actually need.

I want the files from the ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 40 lines

regards
Suman

Quoted 36 lines
Quoted 36 lines
Quoted 35 lines
Quoted 35 lines
---
 .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                         elfutils-staticdev \
 "
 UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
 EXTRA_LIBS = ""
 EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0
#6 lore raw

Suman

Quoted 57 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna

Hi Denys,

Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna
Quoted 4 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
Quoted 2 lines

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs correcting?

It depends on what you actually need.

I want the files from the ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 32 lines

regards
Suman

Quoted 29 lines
Quoted 29 lines
Quoted 29 lines
Quoted 29 lines
---
  .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
  1 file changed, 6 insertions(+), 2 deletions(-)
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +6 -2
index e372dd67744e..b55c79a4d4df 100644
@@ -1,6 +1,6 @@
  DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
  LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
 
  PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                          elfutils-staticdev \
  "
  UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+	can-utils-dev \
+	ti-rpmsg-char-dev \
+	ti-rpmsg-char-staticdev \
+"
 
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb +0 -0
  EXTRA_LIBS = ""
  EXTRA_LIBS_append_ti43x = "\
Signature · 1 line
2.28.0

Does this need to go in or are you going to send in v2?

Dan

author
#7 lore raw

Hi Dan,

Quoted 64 lines · Dan Murphy

Suman

Quoted 61 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna

Hi Denys,

Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna
Quoted 4 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 36 lines

regards
Suman

Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines

---
  .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--

  1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

(quoted diff) +0 -0
@@ -1,6 +1,6 @@

  DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
  LICENSE = "MIT"

(quoted diff) +1 -1
-PR = "r43"
+PR = "r44"

    PACKAGE_ARCH = "${MACHINE_ARCH}"
  @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                          elfutils-staticdev \
  "
  UTILS_append_k2g = " can-utils-dev"

(quoted diff) +4 -1
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
    EXTRA_LIBS = ""
  EXTRA_LIBS_append_ti43x = "\
--
2.28.0

Does this need to go in or are you going to send in v2?

I am confused by the terminology above, I am not sure if I need to move this to the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE build issues.

regards
Suman

Quoted 4 lines

Dan

#8 lore raw
Quoted 76 lines · Suman Anna

Hi Dan,

Quoted 64 lines · Dan Murphy

Suman

Quoted 61 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna

Hi Denys,

Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna
Quoted 4 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 36 lines

regards
Suman

Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines

---
  .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--

  1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

(quoted diff) +0 -0
@@ -1,6 +1,6 @@

  DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
  LICENSE = "MIT"

(quoted diff) +1 -1
-PR = "r43"
+PR = "r44"

    PACKAGE_ARCH = "${MACHINE_ARCH}"
  @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                          elfutils-staticdev \
  "
  UTILS_append_k2g = " can-utils-dev"

(quoted diff) +4 -1
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
    EXTRA_LIBS = ""
  EXTRA_LIBS_append_ti43x = "\
--
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 4 lines

I am confused by the terminology above, I am not sure if I need to move this to the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Signature · 1 line
Denys
author
#9 lore raw
Quoted 98 lines · Denys Dmytriyenko
Quoted 76 lines · Suman Anna

Hi Dan,

Quoted 64 lines · Dan Murphy

Suman

Quoted 61 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna

Hi Denys,

Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna
Quoted 4 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 36 lines

regards
Suman

Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines

---
  .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--

  1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

(quoted diff) +0 -0
@@ -1,6 +1,6 @@

  DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
  LICENSE = "MIT"

(quoted diff) +1 -1
-PR = "r43"
+PR = "r44"

    PACKAGE_ARCH = "${MACHINE_ARCH}"
  @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                          elfutils-staticdev \
  "
  UTILS_append_k2g = " can-utils-dev"

(quoted diff) +4 -1
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
    EXTRA_LIBS = ""
  EXTRA_LIBS_append_ti43x = "\
--
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 4 lines

I am confused by the terminology above, I am not sure if I need to move this to the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

Quoted 7 lines

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Thanks for the explanation Denys. The ask is to be able to compile on the target, believe for some Vision Apps.

Lucas,
Can you confirm/clarify the need/usage exactly?

regards
Suman

#10 lore raw
Quoted 107 lines · Suman Anna
Quoted 98 lines · Denys Dmytriyenko
Quoted 76 lines · Suman Anna

Hi Dan,

Quoted 64 lines · Dan Murphy

Suman

Quoted 61 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna

Hi Denys,

Quoted 6 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna
Quoted 4 lines · Denys Dmytriyenko
Quoted 3 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in the target fileystem so that applications can be compiled natively on the target.

Quoted 8 lines
Quoted 6 lines
Quoted 5 lines
Quoted 2 lines

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Hmm, is this supposed to go into a different file or my patch description needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 36 lines

regards
Suman

Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
Quoted 33 lines
---
   .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8 ++++++--
   1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

(quoted diff) +0 -0
@@ -1,6 +1,6 @@
   DESCRIPTION = "Task to install headers and libraries related to addons

into the SDK"
  LICENSE = "MIT"

(quoted diff) +5 -2
-PR = "r43"
+PR = "r44"
     PACKAGE_ARCH = "${MACHINE_ARCH}"
   @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                           elfutils-staticdev \
   "
   UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
    EXTRA_LIBS = ""
  EXTRA_LIBS_append_ti43x = "\

Signature · 1 line
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 4 lines

I am confused by the terminology above, I am not sure if I need to move this to the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

Quoted 7 lines

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Quoted 5 lines

Thanks for the explanation Denys. The ask is to be able to compile on the target, believe for some Vision Apps.

Lucas,
Can you confirm/clarify the need/usage exactly?

Suman,

Sorry for the delay. We need this for cross compiling on the host, so including in the devkit should be sufficient.

Quoted 5 lines

regards
Suman

author
#11 lore raw
Quoted 122 lines · Lucas
Quoted 119 lines · Suman Anna
Quoted 107 lines · Denys Dmytriyenko
Quoted 85 lines · Suman Anna

Hi Dan,

Quoted 73 lines · Dan Murphy

Suman

Quoted 70 lines · Denys Dmytriyenko
Quoted 13 lines · Suman Anna

Hi Denys,

Quoted 10 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna
Quoted 8 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in
the target fileystem so that applications can be compiled natively on the
target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Quoted 7 lines
Quoted 4 lines
Quoted 3 lines

Hmm, is this supposed to go into a different file or my patch description needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files
and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 42 lines

regards
Suman

Quoted 39 lines
Quoted 39 lines
Quoted 39 lines
Quoted 39 lines

---
   .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8
++++++--

   1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

(quoted diff) +0 -0
@@ -1,6 +1,6 @@

   DESCRIPTION = "Task to install headers and libraries related to addons
into the SDK"
   LICENSE = "MIT"

(quoted diff) +1 -1
-PR = "r43"
+PR = "r44"

     PACKAGE_ARCH = "${MACHINE_ARCH}"
   @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                           elfutils-staticdev \
   "
   UTILS_append_k2g = " can-utils-dev"

(quoted diff) +4 -1
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
     EXTRA_LIBS = ""
   EXTRA_LIBS_append_ti43x = "\
--
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 4 lines

I am confused by the terminology above, I am not sure if I need to move this to the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

Quoted 7 lines

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Thanks for the explanation Denys. The ask is to be able to compile on the target, believe for some Vision Apps.

Quoted 6 lines
Quoted 2 lines

Lucas,
Can you confirm/clarify the need/usage exactly?

Suman,

Sorry for the delay.  We need this for cross compiling on the host, so including in the devkit should be sufficient.

Lucas,

Hmm, ok. Then I misunderstood what you were asking before. So, does this patch work for you? If it is, then I will post a v2 correcting the patch description.

regards
Suman

#12 lore raw
Quoted 130 lines · Suman Anna
Quoted 122 lines · Lucas
Quoted 119 lines · Suman Anna
Quoted 107 lines · Denys Dmytriyenko
Quoted 85 lines · Suman Anna

Hi Dan,

Quoted 73 lines · Dan Murphy

Suman

Quoted 70 lines · Denys Dmytriyenko
Quoted 13 lines · Suman Anna

Hi Denys,

Quoted 10 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna
Quoted 8 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers available in
the target fileystem so that applications can be compiled natively on the
target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Quoted 7 lines
Quoted 4 lines
Quoted 3 lines

Hmm, is this supposed to go into a different file or my patch description needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files
and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 42 lines

regards
Suman

Quoted 39 lines
Quoted 39 lines
Quoted 39 lines
Quoted 39 lines
---
    .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8
++++++--
    1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

(quoted diff) +0 -0
@@ -1,6 +1,6 @@
    DESCRIPTION = "Task to install headers and libraries related to

addons
into the SDK"
   LICENSE = "MIT"

(quoted diff) +5 -2
-PR = "r43"
+PR = "r44"
      PACKAGE_ARCH = "${MACHINE_ARCH}"
    @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                            elfutils-staticdev \
    "
    UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \
Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
     EXTRA_LIBS = ""
   EXTRA_LIBS_append_ti43x = "\

Signature · 1 line
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 4 lines

I am confused by the terminology above, I am not sure if I need to move this to the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

Quoted 7 lines

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Thanks for the explanation Denys. The ask is to be able to compile on the target, believe for some Vision Apps.

Quoted 6 lines
Quoted 2 lines

Lucas,
Can you confirm/clarify the need/usage exactly?

Suman,

Sorry for the delay.  We need this for cross compiling on the host, so including in the devkit should be sufficient.

Quoted 8 lines

Lucas,

Hmm, ok. Then I misunderstood what you were asking before. So, does this patch work for you? If it is, then I will post a v2 correcting the patch description.

regards
Suman

Suman,

Sorry, I probably wasn't clear before. Yes, this looks like it will work for us.

Regards,
Lucas

author
#13 lore raw
Quoted 146 lines · Lucas
Quoted 143 lines · Suman Anna
Quoted 130 lines · Lucas
Quoted 127 lines · Suman Anna
Quoted 115 lines · Denys Dmytriyenko
Quoted 91 lines · Suman Anna

Hi Dan,

Quoted 79 lines · Dan Murphy

Suman

Quoted 76 lines · Denys Dmytriyenko
Quoted 13 lines · Suman Anna

Hi Denys,

Quoted 10 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna
Quoted 8 lines · Denys Dmytriyenko
Quoted 5 lines · Suman Anna

Add the ti-rpmsg-char dev packages to make the public headers
available in
the target fileystem so that applications can be compiled natively on
the
target.

-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Quoted 8 lines
Quoted 5 lines
Quoted 4 lines

Hmm, is this supposed to go into a different file or my patch description
needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files
and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 46 lines

regards
Suman

Quoted 43 lines
Quoted 43 lines
Quoted 43 lines
Quoted 43 lines

Signed-off-by: Suman Anna <[email protected]>
---
    .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8
++++++--
    1 file changed, 6 insertions(+), 2 deletions(-)

diff --git
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

@@ -1,6 +1,6 @@
    DESCRIPTION = "Task to install headers and libraries related to
addons
into the SDK"
    LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
      PACKAGE_ARCH = "${MACHINE_ARCH}"
    @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                            elfutils-staticdev \
    "
    UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \

Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
      EXTRA_LIBS = ""
    EXTRA_LIBS_append_ti43x = "\
--
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 6 lines

I am confused by the terminology above, I am not sure if I need to move this to
the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE
build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

Quoted 7 lines

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Thanks for the explanation Denys. The ask is to be able to compile on the target, believe for some Vision Apps.

Quoted 6 lines
Quoted 2 lines

Lucas,
Can you confirm/clarify the need/usage exactly?

Suman,

Sorry for the delay.  We need this for cross compiling on the host, so including in the devkit should be sufficient.

Lucas,

Hmm, ok. Then I misunderstood what you were asking before. So, does this patch work for you? If it is, then I will post a v2 correcting the patch description.

Quoted 6 lines
Quoted 3 lines

regards
Suman

Suman,

Sorry, I probably wasn't clear before.  Yes, this looks like it will work for us.

Lucas,

No problem. Care to give a formal Tested-by: ?

regards
Suman

Tested-by
#14 lore raw
Quoted 152 lines · Suman Anna
Quoted 151 lines · Lucas
Quoted 138 lines · Suman Anna
Quoted 130 lines · Lucas
Quoted 127 lines · Suman Anna
Quoted 115 lines · Denys Dmytriyenko
Quoted 91 lines · Suman Anna

Hi Dan,

Quoted 79 lines · Dan Murphy

Suman

Quoted 76 lines · Denys Dmytriyenko
Quoted 13 lines · Suman Anna

Hi Denys,

Quoted 10 lines · Denys Dmytriyenko
Quoted 9 lines · Suman Anna
Quoted 8 lines · Denys Dmytriyenko

On Mon, Oct 26, 2020 at 09:41:12PM -0500, Suman Anna wrote:
Add the ti-rpmsg-char dev packages to make the public headers
available in
the target fileystem so that applications can be compiled natively on
the
target.
-sdk-target is not for the target filesystem!
It is for the target sysroot in the devkit.

Quoted 8 lines
Quoted 5 lines
Quoted 4 lines

Hmm, is this supposed to go into a different file or my patch description
needs
correcting?

It depends on what you actually need.

I want the files from the  ti-rpmsg-char-dev package (the public header files
and libti_rpmsg_char.so) to be part of the FS tarball.

Then you need to pull corresponding -dev package into the packagegroup that builds up the rootfs.

At least in Arago, I kept the namespace convention that -sdk-target and -sdk-host suffixes are used to identify packagegroups for the devkit - cross-compile development environment on the host, target and host sysroots.

Quoted 46 lines

regards
Suman

Quoted 43 lines
Quoted 43 lines
Quoted 43 lines

Signed-off-by: Suman Anna <[email protected]>
---
    .../packagegroup-arago-tisdk-addons-sdk-target.bb         | 8
++++++--
    1 file changed, 6 insertions(+), 2 deletions(-)

diff --git
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

index e372dd67744e..b55c79a4d4df 100644
---
a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

+++
b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb

@@ -1,6 +1,6 @@
    DESCRIPTION = "Task to install headers and libraries related to
addons
into the SDK"
    LICENSE = "MIT"
-PR = "r43"
+PR = "r44"
      PACKAGE_ARCH = "${MACHINE_ARCH}"
    @@ -143,7 +143,11 @@ UTILS_append_dra7xx = " can-utils-dev \
                            elfutils-staticdev \
    "
    UTILS_append_k2g = " can-utils-dev"
-UTILS_append_k3 = " can-utils-dev"
+UTILS_append_k3 = "\
+    can-utils-dev \
+    ti-rpmsg-char-dev \
+    ti-rpmsg-char-staticdev \

Quoted 8 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

+"
      EXTRA_LIBS = ""
    EXTRA_LIBS_append_ti43x = "\
--
2.28.0

Does this need to go in or are you going to send in v2?

Quoted 6 lines

I am confused by the terminology above, I am not sure if I need to move this to
the packagegroup-arago-tisdk-addons.bb file, or if this is just a question of writing the proper patch description. I cannot verify myself until I fix my OE
build issues.

Suman,

If you do need these development packages on the target rootfs, then you do need to add them to packagegroup-arago-tisdk-addons.bb

But if you need them to be part of the devkit (cross-compile development environment on the host), then you need to add to the corresponding packagegroup-arago-tisdk-addons-sdk-target.bb

In other words, do you expect someone to compile natively on the target against your library and headers? Then it's the first one. But, enabling native development environment on the target should not be decided lightly. As a matter of fact, for 7.0 we removed this from the default rootfs, expecting users to be able to add it optionally from package feeds. Though public package feeds were not ready and got postponed...

Quoted 7 lines

So, my point is - what are you trying to achieve here? Why do you need -dev package on the target filesystem? If you are trying to enable other developers to build apps against your library, could they just write a recipe? Is it really necessary for the default rootfs? Anyway, hopefully these questions could guide you towards the proper solution. Please let me know if you still have questions :)

Thanks for the explanation Denys. The ask is to be able to compile on the target, believe for some Vision Apps.

Quoted 6 lines
Quoted 2 lines

Lucas,
Can you confirm/clarify the need/usage exactly?

Suman,

Sorry for the delay.  We need this for cross compiling on the host, so including in the devkit should be sufficient.

Quoted 8 lines

Lucas,

Hmm, ok. Then I misunderstood what you were asking before. So, does this patch work for you? If it is, then I will post a v2 correcting the patch description.

regards
Suman

Suman,

Quoted 9 lines
Quoted 1 line

Sorry, I probably wasn't clear before.  Yes, this looks like it will work for us.

Lucas,

No problem. Care to give a formal Tested-by: ?

regards
Suman