Re: [meta-arago] [oe-layersetup PATCH v3] processor-sdk: Add 07.03.00.005 release config
On 8/27/2021 5:54 AM, Vigna Raja Priya N S wrote: On Fri, Aug 27, 2021 at 1:42 AM Praneeth Bajjuri wrote: On 8/26/21 5:31 AM, Priya N S wrote: Signed-off-by: Priya N S --- Hi All, This patch adds the processor-sdk-07.03.00.005-config for the AM335x and AM437x 07.03 release. Changes made in the V3 patch: * This corresponds to the 07.03 release for the am335x-evm and am437x-evm platforms. * The meta-linaro meta-layer is removed because the meta-optee needed for the build is moved to meta-arm from the dunfell. any version change log should be below --- please correct the commit message about "Changes made in the V3 patch:" .../processor-sdk-07.03.00.005-config.txt | 14 ++ 1 file changed, 14 insertions(+) create mode 100644 configs/processor-sdk/processor-sdk-07.03.00.005-config.txt diff --git a/configs/processor-sdk/processor-sdk-07.03.00.005-config.txt b/configs/processor-sdk/processor-sdk-07.03.00.005-config.txt new file mode 100644 index 000..548e759 --- /dev/null +++ b/configs/processor-sdk/processor-sdk-07.03.00.005-config.txt @@ -0,0 +1,14 @@ +# This file takes repo entries in the format +# repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] + +bitbake,git://git.openembedded.org/bitbake,1.46,017a39ed05d065bf28fd38f91bcde8a098300551 +meta-processor-sdk,git://git.ti.com/processor-sdk/meta-processor-sdk.git,dunfell,c467012684e57c914c4070238987e931f329da15,layers= this doesnt seems to be latest commit from https://git.ti.com/cgit/processor-sdk/meta-processor-sdk/log/?h=dunfell it looks atleast 27 patches behind. Please provide the reason for this difference. The release config file added in this patch is for the AM335x and AM437x GP EVM 07.03.00.005 release that has already happened on 24th May 2021 and 02nd July 2021. The config file was missed to add in the oe-layersetup repository after the release. The 27 patches mentioned were added after the release of AM335x and AM437x GP EVM. So, this is the reason for seeing the differences in the commit Ids. Can you also start using tags for meta-processor-sdk. Since 07.03 release has already happened, Yes, but you can still tag the right commitID eventhough its not on the top and update the oelayersup patch to point to tagname instead. We will loose history and dont have a read point later to demystify why we are using a older commit for the snapshot config patch after a month. we will consider using the tags in meta-processor-sdk for the upcoming releases. Please suggest. +meta-arago,git://arago-project.org/git/meta-arago.git,dunfell,07.03.00.005,layers=meta-arago-distro:meta-arago-extras +meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,b4d24d70aca75791902df5cd59a4f4a54aa4a125,layers= +meta-virtualization,git://git.yoctoproject.org/meta-virtualization,dunfell,89abc62b47f6f20db9d00a8ec9b2c1b6b60ac3f9,layers= +meta-openembedded,git://git.openembedded.org/meta-openembedded,dunfell,389757a7494221fea1d8437e9a01c6e4fb4700af,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems +meta-ti,git://git.yoctoproject.org/meta-ti,dunfell,07.03.00.005,layers= +meta-arm,git://git.yoctoproject.org/meta-arm,dunfell,c4f04f3fb66f8f4365b08b553af8206372e90a63,layers=meta-arm:meta-arm-toolchain +oe-core,git://git.openembedded.org/openembedded-core,dunfell,707036d4ec12ef1a260adcef78627b26e32e6540,layers=meta +OECORELAYERCONF=./sample-files/bblayers.conf.sample +OECORELOCALCONF=./sample-files/local-processor-sdk-64.conf.sample ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [oe-layersetup PATCH v2] processor-sdk: Add 07.03.00.005 release config
On 8/6/2021 6:48 AM, Priya N S wrote: Signed-off-by: Priya N S --- Hi All, Kindly ignore the changes made in the V1 patch and consider the V2 patch. Changes made in the V2 patch: * Added the processor-sdk-07.03.00.005-config for the 07.03 release. Why are we doing this at the time of 8.0 release ? will there be a 8.0 based config too as a separate patch later? Anyhow, this patch is a NACK. See review comments below. * This corresponds to the 07.03 release for the am335x-evm and am437x-evm platforms. .../processor-sdk-07.03.00.005-config.txt | 17 + 1 file changed, 17 insertions(+) create mode 100644 configs/processor-sdk/processor-sdk-07.03.00.005-config.txt diff --git a/configs/processor-sdk/processor-sdk-07.03.00.005-config.txt b/configs/processor-sdk/processor-sdk-07.03.00.005-config.txt new file mode 100644 index 000..09bde9e --- /dev/null +++ b/configs/processor-sdk/processor-sdk-07.03.00.005-config.txt Did the convention followed for processor-sdk change? Ex: I see 106* used for the last part of the release name (may be pointing to a build number) Ref: http://arago-project.org/git/projects/oe-layersetup.git?p=projects/oe-layersetup.git;a=commit;h=30111f3c58442c088969a548dcd6c9140c422da8 @@ -0,0 +1,17 @@ +# This file takes repo entries in the format +# repo name,repo uri,repo branch,repo commit[,layers=layer1:layer2...:layern] + +bitbake,git://git.openembedded.org/bitbake,1.46,017a39ed05d065bf28fd38f91bcde8a098300551 +meta-processor-sdk,git://git.ti.com/processor-sdk/meta-processor-sdk.git,dunfell,c467012684e57c914c4070238987e931f329da15,layers= Why commitsha and not a 07.03* tag ? Nikhil, does this look correct? +meta-arago,git://arago-project.org/git/meta-arago.git,dunfell,07.03.00.005,layers=meta-arago-distro:meta-arago-extras +meta-aws,https://github.com/aws/meta-aws.git,dunfell,HEAD,layers= HEAD >> This doesnt look right for the config snapshot. You need to pick the exact commitsha used for your release tagged images ( you should see that in build-config file) +#meta-browser,git://github.com/OSSystems/meta-browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers= +meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,b4d24d70aca75791902df5cd59a4f4a54aa4a125,layers= +meta-virtualization,git://git.yoctoproject.org/meta-virtualization,dunfell,89abc62b47f6f20db9d00a8ec9b2c1b6b60ac3f9,layers= +meta-openembedded,git://git.openembedded.org/meta-openembedded,dunfell,389757a7494221fea1d8437e9a01c6e4fb4700af,layers=meta-networking:meta-python:meta-oe:meta-gnome:meta-filesystems +meta-ti,git://git.yoctoproject.org/meta-ti,dunfell,07.03.00.005,layers= +meta-linaro,https://git.linaro.org/openembedded/meta-linaro.git,dunfell,HEAD,layers=meta-optee Similar comment as above of meta-aws. HEAD is not correct for release snapshot. By the way, why do you even need meta-linaro layer for psdkl builds? +meta-arm,git://git.yoctoproject.org/meta-arm,dunfell,c4f04f3fb66f8f4365b08b553af8206372e90a63,layers=meta-arm:meta-arm-toolchain +oe-core,git://git.openembedded.org/openembedded-core,dunfell,707036d4ec12ef1a260adcef78627b26e32e6540,layers=meta +OECORELAYERCONF=./sample-files/bblayers.conf.sample +OECORELOCALCONF=./sample-files/local-processor-sdk-64.conf.sample ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell/master][PATCH 1/4] chromium: apply bbappend with fix dynamically based on "browser-layer" presence
On 5/3/2021 4:32 PM, Denys Dmytriyenko wrote: On Mon, May 03, 2021 at 04:29:06PM -0500, Bajjuri, Praneeth wrote: On 5/3/2021 4:12 PM, Denys Dmytriyenko wrote: Praneeth, Any plans to merge this series? Even though the config is disabled by default, it does some recipe cleanup and establishes dynamic layer dependency framework. Thanks for the bump, pulled to dunfell-next. Will sync to -master in a day once the nightly build is done. Thanks! Might want to pull corresponding oe-layersetup patch as well, even though it only adds extra comments :) Pulled this one too. --Praneeth On Tue, Mar 23, 2021 at 05:15:04PM -0400, Denys Dmytriyenko wrote: From: Denys Dmytriyenko This solves the dangling bbappend warning when browser-layer is not enabled. As chromium still requires Python2, corresponding meta-python2 layer is required. Signed-off-by: Denys Dmytriyenko --- meta-arago-distro/conf/layer.conf | 4 .../chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch | 0 .../recipes-browser/chromium/chromium-ozone-wayland_%.bbappend| 0 3 files changed, 4 insertions(+) rename meta-arago-distro/{ => dynamic-layers/browser-layer}/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch (100%) rename meta-arago-distro/{ => dynamic-layers/browser-layer}/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend (100%) diff --git a/meta-arago-distro/conf/layer.conf b/meta-arago-distro/conf/layer.conf index 2931bf9..9014511 100644 --- a/meta-arago-distro/conf/layer.conf +++ b/meta-arago-distro/conf/layer.conf @@ -24,6 +24,10 @@ LAYERRECOMMENDS_meta-arago-distro = " \ browser-layer \ " +BBFILES_DYNAMIC += " \ + browser-layer:${LAYERDIR}/dynamic-layers/browser-layer/recipes*/*/*.bbappend \ +" + BB_DANGLINGAPPENDS_WARNONLY = "true" SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \ diff --git a/meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch b/meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch similarity index 100% rename from meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch rename to meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch diff --git a/meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend b/meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend similarity index 100% rename from meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend rename to meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend -- 2.7.4 ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell/master][PATCH 1/4] chromium: apply bbappend with fix dynamically based on "browser-layer" presence
On 5/3/2021 4:12 PM, Denys Dmytriyenko wrote: Praneeth, Any plans to merge this series? Even though the config is disabled by default, it does some recipe cleanup and establishes dynamic layer dependency framework. Thanks for the bump, pulled to dunfell-next. Will sync to -master in a day once the nightly build is done. --Praneeth On Tue, Mar 23, 2021 at 05:15:04PM -0400, Denys Dmytriyenko wrote: From: Denys Dmytriyenko This solves the dangling bbappend warning when browser-layer is not enabled. As chromium still requires Python2, corresponding meta-python2 layer is required. Signed-off-by: Denys Dmytriyenko --- meta-arago-distro/conf/layer.conf | 4 .../chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch | 0 .../recipes-browser/chromium/chromium-ozone-wayland_%.bbappend| 0 3 files changed, 4 insertions(+) rename meta-arago-distro/{ => dynamic-layers/browser-layer}/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch (100%) rename meta-arago-distro/{ => dynamic-layers/browser-layer}/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend (100%) diff --git a/meta-arago-distro/conf/layer.conf b/meta-arago-distro/conf/layer.conf index 2931bf9..9014511 100644 --- a/meta-arago-distro/conf/layer.conf +++ b/meta-arago-distro/conf/layer.conf @@ -24,6 +24,10 @@ LAYERRECOMMENDS_meta-arago-distro = " \ browser-layer \ " +BBFILES_DYNAMIC += " \ + browser-layer:${LAYERDIR}/dynamic-layers/browser-layer/recipes*/*/*.bbappend \ +" + BB_DANGLINGAPPENDS_WARNONLY = "true" SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS += " \ diff --git a/meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch b/meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch similarity index 100% rename from meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch rename to meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland/chromium-75.0.3770.80-SIOCGSTAMP.patch diff --git a/meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend b/meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend similarity index 100% rename from meta-arago-distro/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend rename to meta-arago-distro/dynamic-layers/browser-layer/recipes-browser/chromium/chromium-ozone-wayland_%.bbappend -- 2.7.4 ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell/master PATCH] ti-test: omap-a15: split package selection command to avoid build erros
On 4/19/2021 10:05 PM, prane...@ti.com wrote: From: Praneeth Bajjuri Split the package selection option for omap-a15 based machines to avoid the build errors like this. ERROR: Nothing RPROVIDES '${@oe.utils.conditional('ARAGO_BRAND',' (but <>/packagegroups/ti-test.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target '${@oe.utils.conditional('ARAGO_BRAND',' is unbuildable, removing... Missing or unbuildable dependency chain was: ["${@oe.utils.conditional('ARAGO_BRAND',"] Please ignore this one as its not the right fix. Signed-off-by: Praneeth Bajjuri --- .../recipes-core/packagegroups/ti-test.bb | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/meta-arago-distro/recipes-core/packagegroups/ti-test.bb b/meta-arago-distro/recipes-core/packagegroups/ti-test.bb index cbc246d5..2730c381 100644 --- a/meta-arago-distro/recipes-core/packagegroups/ti-test.bb +++ b/meta-arago-distro/recipes-core/packagegroups/ti-test.bb @@ -66,14 +66,9 @@ ARAGO_TI_TEST_append_ti43x = " \ ${@oe.utils.conditional('ARAGO_BRAND', 'mainline', '', 'cmem-test', d)} \ " -ARAGO_TI_TEST_append_omap-a15 = " \ -omapconf \ -${@oe.utils.conditional('ARAGO_BRAND', 'mainline', '', " \ -ti-ipc-test \ -${@bb.utils.contains('MACHINE_FEATURES', 'mmip', 'omapdrmtest', '', d)} \ -cmem-test \ -", d)} \ -" +ARAGO_TI_TEST_append_omap-a15 = "omapconf ti-ipc-test cmem-test" + +ARAGO_TI_TEST_append_omap-a15 = "${@bb.utils.contains('MACHINE_FEATURES', 'mmip', 'omapdrmtest', '', d)}" ARAGO_TI_TEST_append_k3 = " \ k3conf \ ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell][PATCH 1/3] Revert "HACK: qtwebkit: define MESA_EGL_NO_X11_HEADERS at ANGLE/khrplatform.h"
On 4/1/2021 11:33 AM, Gowtham Tammana wrote: This reverts commit 1e83ebf61bd22ca8ad04d5538db044d81330df2c. It is no longer needed as it is handled through build dependencies. no signed-off-by ? Will append before merging to dunfell --- ...atform.h-add-define-MESA_EGL_NO_X11_.patch | 30 --- .../recipes-qt/qt5/qtwebkit_%.bbappend| 3 +- 2 files changed, 1 insertion(+), 32 deletions(-) delete mode 100644 meta-arago-distro/recipes-qt/qt5/qtwebkit/0001-HACK-ANGLE-khrplatform.h-add-define-MESA_EGL_NO_X11_.patch diff --git a/meta-arago-distro/recipes-qt/qt5/qtwebkit/0001-HACK-ANGLE-khrplatform.h-add-define-MESA_EGL_NO_X11_.patch b/meta-arago-distro/recipes-qt/qt5/qtwebkit/0001-HACK-ANGLE-khrplatform.h-add-define-MESA_EGL_NO_X11_.patch deleted file mode 100644 index 29521a8e.. --- a/meta-arago-distro/recipes-qt/qt5/qtwebkit/0001-HACK-ANGLE-khrplatform.h-add-define-MESA_EGL_NO_X11_.patch +++ /dev/null @@ -1,30 +0,0 @@ -From 4a21fcedd886772b7e1bd40861835f1b4f33c7ff Mon Sep 17 00:00:00 2001 -From: Eric Ruei -Date: Fri, 30 Aug 2019 17:41:13 -0400 -Subject: [PATCH] HACK: ANGLE/khrplatform.h: add #define - MESA_EGL_NO_X11_HEADERS - -Note: Only the KHR/khrplatform.h at sysroot/usr/include should be used. - This patch is a tentative workaround to make both files compatible - -Upstream-Status: Inappropriate [tentative workaround only] - -Signed-off-by: Eric Ruei - Source/ThirdParty/ANGLE/include/KHR/khrplatform.h | 2 ++ - 1 file changed, 2 insertions(+) - -diff --git a/Source/ThirdParty/ANGLE/include/KHR/khrplatform.h b/Source/ThirdParty/ANGLE/include/KHR/khrplatform.h -index c9e6f17d3..4e3ff69a8 100644 a/Source/ThirdParty/ANGLE/include/KHR/khrplatform.h -+++ b/Source/ThirdParty/ANGLE/include/KHR/khrplatform.h -@@ -279,4 +279,6 @@ typedef enum { - KHRONOS_BOOLEAN_ENUM_FORCE_SIZE = KHRONOS_MAX_ENUM - } khronos_boolean_enum_t; - -+#define MESA_EGL_NO_X11_HEADERS -+ - #endif /* __khrplatform_h_ */ --- -2.17.1 - diff --git a/meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend b/meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend index 1dbe40d1..75213487 100644 --- a/meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend +++ b/meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend @@ -6,10 +6,9 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI += " \ file://GraphicsSurfaceGL_NoX.cpp.patch \ - file://0001-HACK-ANGLE-khrplatform.h-add-define-MESA_EGL_NO_X11_.patch \ " -PR_append = ".arago8" +PR_append = ".arago7" EXTRA_OECMAKE_append = " -DCMAKE_BUILD_TYPE=Release" ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [master][PATCH] layer.conf: Add hardknott to compatible release branches
On 3/23/2021 9:51 AM, Nishanth Menon wrote: This follows commit cfe3f78 ("layer.conf: add hardknott to compatible release branches") from meta-ti. While we are at it, remove old releases before dunfell as we no longer support the build of such configurations. Thanks for the fix. looks good to me. I will make a similar cleanup fix for dunfell branch from meta-ti --- a/meta-arago-distro/conf/layer.conf +++ b/meta-arago-distro/conf/layer.conf -LAYERSERIES_COMPAT_meta-arago-distro = "sumo thud warrior zeus dunfell" +LAYERSERIES_COMPAT_meta-arago-distro = "dunfell" --- a/meta-arago-extras/conf/layer.conf +++ b/meta-arago-extras/conf/layer.conf -LAYERSERIES_COMPAT_meta-arago-extras = "sumo thud warrior zeus dunfell" +LAYERSERIES_COMPAT_meta-arago-extras = "dunfell" Signed-off-by: Nishanth Menon --- WARNING: there is a bunch of work to do to move to gatesgarth / hardknott .. https://pastebin.ubuntu.com/p/kKCqXvnDKf/ but this allows us to get started, I think. meta-arago-distro/conf/layer.conf | 2 +- meta-arago-extras/conf/layer.conf | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-arago-distro/conf/layer.conf b/meta-arago-distro/conf/layer.conf index 2931bf9daf4a..1fa61207fe01 100644 --- a/meta-arago-distro/conf/layer.conf +++ b/meta-arago-distro/conf/layer.conf @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "meta-arago-distro" BBFILE_PATTERN_meta-arago-distro := "^${LAYERDIR}/" BBFILE_PRIORITY_meta-arago-distro = "10" -LAYERSERIES_COMPAT_meta-arago-distro = "sumo thud warrior zeus dunfell" +LAYERSERIES_COMPAT_meta-arago-distro = "dunfell gatesgarth hardknott" LAYERDEPENDS_meta-arago-distro = " \ core \ diff --git a/meta-arago-extras/conf/layer.conf b/meta-arago-extras/conf/layer.conf index 7e3081b20ba8..d64a80f8890f 100644 --- a/meta-arago-extras/conf/layer.conf +++ b/meta-arago-extras/conf/layer.conf @@ -8,7 +8,7 @@ BBFILE_COLLECTIONS += "meta-arago-extras" BBFILE_PATTERN_meta-arago-extras := "^${LAYERDIR}/" BBFILE_PRIORITY_meta-arago-extras = "10" -LAYERSERIES_COMPAT_meta-arago-extras = "sumo thud warrior zeus dunfell" +LAYERSERIES_COMPAT_meta-arago-extras = "dunfell gatesgarth hardknott" # Set a variable to get to the top of the metadata location ARAGOBASE := '${@os.path.normpath("${LAYERDIR}/../")}' ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [oe-layersetup][PATCH 0/2] arago-dunfell/dunfell-next: Move to
On 3/16/2021 1:45 PM, Denys Dmytriyenko wrote: On Tue, Mar 16, 2021 at 12:18:01PM -0500, Nishanth Menon wrote: On 12:08-20210316, Nishanth Menon wrote: I have no idea what ate up my $subject -> I intended to add "Move to dunfell/dunfell-tip from upstream. This brings arago-config and arago-next-config both in sync with latest dunfell and dunfell-next tips appropriately. This series obviously will need to be followed up at an appropriate time with a stable commit sha patch to pin things up. K, I might be missing the motivation here - the pinning may not be required given that dunfell is always a rolling config.. and used only in the cases of exceptions.. So, please ignore my comment. Looks good to me. Praneeth, I see you only merged one of two patches? Yes , only pulled the dunfell-next config .. started the build job to check if builds are ok. Will pull the dunfell patch in couple of hrs. ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell][PATCH v3] packagegroups: tisdk-connectivity: Include TI wlan packages for k3 platforms
On 3/12/2021 8:12 AM, Nagalla, Hari wrote: I believe, you could do the same for 'BT_TI' components. Add it to the CONNECTIVITY_RDEPENDS variable. In the current builds, BT FW is missing.. The above would fix it.. Can you send a seperate patch for BT update in the same way. Thanks Hari -Original Message- From: Devshatwar, Nikhil Sent: Wednesday, March 10, 2021 2:01 PM To: meta-arago@arago-project.org; Bajjuri, Praneeth Cc: Vutla, Lokesh ; Kishon Vijay Abraham ; Nori, Sekhar ; Nagalla, Hari ; Narang, Saurabh ; Devshatwar, Nikhil Subject: [meta-arago][dunfell][PATCH v3] packagegroups: tisdk-connectivity: Include TI wlan packages for k3 platforms Currently, the K3 platforms do not include the TI wlan related packages. Add in the tisdk-connectivity packagegroup. While at it, combine the packages added in all overrides into CONNECTIVITY_RDEPENDS variable and remove from overrides. Signed-off-by: Nikhil Devshatwar Suggested-by: Hari Nagalla Reviewed-by: Lokesh Vutla --- Notes: changes from v2: * Combine the common package list into CONNECTIVITY_RDEPENDS changes from v1: * Drop the new recipe and simply include the existing packages for wilink This way, all the platforms are using the same recipes and we don't have to maintain any new recipe just for the am64xx-sk The firmare will get picked from the repo git://git.ti.com/wilink8-wlan/wl18xx_fw.git .../packagegroup-arago-tisdk-connectivity.bb| 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb index 11109432..8a8189fe 100644 --- a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb +++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-ti +++ sdk-connectivity.bb @@ -61,36 +61,25 @@ CONNECTIVITY_RDEPENDS = " \ iproute2-devlink \ net-snmp \ net-snmp-server-snmpd \ -" - -CONNECTIVITY_RDEPENDS_append_ti33x = "\ ${WLAN_COMMON} \ ${WLAN_TI} \ ${BT_COMMON} \ +" + +CONNECTIVITY_RDEPENDS_append_ti33x = "\ ${BT_TI} \ ${DEMO_APPS} \ " CONNECTIVITY_RDEPENDS_append_ti43x = "\ -${WLAN_COMMON} \ -${WLAN_TI} \ -${BT_COMMON} \ ${BT_TI} \ ${DEMO_APPS} \ " CONNECTIVITY_RDEPENDS_append_dra7xx = "\ -${WLAN_COMMON} \ -${WLAN_TI} \ -${BT_COMMON} \ ${BT_TI} \ " -CONNECTIVITY_RDEPENDS_append_k3 = "\ -${WLAN_COMMON} \ -${BT_COMMON} \ -" - RDEPENDS_${PN} = "\ ${CONNECTIVITY_RDEPENDS} \ " -- 2.17.1 ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [meta-ti][dunfell/master][PATCH v2] packagegroups: tisdk-connectivity: Include TI wlan packages for k3 platforms
On 3/10/2021 12:37 PM, Nikhil Devshatwar wrote: On 10/03/21 11:00 pm, Bajjuri, Praneeth wrote: On 3/3/2021 12:21 PM, Nikhil Devshatwar wrote: Currently, the K3 platforms do not include the TI wlan related packages. Add in the tisdk-connectivity packagegroup. Signed-off-by: Nikhil Devshatwar Suggested-by: Hari Nagalla Reviewed-by: Lokesh Vutla --- Notes: changes from v1: s/meta-ti/meta-arago. Please point to right project next time. Sorry about that. Reused last command and missed this. * Drop the new recipe and simply include the existing packages for wilink This way, all the platforms are using the same recipes and we don't have to maintain any new recipe just for the am64xx-sk The firmare will get picked from the repo git://git.ti.com/wilink8-wlan/wl18xx_fw.git .../packagegroups/packagegroup-arago-tisdk-connectivity.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb index 11109432..ab632924 100644 --- a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb +++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb @@ -89,6 +89,7 @@ CONNECTIVITY_RDEPENDS_append_dra7xx = "\ CONNECTIVITY_RDEPENDS_append_k3 = "\ ${WLAN_COMMON} \ ${BT_COMMON} \ + ${WLAN_TI} \ " Looks like WLAN_TI and WLAN_COMMON is valid for all platforms defined in this packagegroup. why not move both of them under CONNECTIVITY_RDEPENDS without a specific platform append?. Looking at the history, the following commit split the package list into a separate group explicitly: d24fa63f33 ("packagegroup-*-connectivity: restructure WLAN & BT lists and add WLAN to K3") Where the WLAN_COMMON was added but WLAN_TI was not added. Thats correct, But after this patch we have WLAN_TI and WLAN_COMMON for all platforms now (including K3). Why not do something like this. @@ -61,36 +61,25 @@ CONNECTIVITY_RDEPENDS = " \ iproute2-devlink \ net-snmp \ net-snmp-server-snmpd \ -" - -CONNECTIVITY_RDEPENDS_append_ti33x = "\ ${WLAN_COMMON} \ ${WLAN_TI} \ ${BT_COMMON} \ +" + +CONNECTIVITY_RDEPENDS_append_ti33x = "\ ${BT_TI} \ ${DEMO_APPS} \ " CONNECTIVITY_RDEPENDS_append_ti43x = "\ -${WLAN_COMMON} \ -${WLAN_TI} \ -${BT_COMMON} \ ${BT_TI} \ ${DEMO_APPS} \ " CONNECTIVITY_RDEPENDS_append_dra7xx = "\ -${WLAN_COMMON} \ -${WLAN_TI} \ -${BT_COMMON} \ ${BT_TI} \ " -CONNECTIVITY_RDEPENDS_append_k3 = "\ -${WLAN_COMMON} \ -${BT_COMMON} \ -" - Regards, Nikhil D RDEPENDS_${PN} = "\ ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [meta-ti][dunfell/master][PATCH v2] packagegroups: tisdk-connectivity: Include TI wlan packages for k3 platforms
On 3/3/2021 12:21 PM, Nikhil Devshatwar wrote: Currently, the K3 platforms do not include the TI wlan related packages. Add in the tisdk-connectivity packagegroup. Signed-off-by: Nikhil Devshatwar Suggested-by: Hari Nagalla Reviewed-by: Lokesh Vutla --- Notes: changes from v1: s/meta-ti/meta-arago. Please point to right project next time. * Drop the new recipe and simply include the existing packages for wilink This way, all the platforms are using the same recipes and we don't have to maintain any new recipe just for the am64xx-sk The firmare will get picked from the repo git://git.ti.com/wilink8-wlan/wl18xx_fw.git .../packagegroups/packagegroup-arago-tisdk-connectivity.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb index 11109432..ab632924 100644 --- a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb +++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-connectivity.bb @@ -89,6 +89,7 @@ CONNECTIVITY_RDEPENDS_append_dra7xx = "\ CONNECTIVITY_RDEPENDS_append_k3 = "\ ${WLAN_COMMON} \ ${BT_COMMON} \ +${WLAN_TI} \ " Looks like WLAN_TI and WLAN_COMMON is valid for all platforms defined in this packagegroup. why not move both of them under CONNECTIVITY_RDEPENDS without a specific platform append?. RDEPENDS_${PN} = "\ ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [[master/dunfell PATCH] ltp-ddt: Update to latest
On 2/11/2021 12:06 PM, Bajjuri, Praneeth wrote: On 2/11/2021 7:00 AM, Aparna Balasubramanian wrote: Signed-off-by: Aparna Balasubramanian Can you add some description? Looks like this patch brings am64xx-sk support. Aparna, took care of updating commit message and pushed to dunfell-next. Please add a valid description whenever a major change is coming. --- .../recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb b/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb index f0824a94..d8eb5918 100644 --- a/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb +++ b/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb @@ -11,10 +11,10 @@ PROVIDES += "ltp" DEPENDS += "alsa-lib" PE = "1" -PR = "r10" +PR = "r11" PV_append = "+git${SRCPV}" -SRCREV = "b0459d9aa364d07699ae6f273280358aae509d56" +SRCREV = "202913bf46e218e7c4a6d99f9833f4033cc3c17d" BRANCH ?= "master" SRC_URI_remove = "git://github.com/linux-test-project/ltp.git" ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [[master/dunfell PATCH] ltp-ddt: Update to latest
On 2/11/2021 7:00 AM, Aparna Balasubramanian wrote: Signed-off-by: Aparna Balasubramanian Can you add some description? Looks like this patch brings am64xx-sk support. --- .../recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb b/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb index f0824a94..d8eb5918 100644 --- a/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb +++ b/meta-arago-extras/recipes-devtools/ltp-ddt/ltp-ddt_20200120.bb @@ -11,10 +11,10 @@ PROVIDES += "ltp" DEPENDS += "alsa-lib" PE = "1" -PR = "r10" +PR = "r11" PV_append = "+git${SRCPV}" -SRCREV = "b0459d9aa364d07699ae6f273280358aae509d56" +SRCREV = "202913bf46e218e7c4a6d99f9833f4033cc3c17d" BRANCH ?= "master" SRC_URI_remove = "git://github.com/linux-test-project/ltp.git" ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell/master][PATCH] optee-os: as meta-ti now has upstream 3.11, drop local fork
On 12/17/2020 3:42 PM, Denys Dmytriyenko wrote: There's no need for ti-optee-os fork any more, as it's exactly the same as upstream Thanks Denys for the fix. This along with the meta-ti patch helped in building 3.11 on sdk builds. One question though, While there is no difference today between TI and upstream optee, Any reason why we cannot use the forked project? Similar to how we are doing with ATF today ? Signed-off-by: Denys Dmytriyenko --- meta-arago-distro/recipes-security/optee/optee-os_git.bbappend | 7 --- 1 file changed, 7 deletions(-) delete mode 100644 meta-arago-distro/recipes-security/optee/optee-os_git.bbappend diff --git a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend deleted file mode 100644 index 677c6dd..000 --- a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +++ /dev/null @@ -1,7 +0,0 @@ -PR_append = ".arago0" - -SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \ - file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \ -" -BRANCH = "ti-optee-os" -SRCREV = "199fca17b575d4c748c9c435e908a6ec9618c75a" ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell/master PATCH] optee-os: update SRCREV to pick latest
On 12/7/2020 1:40 PM, Dan Murphy wrote: Praneeth On 12/4/20 3:47 PM, prane...@ti.com wrote: From: Praneeth Bajjuri updating SRCREV to pick the latest commit on repo: ti-optee-os.git branch: ti-optee-os Signed-off-by: Praneeth Bajjuri --- meta-arago-distro/recipes-security/optee/optee-os_git.bbappend | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend index 677c6dd0..8a52833e 100644 --- a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +++ b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend @@ -4,4 +4,4 @@ SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \ file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \ " BRANCH = "ti-optee-os" -SRCREV = "199fca17b575d4c748c9c435e908a6ec9618c75a" +SRCREV = "f414104d552c8ab96ccc3c4182c395c20e3a0a34" Are you updating this to a new version or reverting to an older version? If so you probably want to add a PV = "3.xx" here. meta-arm has the PV set to 3.8 unless you are moving to 3.8. There is no change in OPTEE version between those commit sha. Since the git.ti.com repo does not contain the optee upstream tags it is difficult to know what version this is. (Yes I know you just picked up the maintenance). Dan , Please go ahead and pull this update ( we will continue to be on 3.8) Dan ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
Re: [meta-arago] [dunfell/master PATCH] optee-os: update SRCREV to pick latest
On 12/10/2020 4:33 PM, Dan Murphy wrote: Praneeth On 12/10/20 4:32 PM, prane...@ti.com wrote: From: Praneeth Bajjuri updating SRCREV to pick the latest commit on repo: ti-optee-os.git branch: ti-optee-os Signed-off-by: Praneeth Bajjuri --- .../recipes-security/optee/optee-os_git.bbappend | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend index 677c6dd0..28b9b6c5 100644 --- a/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend +++ b/meta-arago-distro/recipes-security/optee/optee-os_git.bbappend @@ -1,7 +1,9 @@ PR_append = ".arago0" SRC_URI = "git://git.ti.com/optee/ti-optee-os.git;branch=${BRANCH} \ - file://0001-allow-setting-sysroot-for-libgcc-lookup.patch \ + file://0006-allow-setting-sysroot-for-libgcc-lookup.patch \ Why is this 0006? What are the other 5 patches? As per this , https://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/commit/meta-arm/recipes-security/optee/optee-os/0006-allow-setting-sysroot-for-libgcc-lookup.patch?id=715c9f8f98534655c3a368c50ceaf7a1f12da084 that patch has been updated for 3.10+ recipe update. Dan ___ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago