meta-arago-test: Add optee-test, strongswan, and libgpiod-tools to image
PATCH 1/1 meta-arago-test: Add optee-test, strongswan, and libgpiod-tools to image
These packages are used by ltp-ddt and the test framework. These are added to the default Arago images, but when doing upstream testing with Poky these packages are missing. Add these to the base testing layer.
--- meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++ meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb | 1 + 2 files changed, 3 insertions(+)
meta-arago-test/recipes-core/packagegroups/ti-test.bb +2 -0
@@ -41,6 +41,7 @@ TI_TEST_BASE = "\ nbench-byte \ netperf \ openntpd \ + optee-test \ pcitest \ perf \ powertop \
@@ -53,6 +54,7 @@ TI_TEST_BASE = "\ stream \ stress \ stress-ng \ + strongswan \ tcpdump \ v4l-utils \ yavta \
meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb +1 -0
@@ -33,6 +33,7 @@ RDEPENDS:${PN} += "\ pm-qa \ serialcheck \ memtester \ + libgpiod-tools \ " do_install:prepend() {
Signature · 1 line
2.39.2
Quoted 15 lines · Andrew Davis via lists.yoctoproject.org
These packages are used by ltp-ddt and the test framework. These are added to the default Arago images, but when doing upstream testing with Poky these packages are missing. Add these to the base testing layer.
Signed-off-by Andrew Davis <[email protected]>--- meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++ meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb | 1 + 2 files changed, 3 insertions(+)meta-arago-test/recipes-core/packagegroups/ti-test.bb +0
-0
meta-arago-test/recipes-core/packagegroups/ti-test.bb TI_TEST_BASE = "\ · line 44
Quoted 4 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0@@ -41,6 +41,7 @@ TI_TEST_BASE = "\ nbench-byte \ netperf \ openntpd \ + optee-test \
Should this be conditional on whether OPTEE is used for the platform? Like it is done here:
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb#n58
Quoted 25 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0pcitest \ perf \ powertop \@@ -53,6 +54,7 @@ TI_TEST_BASE = "\ stream \ stress \ stress-ng \ + strongswan \ tcpdump \ v4l-utils \ yavta \meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb +1
-0@@ -33,6 +33,7 @@ RDEPENDS:${PN} += "\ pm-qa \ serialcheck \ memtester \ + libgpiod-tools \ " do_install:prepend() {Signature · 1 line
2.39.2
Quoted 11 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
These packages are used by ltp-ddt and the test framework. These are added to the default Arago images, but when doing upstream testing with Poky these packages are missing. Add these to the base testing layer.
Signed-off-by Andrew Davis <[email protected]>--- meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++ meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb | 1 + 2 files changed, 3 insertions(+)
Quoted 14 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb TI_TEST_BASE = "\ · line 44
Quoted 9 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0@@ -41,6 +41,7 @@ TI_TEST_BASE = "\ nbench-byte \ netperf \ openntpd \ + optee-test \Should this be conditional on whether OPTEE is used for the platform? Like it is done here:
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb#n58
Good catch, this does need to be conditional or AM335x (the only plat we have without OP-TEE) will break, will update and resend.
Thanks,
Andrew
Quoted 26 lines
Quoted 26 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0pcitest \ perf \ powertop \@@ -53,6 +54,7 @@ TI_TEST_BASE = "\ stream \ stress \ stress-ng \ + strongswan \ tcpdump \ v4l-utils \ yavta \meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb +1
-0@@ -33,6 +33,7 @@ RDEPENDS:${PN} += "\ pm-qa \ serialcheck \ memtester \ + libgpiod-tools \ " do_install:prepend() {Signature · 1 line
2.39.2
Quoted 27 lines · Andrew Davis via lists.yoctoproject.org
Quoted 11 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
These packages are used by ltp-ddt and the test framework. These are added to the default Arago images, but when doing upstream testing with Poky these packages are missing. Add these to the base testing layer.
Signed-off-by Andrew Davis <[email protected]>--- meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++ meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb | 1 + 2 files changed, 3 insertions(+)Quoted 14 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb TI_TEST_BASE = "\ · line 44
Quoted 9 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0@@ -41,6 +41,7 @@ TI_TEST_BASE = "\ nbench-byte \ netperf \ openntpd \ + optee-test \Should this be conditional on whether OPTEE is used for the platform? Like it is done here:
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb#n58
Quoted 2 lines
Good catch, this does need to be conditional or AM335x (the only plat we have without OP-TEE) will break, will update and resend.
The other legacy platform that doesn't use OPTEE is OMAP-L138.
Also, if you recall, only HS variants of AM437x and AM57x use OP-TEE, not GP.
Quoted 28 lines
Thanks,
AndrewQuoted 25 lines
Quoted 25 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0pcitest \ perf \ powertop \@@ -53,6 +54,7 @@ TI_TEST_BASE = "\ stream \ stress \ stress-ng \ + strongswan \ tcpdump \ v4l-utils \ yavta \meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb +1
-0@@ -33,6 +33,7 @@ RDEPENDS:${PN} += "\ pm-qa \ serialcheck \ memtester \ + libgpiod-tools \ " do_install:prepend() {Signature · 1 line
2.39.2
Quoted 28 lines · Denys Dmytriyenko
Quoted 27 lines · Andrew Davis via lists.yoctoproject.org
Quoted 25 lines · Denys Dmytriyenko
Quoted 15 lines · Andrew Davis via lists.yoctoproject.org
These packages are used by ltp-ddt and the test framework. These are added to the default Arago images, but when doing upstream testing with Poky these packages are missing. Add these to the base testing layer.
Signed-off-by Andrew Davis <[email protected]>--- meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++ meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb | 1 + 2 files changed, 3 insertions(+)meta-arago-test/recipes-core/packagegroups/ti-test.bb +0
-0meta-arago-test/recipes-core/packagegroups/ti-test.bb TI_TEST_BASE = "\ · line 44
Quoted 4 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0@@ -41,6 +41,7 @@ TI_TEST_BASE = "\ nbench-byte \ netperf \ openntpd \ + optee-test \Should this be conditional on whether OPTEE is used for the platform? Like it is done here:
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb#n58
Quoted 7 lines
Quoted 2 lines
Good catch, this does need to be conditional or AM335x (the only plat we have without OP-TEE) will break, will update and resend.
The other legacy platform that doesn't use OPTEE is OMAP-L138.
Also, if you recall, only HS variants of AM437x and AM57x use OP-TEE, not GP.
Sure but these still have valid platform targets in OP-TEE, so the building the optee-test package should still work; there are no target names for AM335 (and L138) so they would cause an issue when building the OP-TEE dependency.
Side thought, I wonder if having an "optee" MACHINE_FEATURE would be a better solution than checking OPTEEOUTPUTMACHINE as done in packagegroup-arago-base.bb (which shouldn't that be OPTEEMACHINE?)
Andrew
Quoted 29 lines
Quoted 29 lines
Thanks,
AndrewQuoted 25 lines
Quoted 25 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0pcitest \ perf \ powertop \@@ -53,6 +54,7 @@ TI_TEST_BASE = "\ stream \ stress \ stress-ng \ + strongswan \ tcpdump \ v4l-utils \ yavta \meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb +1
-0@@ -33,6 +33,7 @@ RDEPENDS:${PN} += "\ pm-qa \ serialcheck \ memtester \ + libgpiod-tools \ " do_install:prepend() {Signature · 1 line
2.39.2
Quoted 32 lines · Andrew Davis
Quoted 31 lines · Denys Dmytriyenko
Quoted 29 lines · Andrew Davis via lists.yoctoproject.org
Quoted 11 lines · Denys Dmytriyenko
Quoted 10 lines · Andrew Davis via lists.yoctoproject.org
These packages are used by ltp-ddt and the test framework. These are added to the default Arago images, but when doing upstream testing with Poky these packages are missing. Add these to the base testing layer.
Signed-off-by Andrew Davis <[email protected]>--- meta-arago-test/recipes-core/packagegroups/ti-test.bb | 2 ++ meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb | 1 + 2 files changed, 3 insertions(+)Quoted 14 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb TI_TEST_BASE = "\ · line 44
Quoted 9 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0@@ -41,6 +41,7 @@ TI_TEST_BASE = "\ nbench-byte \ netperf \ openntpd \ + optee-test \Should this be conditional on whether OPTEE is used for the platform? Like it is done here:
https://git.yoctoproject.org/meta-arago/tree/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-base.bb#n58Good catch, this does need to be conditional or AM335x (the only plat we have without OP-TEE) will break, will update and resend.
Quoted 8 lines
Quoted 4 lines
The other legacy platform that doesn't use OPTEE is OMAP-L138.
Also, if you recall, only HS variants of AM437x and AM57x use OP-TEE, not GP.
Sure but these still have valid platform targets in OP-TEE, so the building the optee-test package should still work; there are no target names for AM335 (and L138) so they would cause an issue when building the OP-TEE dependency.
Those GP platforms don't set any valid OP-TEE targets, so the build will still fail.
Quoted 3 lines
Side thought, I wonder if having an "optee"
MACHINE_FEATUREwould be a better solution than checking OPTEEOUTPUTMACHINE as done in packagegroup-arago-base.bb (which shouldn't that be OPTEEMACHINE?)
Ah, indeed:
https://git.yoctoproject.org/meta-ti/commit/?id=0942b58dab47920f6d5661017720f3e5589389d4
Though OPTEEMACHINE is either "ti-am57xx" or "ti-dra7xx" or "ti-am43xx" for legacy platforms and "k3-*" for K3 platforms (though all K3 use OPTEE).
Can probably simply check if OPTEEMACHINE is defined and not empty...
Quoted 31 lines
Andrew
Quoted 29 lines
Quoted 29 lines
Thanks,
AndrewQuoted 25 lines
Quoted 25 lines
meta-arago-test/recipes-core/packagegroups/ti-test.bb +1
-0pcitest \ perf \ powertop \@@ -53,6 +54,7 @@ TI_TEST_BASE = "\ stream \ stress \ stress-ng \ + strongswan \ tcpdump \ v4l-utils \ yavta \meta-arago-test/recipes-devtools/ltp-ddt/ltp-ddt_20250130.bb +1
-0@@ -33,6 +33,7 @@ RDEPENDS:${PN} += "\ pm-qa \ serialcheck \ memtester \ + libgpiod-tools \ " do_install:prepend() {Signature · 1 line
2.39.2