[PATCH yocto-autobuilder-helper 1/4] config.json: add "collect-data" template
sakib.sajal@...
collect-data template can run arbitrary commands/scripts
on a regular basis and logs the output in a file. See oe-core for more details: edb7098e9e buildstats.bbclass: add functionality to collect build system stats Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com> Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> --- config.json | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/config.json b/config.json index 5bfa240..c43d231 100644 --- a/config.json +++ b/config.json @@ -87,6 +87,13 @@ "SANITYTARGETS" : "core-image-full-cmdline:do_testimage core-image-sato:do_testimage core-image-sato-sdk:do_testimage" } }, + "collect-data" : { + "extravars" : [ + "BB_HEARTBEAT_EVENT = '10'", + "BB_LOG_HOST_STAT_ON_INTERVAL = '1'", + "BB_LOG_HOST_STAT_CMDS = 'oe-time-dd-test.sh 100'" + ] + }, "ptest-qemu" : { "BUILDINFO" : true, "BBTARGETS" : "core-image-sato-ptest", -- 2.25.1
|
|
Re: ref-manual: reverse the order of migration guides?
Michael Opdenacker
Oops, sent to the wrong list (meant to use the "docs" list). You can
remove if this list is moderated. Apologies -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
ref-manual: reverse the order of migration guides?
Michael Opdenacker
Greetings,
Wouldn't it make sense to reverse the order of migration guides in the reference manual (https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#migration)? I guess it would be easier to start mentioning the migration path from the most recent release, as version 1.3 looks ancient. Would it make sense? If so, it's easy to propose a patch... Thanks in advance, Michael. -- Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
Re: [meta-cgl][PATCH] pacemaker: upgrade 2.0.3 -> 2.0.5
On 2021-04-12 11:00 p.m., Jeremy Puhlman wrote:
I haven't been doing much with it lately and this got lost in my pile. Its merged to master.Thanks Jeremy. ../Randy On Mon, Apr 12, 2021 at 7:29 PM Randy MacLeod <randy.macleod@windriver.com <mailto:randy.macleod@windriver.com>> wrote: -- # Randy MacLeod # Wind River Linux
|
|
Re: need Sysvinit as system manager in Rocko Version
#rocko
rohit jadhav
Hi Khem Raj, Thanks you for your valuable feedback. I have tried with your suggestions. but observed with following error: ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-qt5-webengine.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-qt5-demos.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-imx-erpc.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-fsl-tools-gpu-external.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES ERROR: Failed to parse recipe: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-imx-erpc.bb ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-fsl-optee-imx.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-fsl-pulseaudio.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES ERROR: /home/tel/imx_yocto_bsp/sources/meta-fsl-bsp-release/imx/meta-sdk/recipes-fsl/packagegroup/packagegroup-fsl-tools-audio.bb: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (systemd) matches the entries enabled in DISTRO_FEATURES Thanks and regards Rohit J
On Tue, Apr 13, 2021 at 8:58 PM Khem Raj <raj.khem@...> wrote:
|
|
[meta-rockchip][PATCH 5/6] WIP nanopi-m4: declare OP-TEE presence in devicetree
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
FIXME: - this is not specific to the board, and would indeed apply to any SoC supported by OP-TEE. - should rather be selected by "optee" in DISTRO_FEATURES, maybe using a dts overlay --- .../0001-nanopi-declare-optee-presence.patch | 30 +++++++++++++++++++ recipes-kernel/linux/linux-yocto%.bbappend | 1 + 2 files changed, 31 insertions(+) create mode 100644 recipes-kernel/linux/files/0001-nanopi-declare-optee-= presence.patch diff --git a/recipes-kernel/linux/files/0001-nanopi-declare-optee-presenc= e.patch b/recipes-kernel/linux/files/0001-nanopi-declare-optee-presence.p= atch new file mode 100644 index 0000000..aede781 --- /dev/null +++ b/recipes-kernel/linux/files/0001-nanopi-declare-optee-presence.patch @@ -0,0 +1,30 @@ +From 30cb714e717990276a5fabc50dc616c83b223ee7 Mon Sep 17 00:00:00 2001 +From: Yann Dirson <yann@blade-group.com> +Date: Mon, 12 Apr 2021 15:50:26 +0200 +Subject: [PATCH] nanopi: declare optee presence + +--- + arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts | 7 +++++++ + 1 file changed, 7 insertions(+) + +diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts b/arch/ar= m64/boot/dts/rockchip/rk3399-nanopi-m4.dts +index 60358ab8c7df..ef11639b03f6 100644 +--- a/arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts ++++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4.dts +@@ -16,6 +16,13 @@ / { + model =3D "FriendlyElec NanoPi M4"; + compatible =3D "friendlyarm,nanopi-m4", "rockchip,rk3399"; +=20 ++ firmware { ++ optee { ++ compatible =3D "linaro,optee-tz"; ++ method =3D "smc"; ++ }; ++ }; ++ + vdd_5v: vdd-5v { + compatible =3D "regulator-fixed"; + regulator-name =3D "vdd_5v"; +--=20 +2.30.2 + diff --git a/recipes-kernel/linux/linux-yocto%.bbappend b/recipes-kernel/= linux/linux-yocto%.bbappend index 9658681..97b3238 100644 --- a/recipes-kernel/linux/linux-yocto%.bbappend +++ b/recipes-kernel/linux/linux-yocto%.bbappend @@ -2,6 +2,7 @@ FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:" =20 SRC_URI_append =3D "\ file://bsp;type=3Dkmeta;subdir=3Dkernel-meta \ + file://0001-nanopi-declare-optee-presence.patch \ " =20 COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066" --=20 2.30.2
|
|
[meta-rockchip][PATCH 6/6] WIP kernel config feature for OP-TEE activation
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
FIXME: - provide an .scc with proper information - maybe bundle with dts overlay - select a more suitable path in config namespace --- recipes-kernel/linux/files/bsp/tee.cfg | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 recipes-kernel/linux/files/bsp/tee.cfg diff --git a/recipes-kernel/linux/files/bsp/tee.cfg b/recipes-kernel/linu= x/files/bsp/tee.cfg new file mode 100644 index 0000000..82213a5 --- /dev/null +++ b/recipes-kernel/linux/files/bsp/tee.cfg @@ -0,0 +1,2 @@ +CONFIG_TEE=3Dm +CONFIG_OPTEE=3Dm --=20 2.30.2
|
|
[meta-rockchip][PATCH 4/6] WIP optee-os: rk3399 support
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
This is the current state of working patches being discussed in https://github.com/OP-TEE/optee_os/issues/4542 --- conf/machine/include/rk3399.inc | 2 + ...399-enable-serial-console-by-default.patch | 46 +++++++++++++++++++ .../optee/files/rk3399-boot-fix.patch | 13 ++++++ recipes-security/optee/optee%.bbappend | 2 + recipes-security/optee/optee-os_%.bbappend | 9 ++++ 5 files changed, 72 insertions(+) create mode 100644 recipes-security/optee/files/0001-rk3399-enable-seria= l-console-by-default.patch create mode 100644 recipes-security/optee/files/rk3399-boot-fix.patch create mode 100644 recipes-security/optee/optee-os_%.bbappend diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk339= 9.inc index f6b7826..9ac434e 100644 --- a/conf/machine/include/rk3399.inc +++ b/conf/machine/include/rk3399.inc @@ -13,6 +13,8 @@ KBUILD_DEFCONFIG ?=3D "defconfig" KERNEL_CLASSES =3D "kernel-fitimage" KERNEL_IMAGETYPE =3D "fitImage" =20 +OPTEEMACHINE =3D "rockchip-rk3399" + TFA_PLATFORM =3D "rk3399" TFA_BUILD_TARGET =3D "bl31" =20 diff --git a/recipes-security/optee/files/0001-rk3399-enable-serial-conso= le-by-default.patch b/recipes-security/optee/files/0001-rk3399-enable-ser= ial-console-by-default.patch new file mode 100644 index 0000000..31daef7 --- /dev/null +++ b/recipes-security/optee/files/0001-rk3399-enable-serial-console-by-d= efault.patch @@ -0,0 +1,46 @@ +From 0e2cbe08532a1344aab62f21b032ce6171e50f49 Mon Sep 17 00:00:00 2001 +From: Yann Dirson <yann@blade-group.com> +Date: Mon, 12 Apr 2021 10:49:18 +0200 +Subject: [PATCH] rk3399: enable serial console by default +Upstream-Status: Submitted [https://github.com/OP-TEE/optee_os/pull/4551= ] + +Signed-off-by: Yann Dirson <yann@blade-group.com> +--- + core/arch/arm/plat-rockchip/conf.mk | 6 ++++++ + 1 file changed, 6 insertions(+) + +Index: git/core/arch/arm/plat-rockchip/conf.mk +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +--- git.orig/core/arch/arm/plat-rockchip/conf.mk ++++ git/core/arch/arm/plat-rockchip/conf.mk +@@ -26,8 +26,6 @@ CFG_EARLY_CONSOLE_BAUDRATE ?=3D 1500000 + CFG_EARLY_CONSOLE_CLK_IN_HZ ?=3D 24000000 + endif +=20 +-CFG_EARLY_CONSOLE ?=3D n +- + ifeq ($(PLATFORM_FLAVOR),rk3399) + include core/arch/arm/cpu/cortex-armv8-0.mk + $(call force,CFG_TEE_CORE_NB_CORE,6) +@@ -37,6 +35,12 @@ CFG_TZDRAM_START ?=3D 0x30000000 + CFG_TZDRAM_SIZE ?=3D 0x02000000 + CFG_SHMEM_START ?=3D 0x32000000 + CFG_SHMEM_SIZE ?=3D 0x00400000 ++ ++CFG_EARLY_CONSOLE ?=3D y ++CFG_EARLY_CONSOLE_BASE ?=3D UART2_BASE ++CFG_EARLY_CONSOLE_SIZE ?=3D UART2_SIZE ++CFG_EARLY_CONSOLE_BAUDRATE ?=3D 1500000 ++CFG_EARLY_CONSOLE_CLK_IN_HZ ?=3D 24000000 + endif +=20 + ifeq ($(PLATFORM_FLAVOR),px30) +@@ -47,6 +51,8 @@ CFG_TZDRAM_START ?=3D 0x30000000 + CFG_TZDRAM_SIZE ?=3D 0x02000000 + CFG_SHMEM_START ?=3D 0x32000000 + CFG_SHMEM_SIZE ?=3D 0x00400000 ++ ++CFG_EARLY_CONSOLE ?=3D n + endif +=20 + ifeq ($(platform-flavor-armv8),1) diff --git a/recipes-security/optee/files/rk3399-boot-fix.patch b/recipes= -security/optee/files/rk3399-boot-fix.patch new file mode 100644 index 0000000..d346157 --- /dev/null +++ b/recipes-security/optee/files/rk3399-boot-fix.patch @@ -0,0 +1,13 @@ +Index: git/core/arch/arm/kernel/entry_a64.S +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D +--- git.orig/core/arch/arm/kernel/entry_a64.S ++++ git/core/arch/arm/kernel/entry_a64.S +@@ -219,7 +219,7 @@ clear_nex_bss: + adr_l x0, __text_start + ldr x1, cached_mem_end + sub x1, x1, x0 +- bl dcache_cleaninv_range ++/* bl dcache_cleaninv_range*/ +=20 +=20 + /* diff --git a/recipes-security/optee/optee%.bbappend b/recipes-security/op= tee/optee%.bbappend index 2a8722a..ec11863 100644 --- a/recipes-security/optee/optee%.bbappend +++ b/recipes-security/optee/optee%.bbappend @@ -1,2 +1,4 @@ +COMPATIBLE_MACHINE_rk3399 ?=3D "rk3399" + inherit features_check REQUIRED_DISTRO_FEATURES =3D "optee" diff --git a/recipes-security/optee/optee-os_%.bbappend b/recipes-securit= y/optee/optee-os_%.bbappend new file mode 100644 index 0000000..eceb694 --- /dev/null +++ b/recipes-security/optee/optee-os_%.bbappend @@ -0,0 +1,9 @@ +EXTRA_OEMAKE_append_rk3399 =3D " \ + CFG_CORE_ASLR=3Dn \ +" + +FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:" +SRC_URI +=3D "\ + file://rk3399-boot-fix.patch \ + file://0001-rk3399-enable-serial-console-by-default.patch \ +" --=20 2.30.2
|
|
[meta-rockchip][PATCH 1/6] optee: condition for "optee" DISTRO_FEATURE
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
This effectively sets up a single switch to activate OP-TEE support. Disabling optee-* recipes when the feature is not set is not the primary goal, though it can occasionally be handy to catch dependencies pulling them without using the new DISTRO_FEATURE, which provides a safeguard to ensure downstream recipes in need of upgrade will fail early. The main value for this flag is for dependent recipes to know when to activate the OP-TEE support, rather than having to control each of them separately: - u-boot - trusted-firmware-a - kernel Signed-off-by: Yann Dirson <yann@blade-group.com> --- recipes-security/optee/optee%.bbappend | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 recipes-security/optee/optee%.bbappend diff --git a/recipes-security/optee/optee%.bbappend b/recipes-security/op= tee/optee%.bbappend new file mode 100644 index 0000000..2a8722a --- /dev/null +++ b/recipes-security/optee/optee%.bbappend @@ -0,0 +1,2 @@ +inherit features_check +REQUIRED_DISTRO_FEATURES =3D "optee" --=20 2.30.2
|
|
[meta-rockchip][PATCH 0/6] WIP/RFC OP-TEE support for ARM and rk3399
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
This tries to provide a generic framework for easier OP-TEE support in BSP layers. It would probably make sense to have the generic parts in meta-arm when they are finalized. Today the kernel/dts handling is still not properly done, and patches to fix rk3399 support in OP-TEE have not yet been merged upstream, and I'm mostly posting this to gather comments on the whole idea. Yann Dirson (6): optee: condition for "optee" DISTRO_FEATURE truster-firmware-a: include optee support when requested by DISTRO_FEATURE u-boot: include optee-os as BL32 when requested by DISTRO_FEATURE WIP optee-os: rk3399 support WIP nanopi-m4: declare OP-TEE presence in devicetree WIP kernel config feature for OP-TEE activation conf/machine/include/rk3399.inc | 2 + .../trusted-firmware-a_%.bbappend | 19 ++++++++ recipes-bsp/u-boot/u-boot%.bbappend | 14 ++++++ .../0001-nanopi-declare-optee-presence.patch | 30 ++++++++++++ recipes-kernel/linux/files/bsp/tee.cfg | 2 + recipes-kernel/linux/linux-yocto%.bbappend | 1 + ...399-enable-serial-console-by-default.patch | 46 +++++++++++++++++++ .../optee/files/rk3399-boot-fix.patch | 13 ++++++ recipes-security/optee/optee%.bbappend | 4 ++ recipes-security/optee/optee-os_%.bbappend | 9 ++++ 10 files changed, 140 insertions(+) create mode 100644 recipes-kernel/linux/files/0001-nanopi-declare-optee-= presence.patch create mode 100644 recipes-kernel/linux/files/bsp/tee.cfg create mode 100644 recipes-security/optee/files/0001-rk3399-enable-seria= l-console-by-default.patch create mode 100644 recipes-security/optee/files/rk3399-boot-fix.patch create mode 100644 recipes-security/optee/optee%.bbappend create mode 100644 recipes-security/optee/optee-os_%.bbappend --=20 2.30.2
|
|
[meta-rockchip][PATCH 2/6] truster-firmware-a: include optee support when requested by DISTRO_FEATURE
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
This instructs TF-A to: - load OP-TEE OS as BL32, but still relies on the actual image to be provided through other means, eg. in u-boot.itb - run opteed as Secure Payload Dispatcher This is configured automatically when DISTRO_FEATURE includes "optee". Signed-off-by: Yann Dirson <yann@blade-group.com> --- .../trusted-firmware-a_%.bbappend | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend= b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend index 1942c17..5b04311 100644 --- a/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend +++ b/recipes-bsp/trusted-firmware-a/trusted-firmware-a_%.bbappend @@ -9,3 +9,22 @@ FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:" SRC_URI +=3D "\ file://serial-console-baudrate.patch \ " + +# OP-TEE, dependent on "optee" DISTRO_FEATURES + +OPTEE_DEPENDS ?=3D "optee-os:do_deploy" +OPTEE_OEMAKE ?=3D " \ + BL32=3D${STAGING_DIR_TARGET}${nonarch_base_libdir}/firmware/tee-head= er_v2.bin \ + BL32_EXTRA1=3D${STAGING_DIR_TARGET}${nonarch_base_libdir}/firmware/t= ee-pager_v2.bin \ + BL32_EXTRA2=3D${STAGING_DIR_TARGET}${nonarch_base_libdir}/firmware/t= ee-pageable_v2.bin \ + " + +do_compile[depends] .=3D " \ + ${@bb.utils.contains('DISTRO_FEATURES', 'optee', ' ${OPTEE_DEPENDS}', '= ', d)} \ +" + +EXTRA_OEMAKE_append =3D " \ + ${@bb.utils.contains('DISTRO_FEATURES', 'optee', ' ${OPTEE_OEMAKE}', ''= , d)} \ +" + +TFA_SPD ?=3D "${@bb.utils.contains('DISTRO_FEATURES', 'optee', 'opteed',= '', d)}" --=20 2.30.2
|
|
[meta-rockchip][PATCH 3/6] u-boot: include optee-os as BL32 when requested by DISTRO_FEATURE
Yann Dirson
From: Yann Dirson <yann@blade-group.com>
This causes OP-TEE to get included into the u-boot.itb fitImage so u-boot can load it for the trusted-firmware-a BL31 to run it. This is configured automatically when DISTRO_FEATURE includes "optee". Signed-off-by: Yann Dirson <yann@blade-group.com> --- recipes-bsp/u-boot/u-boot%.bbappend | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/recipes-bsp/u-boot/u-boot%.bbappend b/recipes-bsp/u-boot/u-b= oot%.bbappend index 95c019d..c8e150b 100644 --- a/recipes-bsp/u-boot/u-boot%.bbappend +++ b/recipes-bsp/u-boot/u-boot%.bbappend @@ -5,6 +5,8 @@ do_compile_append_rock2-square () { fi } =20 +# TF-A, when supported + ATF_DEPENDS ??=3D "" =20 EXTRA_OEMAKE_append_rk3399 =3D " BL31=3D${DEPLOY_DIR_IMAGE}/bl31-rk3399.= elf" @@ -14,3 +16,15 @@ ATF_DEPENDS_rk3328 =3D " virtual/trusted-firmware-a:do= _deploy" =20 do_compile[depends] .=3D "${ATF_DEPENDS}" =20 +# OP-TEE, dependent on "optee" DISTRO_FEATURES + +OPTEE_DEPENDS ?=3D "optee-os:do_deploy" +OPTEE_OEMAKE ?=3D " TEE=3D${DEPLOY_DIR_IMAGE}/optee/tee.elf" + +do_compile[depends] .=3D " \ + ${@bb.utils.contains('DISTRO_FEATURES', 'optee', ' ${OPTEE_DEPENDS}', '= ', d)} \ +" + +EXTRA_OEMAKE_append =3D " \ + ${@bb.utils.contains('DISTRO_FEATURES', 'optee', ' ${OPTEE_OEMAKE}', ''= , d)} \ +" --=20 2.30.2
|
|
Re: QA notification for completed autobuilder build (yocto-3.3.rc2)
LGTM
toggle quoted messageShow quoted text
On 4/13/21 2:48 AM, Sangeeta Jain wrote:
Hello All,
|
|
Re: need Sysvinit as system manager in Rocko Version
#rocko
On 4/13/21 3:02 AM, rohitbjadhav1@gmail.com wrote:
I have created rootfs with Rocko yocto version.remove systemd from DISTRO_FEATURES as well. DISTRO_FEATURES_remove = "sytemd" VIRTUAL-RUNTIME_init_manager = "sysvinit"
|
|
Yocto Project Status WW15`21
Stephen Jolley
Current Dev Position: YP 3.3 M4 (Feature Freeze) Next Deadline: 5th April 2021 YP 3.3 M4 build
Next Team Meetings:
Key Status/Updates:
We are working to identify the load pattern on the infrastructure that seems to trigger these.
Ways to contribute:
YP 3.3 Milestone Dates:
YP 3.4 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
Re: [yocto-autobuilder2] [PATCH] config: Add meta-aws to base configuration
Richard Purdie
On Tue, 2021-04-13 at 14:59 +0100, Richard Purdie via lists.yoctoproject.org wrote:
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>Not sure what happened with the file deletion but I'll fix that. Cheers, Richard
|
|
[yocto-autobuilder2] [PATCH] config: Add meta-aws to base configuration
Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
--- bsp-addition-example.patch | 54 -------------------------------------- config.py | 3 +++ 2 files changed, 3 insertions(+), 54 deletions(-) delete mode 100644 bsp-addition-example.patch diff --git a/bsp-addition-example.patch b/bsp-addition-example.patch deleted file mode 100644 index 7f92789d..00000000 --- a/bsp-addition-example.patch +++ /dev/null @@ -1,54 +0,0 @@ -From d5fb6c086c18722532333c8af1e19b42b9ffb138 Mon Sep 17 00:00:00 2001 -From: Aaron Chan <aaron.chun.yew.chan@intel.com> -Date: Tue, 28 Aug 2018 10:49:13 +0800 -Subject: [PATCH] config.py: Add new job category with suffix bsp - -Add new support on Open Source Automated Hardware Tests on BSP test -cases. New job category is define with builder name standard as -"nightly-<arch>-bsp" where Yocto Project supports architecutures on -hardware platforms of x86, x86-64, arm, arm64, mips, mips64, pcc. - -Add initial support on x86-64 BSP hardware tests and included meta -layers needed to run QA test cases on these platforms. -Community to adopt and add support to autobuilder job config to -support future BSP testing and validation on their architecture. - -Signed-off-by: Aaron Chan <aaron.chun.yew.chan@intel.com> ---- - config.py | 9 +++++++-- - 1 file changed, 7 insertions(+), 2 deletions(-) - -diff --git a/config.py b/config.py -index 2568768..10f740d 100644 ---- a/config.py -+++ b/config.py -@@ -11,6 +11,7 @@ - "nightly-oecore": ["oecore", "bitbake"], - "nightly-checkuri": ["poky", "meta-qt4", "meta-qt3"], - "nightly-check-layer": ["poky", "meta-mingw", "meta-gplv2"], -+ "nightly-x86-64-bsp": ["poky", "meta-intel", "meta-openembedded", "meta-security", "meta-ros", "meta-browser"], - "default": ["poky"] - } - -@@ -32,7 +33,11 @@ - "meta-qt4": ["git://git.yoctoproject.org/meta-qt4", "master"], - "meta-qt3": ["git://git.yoctoproject.org/meta-qt3", "master"], - "meta-mingw": ["git://git.yoctoproject.org/meta-mingw", "master"], -- "meta-gplv2": ["git://git.yoctoproject.org/meta-gplv2", "master"] -+ "meta-gplv2": ["git://git.yoctoproject.org/meta-gplv2", "master"], -+ "meta-security": ["git://git.yoctoproject.org/meta-security", "master"], -+ "meta-openembedded": ["git://git.openembedded.org/meta-openembedded", "master"], -+ "meta-ros": ["git://github.com/bmwcarit/meta-ros", "master"], -+ "meta-browser": ["git://github.com/OSSystems/meta-browser", "master"] - } - - trigger_builders_wait = [ -@@ -40,7 +45,7 @@ - "nightly-mips", "nightly-mips-lsb", "nightly-mips64", - "nightly-multilib", "nightly-x32", - "nightly-ppc", "nightly-ppc-lsb", -- "nightly-x86-64", "nightly-x86-64-lsb", -+ "nightly-x86-64", "nightly-x86-64-lsb", "nightly-x86-64-bsp", - "nightly-x86", "nightly-x86-lsb", - "nightly-packagemanagers", - "nightly-rpm-non-rpm", "nightly-deb-non-deb", diff --git a/config.py b/config.py index 903cb4b8..54ec9ce8 100644 --- a/config.py +++ b/config.py @@ -19,6 +19,7 @@ buildertorepos = { "meta-intel": ["poky", "meta-intel"], "meta-arm": ["poky", "meta-arm", "meta-kernel"], "meta-agl-core": ["poky", "meta-agl"], + "meta-aws": ["poky", "meta-aws", "meta-openembedded"], "qemuarm-oecore": ["oecore", "bitbake"], "checkuri": ["poky"], "check-layer": ["poky", "meta-mingw", "meta-gplv2"], @@ -40,6 +41,7 @@ repos = { "meta-intel": ["git://git.yoctoproject.org/meta-intel", "master"], "meta-arm": ["git://git.yoctoproject.org/meta-arm", "master"], "meta-agl": ["https://git.automotivelinux.org/AGL/meta-agl", "next"], + "meta-aws": ["https://github.com/aws/meta-aws.git", "master"], "oecore": ["git://git.openembedded.org/openembedded-core", "master"], "bitbake": ["git://git.openembedded.org/bitbake", "master"], @@ -107,6 +109,7 @@ builders_others = [ "bringup", "qemuarm-armhost", "meta-agl-core", + "meta-aws", "auh" ] -- 2.30.2
|
|
[yocto-autobuilder2] [PATCH] config/schedulers: Add hardknott config for new release
Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
--- config.py | 1 + schedulers.py | 14 ++++++++++++-- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/config.py b/config.py index 299f2aa5..903cb4b8 100644 --- a/config.py +++ b/config.py @@ -142,6 +142,7 @@ all_workers = workers + workers_bringup + workers_buildperf + workers_arm # Worker filtering for older releases workers_prev_releases = { + "hardknott" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora31", "fedora32", "fedora33", "opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu2004", "perf-"), "gatesgarth" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", "opensuse152", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"), "dunfell" : ("centos7", "centos8", "debian8", "debian9", "debian10", "fedora29", "fedora30", "fedora31", "fedora32", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "ubuntu2004", "perf-"), "zeus" : ("centos7", "debian8", "debian9", "debian10", "fedora28", "fedora29", "fedora30", "opensuse150", "opensuse151", "ubuntu1604", "ubuntu1804", "ubuntu1904", "perf-"), diff --git a/schedulers.py b/schedulers.py index 84792909..b8a73f10 100644 --- a/schedulers.py +++ b/schedulers.py @@ -169,7 +169,7 @@ def parent_scheduler(target): name="branchselector", default="master", label="Release Shortcut Selector", - choices=["master", "master-next", "mut", "gatesgarth", "dunfell", "zeus", "warrior", "thud", "sumo", "rocko", "pyro", "morty"], + choices=["master", "master-next", "mut", "hardknott", "gatesgarth", "dunfell", "zeus", "warrior", "thud", "sumo", "rocko", "pyro", "morty"], selectors={ 'master': { 'branch': 'master', @@ -202,6 +202,16 @@ def parent_scheduler(target): 'branch_meta-mingw': 'master', 'branch_oecore': 'master', }, + 'hardknott': { + 'branch': 'hardknott', + 'branch_poky': 'hardknott', + 'branch_bitbake': '1.50', + 'branch_meta-arm': 'hardknott', + 'branch_meta-gplv2': 'hardknott', + 'branch_meta-intel': 'hardknott', + 'branch_meta-mingw': 'hardknott', + 'branch_oecore': 'hardknott', + }, 'gatesgarth': { 'branch': 'gatesgarth', 'branch_poky': 'gatesgarth', @@ -354,7 +364,7 @@ schedulers.append(sched.Nightly(name='nightly-auh', branch='master', properties= # If any of our sphinx docs branches change, trigger a build schedulers.append(sched.AnyBranchScheduler(name="yocto-docs-changed", - change_filter=util.ChangeFilter(project=["yocto-docs"], branch=["master", "master-next", "gatesgarth", "dunfell", "transition"]), + change_filter=util.ChangeFilter(project=["yocto-docs"], branch=["master", "master-next", "hardknott", "gatesgarth", "dunfell", "transition"]), codebases = ['', 'yocto-docs', 'bitbake'], treeStableTimer=60, builderNames=["docs"])) -- 2.30.2
|
|
need Sysvinit as system manager in Rocko Version
#rocko
rohit jadhav
I have created rootfs with Rocko yocto version.
I need sysyvinit as system manager instead of Systemd. I have tried with following in local.conf DISTRO_FEATURES_append = " sysvinit" VIRTUAL-RUNTIME_init_manager = "sysvinit" VIRTUAL-RUNTIME_initscripts = "initscripts"
|
|
Re: QA notification for completed autobuilder build (yocto-3.3.rc2)
Sangeeta Jain
Hello All,
toggle quoted messageShow quoted text
This is the full report for yocto-3.3.rc2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high milestone defects. No new issue found. Thanks, Sangeeta
-----Original Message-----
|
|