[yocto] [meta-intel-fpga] [PATCH] layer.conf: add layer compatibility to hardknott

From: Meng Li Signed-off-by: Meng Li --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 756e7f4..4b45db9 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -9,6 +9,6 @@ BBFILE_PATTERN_meta-intel-fpga :=

Re: [yocto] #golang: go fetches dependencies in compile phase

Hi, My comments are inline. On 12/04/2021 14:47, Juergen Landwehr wrote: Hi Robert, thanks for your thoughts. I see your point and the last thing I want is "NOT reproducable builds". But dependency management in go is not that arbitrary as it may seem. ... if everybody does what they are

Re: [yocto] Cannot execute nodejs

I was able to solve it by forcing recompiling nodejs with `bitbake -f -c compile nodejs` Not sure what happened there -- Alessandro Tagliapietra On Wed, Apr 14, 2021 at 11:51 AM Alessandro Tagliapietra < tagliapietra.alessan...@gmail.com> wrote: > Hi everyone, > > I've installed nodejs and

[yocto] Cannot execute nodejs

Hi everyone, I've installed nodejs and node-red  by using meta-oe and meta-iot-cloud, with IMAGE_INSTALL_append = " nodejs node-red bash" it was initially working but then I've got some pseudo aborts that fixed automatically and then I saw that: - /usr/bin/node doesn't have the +x flag - the

[yocto] #yocto #sdk SDK_EXTRA_TOOLS inclussion of python-native and devtool

Working with zeus 3.0.4, extended SDK... Could someone explain what I overlooked, or why this issue pops up with python-native support inclusion ? Thanks... When I add in native-python3 support # # Additional SDK Setup variables # SDKIMAGE_FEATURES_append = " staticdev-pkgs"

[yocto] Yocto Technical Team Minutes, Engineering Sync, for April 13, 2021

Yocto Technical Team Minutes, Engineering Sync, for April 13, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto Project Summit is taking place May 25-26 2021 details:

[yocto] [meta-rockchip][PATCH v2 4/6] WIP optee-os: rk3399 support

From: Yann Dirson 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 +++

[yocto] [meta-rockchip][PATCH v2 6/6] WIP kernel config feature for OP-TEE activation

From: Yann Dirson 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

[yocto] [meta-rockchip][PATCH v2 2/6] truster-firmware-a: include optee support when requested by DISTRO_FEATURE

From: Yann Dirson 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:

[yocto] [meta-rockchip][PATCH v2 5/6] WIP nanopi-m4: declare OP-TEE presence in devicetree

From: Yann Dirson 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 +++

[yocto] [meta-rockchip][PATCH v2 0/6] WIP/RFC OP-TEE support for ARM and rk3399

From: Yann Dirson 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

[yocto] [meta-rockchip][PATCH v2 3/6] u-boot: include optee-os as BL32 when requested by DISTRO_FEATURE

From: Yann Dirson 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 --- recipes-bsp/u-boot/u-boot%.bbappend | 9

[yocto] [meta-rockchip][PATCH v2 1/6] optee: condition for "optee" DISTRO_FEATURE

From: Yann Dirson 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

Re: [yocto] [meta-security][PATCH] Clearly define clang toolchain in Parsec recipes

merged, Thanks On 4/12/21 8:30 AM, Anton Antonov wrote: > Signed-off-by: Anton Antonov > --- > .../recipes-parsec/parsec-service/parsec-service_0.7.0.bb | 4 ++-- > meta-parsec/recipes-parsec/parsec-tool/parsec-tool_0.3.0.bb | 3 +-- > 2 files changed, 3 insertions(+), 4 deletions(-) > >

Re: [yocto] [meta-security][PATCH 1/2] Add meta-parsec layer into meta-security.

Merged, Thanks On 4/9/21 4:14 AM, Anton Antonov wrote: > From: Anton Antonov > > The layer contains recipes for Parsec service version 0.7.0 and parsec-tool > version 0.3.0. The Parsec service is built with all supported providers and > deployed with the MbedCrypto provider enabled. Both

Re: [yocto] [meta-security][PATCH] initramfs-framework-ima: introduce IMA_FORCE

merged, Thanks On 4/8/21 11:38 AM, Ming Liu wrote: > From: Ming Liu > > Introduce IMA_FORCE to allow the IMA policy be applied forcely even > 'no_ima' boot parameter is available. > > This ensures the end users have a way to disable 'no_ima' support if > they want to, because it may expose a

Re: [yocto] [meta-security][PATCH] Use libest "main" branch instead of "master".

merged thanks, armin On 4/7/21 3:19 AM, Anton Antonov wrote: > This patch fixes the issue: > > WARNING: libest-3.2.0-r0 do_fetch: Failed to fetch URL > git://github.com/cisco/libest, attempting MIRRORS if available > ERROR: libest-3.2.0-r0 do_fetch: Fetcher failure: Unable to find revision >

Re: [yocto] [meta-security][PATCH] meta: drop IMA_POLICY from policy recipes

merged. thanks -armin On 3/22/21 6:02 AM, liu.min...@gmail.com wrote: > From: Ming Liu > > IMA_POLICY is being referred as policy recipe name in some places and it > is also being referred as policy file in other places, they are > conflicting with each other which make it impossible to set a

[yocto] [meta-security][PATCH] gitlab-ci: Move all parsec builds into a separate job

Signed-off-by: Anton Antonov --- .gitlab-ci.yml | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index f673ef6..f155ba0 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -27,7 +27,6 @@ qemux86: extends: .build script: -

[linux-yocto] [PATCH 2/2] drivers: pci: s32gen1: fix build warning of unused function

The function s32gen1_pcie_config_irq() is used when CONFIG_PCI_S32GEN1_EP_MSI or CONFIG_PCI_DW_DMA enabled, so add check line to fix the build warning. Signed-off-by: Zhantao Tang --- drivers/pci/controller/dwc/pci-s32gen1.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[linux-yocto] [PATCH 1/2] drivers: crypto: hse: fix unused variable build warning

The err variable is used when CONFIG_CRYPTO_DEV_NXP_HSE_UIO disabled, so add check line to fix build warning. Signed-off-by: Zhantao Tang --- drivers/crypto/hse/hse-core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/crypto/hse/hse-core.c b/drivers/crypto/hse/hse-core.c index

[linux-yocto] [linux-yocto v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx]: patches to fix build warnings

Hi Bruce, There are two patches to fix build warnings for pci and hse driver. Would you please help to merge these patches into linux-ycoto kernel, v5.10, branch is v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this