Re: [yocto] [meta-rockchip][PATCH v3 0/7] OP-TEE support for ARM and rk3399

Le ven. 23 avr. 2021 à 19:19, Joshua Watt a écrit : > > > On 4/23/21 11:58 AM, Yann Dirson wrote: > > From: Yann Dirson > > Changes from v2: > - turn the DISTRO_FEATURE idea into separate RFC patches so as to allow >merging of basic support > - remove optee-os patch that proved unnecessary

Re: [yocto] [meta-rockchip][PATCH v3 3/3] linux-yocto: add an initial NanoPi-M4 BSP

> create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4-standard.scc > create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4-tiny.scc > create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4.cfg > create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4.scc > create mode 10

[yocto] Switching a recipe between git head and git tag (for a release)

Hello community, I am looking for a best practice / a simple solution for switching the SRCREV in a bitbake recipe between git master HEAD (default, used in nightly builds) and a tagged release version (needed for a reproducible release config). How can I minimize the amount of changes necess

[yocto] Not all config fragments applied

I added a custom layer and under recipes-kernel I try to apply kernel config fragments: └[ *~* ]> cat poky/meta-insidem2m/recipes-kernel/linux/linux-yocto_5.10.bbappend FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" SRC_URI += "\ file://wext.cfg \ file://at24.cfg \ file://leds.cfg \ file://

Re: [yocto] [PATCH yocto-autobuilder-helper 1/4] config.json: add "collect-data" template

On 2021-04-15 9:52 a.m., Richard Purdie wrote: [Please note: This e-mail is from an EXTERNAL e-mail address] On Tue, 2021-04-13 at 13:02 -0400, sakib.sa...@windriver.com wrote: collect-data template can run arbitrary commands/scripts on a regular basis and logs the output in a file. See oe-co

[yocto] AppArmor with BusyBox

I'm using the OpenBMC system (https://github.com/openbmc/openbmc) and I've tried to enable AppArmor functionality from the 'meta-security' layer. To achieve this I've added these strings to my local.conf file: DISTRO_FEATURES_append = " apparmor" IMAGE_INSTALL += "apparmor" The AppArmor functiona

[yocto] AppArmor with BusyBox

I'm using the OpenBMC system (https://github.com/openbmc/openbmc) and I've tried to enable AppArmor functionality from the 'meta-security' layer. To achieve this I've added these strings to my local.conf file: DISTRO_FEATURES_append = " apparmor" IMAGE_INSTALL += "apparmor" The AppArmor functiona

Re: [yocto] AppArmor with BusyBox

Hi Konstantin, On Mon, Apr 26, 2021 at 01:45:30PM +0300, Konstantin Aladyshev wrote: > I'm using the OpenBMC system (https://github.com/openbmc/openbmc) and > I've tried to enable AppArmor functionality from the 'meta-security' > layer. > > To achieve this I've added these strings to my local.con

[yocto] [meta-security][PATCH] libseccomp: drop recipe. In core now

Signed-off-by: Armin Kuster --- recipes-security/libseccomp/files/run-ptest | 4 -- .../libseccomp/libseccomp_2.5.1.bb| 47 --- 2 files changed, 51 deletions(-) delete mode 100644 recipes-security/libseccomp/files/run-ptest delete mode 100644 recipes-security/libs

Re: [yocto] Switching a recipe between git head and git tag (for a release)

Hi Martin, On Mon, Apr 26, 2021 at 12:41:18PM +, Martin Hollingsworth wrote: > Hello community, > > I am looking for a best practice / a simple solution for switching the SRCREV > in a bitbake recipe between git master HEAD (default, used in nightly builds) > and a tagged release version (n

[yocto] [meta-rockchip][PATCH v4 1/3] NanoPi-M4: let all variants use the same KMACHINE type

From: Yann Dirson This will allow us to define a single set of kernel BSP for all variants of the board (which only need to differ in u-boot dts). Signed-off-by: Yann Dirson --- conf/machine/include/nanopi-m4.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/nanopi-m

[yocto] [meta-rockchip][PATCH v4 0/3] kmeta BSP for nanopi-m4

From: Yann Dirson Changes in v4: - install our bsp files in bsp/rockchip/ rather than directly in bsp/ - also add "serial" to MACHINE_FEATURES Changes in v3: - relocate the bsp files into files/ so we don't have to add linux-yocto/ to FILESEXTRAPATHS for all other kernels - removed the "don't

[yocto] [meta-rockchip][PATCH v4 2/3] NanoPi-M4: declare "usbhost" and "serial" in MACHINE_FEATURES

From: Yann Dirson Signed-off-by: Yann Dirson --- conf/machine/include/nanopi-m4.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/nanopi-m4.inc index 603160f..a14b705 100644 --- a/conf/machine/include/nanopi-m4.inc +++ b/conf/ma

[yocto] [meta-rockchip][PATCH v4 3/3] linux-yocto: add an initial NanoPi-M4 BSP

From: Yann Dirson This patch provides "standard" and "tiny" BSP. There is still much work to be done in dispatching feature to individual scc files - the more boards we can support the better it will get. Not all SoC/board features are covered yet either (esp. Wifi/Bluetooth and audio jack), and

[yocto] Criteria for bitbake to skip recipes #bitbake

I wonder what are all possible criteria for Bitbake to decide to skip recipe (please compare to reports delivered by bitbake-layers). Recipe overlay, recipe version, others? Which knowledge source to find more details in? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group

Re: [yocto] [meta-security] [dunfell] [PATCH 0/3] Backport several IMA fixes to LTS dunfell

On 4/18/21 11:41 PM, liu.min...@gmail.com wrote: > From: Ming Liu I have not forgotten about these. My build system is backlogged. I hope to process these by this weekend. -armin > > Ming Liu (3): > ima-evm-keys: add file-checksums to IMA_EVM_X509 > meta: drop IMA_POLICY from policy recip

[yocto] Hardknott: grub immediately reboots

After upgrading from Dunfell (YP 3.1) to Hardknott (YP 3.3), our firmware was unable to boot.  Our target hardware is x86-64 booting in legacy BIOS mode using grub on a variety of motherboards and CPUs.  The grub menu would never show up; instead it would reboot immediately, leading to an endless r

[yocto] Improving NPM recipe build speed

Hi everyone, I'm making an image that includes the node-red recipe from meta-iot-cloud. The whole process takes about 30+ minutes for that recipe alone (most of the time spent in do_configure). Now I want to override the recipe systemd service file and create a nodered user. Every time I change

[yocto] [meta-zephyr][PATCH 0/1] Gitlab CI for meta-zephyr

No one asked for it, but here it is, Gitlab CI for meta-zephyr. Stolen and repurposed from meta-arm. This building and testing should help discover regressions more quickly. And if you include this patch, I'll do nightly builds via my gitlab account (https://gitlab.com/jonmason00/meta-zephyr

[yocto] [meta-zephyr][PATCH 1/1] CI: add Gitlab CI support

Signed-off-by: Jon Mason --- .gitlab-ci.yml| 172 ++ ci/96b-avenger96.yml | 9 ++ ci/96b-nitrogen.yml | 6 ++ ci/acrn.yml | 6 ++ ci/base.yml | 35 ci/check-machine-coverage | 26 ++ ci/che

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newc

[yocto] Current high bug count owners for Yocto Project 3.4

All, Below is the list as of top 50 bug owners as of the end of WW17 of who have open medium or higher bugs and enhancements against YP 3.4. There are 130 possible work days left until the final release candidates for YP 3.4 needs to be released. Who Count richard.pur...@linuxfoundation.org

[yocto] Enhancements/Bugs closed WW17!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.pur...@linuxfoundation.org 16 yf...@uwaterloo.ca 8 michael.opdenac...@bootlin.com 3 mhalst...@linuxfoundation.org 2 randy.macl...@windriver.com 2 prabin...@arm.com 1 Grand T

[yocto] M+ & H bugs with Milestone Movements WW17

All, YP M+ or high bugs which moved to a new milestone in WW17 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 11766 nobody group added by systemd sysusers.d randy.macl...@windriver.com y

[yocto] ERROR: Fetcher failure: Fetch command export...

When I trying using bitbake to build openembedded Linux kernel, it dies with these download failures: NOTE: Fetching uninative binary shim http://downloads.yoctoproject.org/releases/uninative/3.0/x86_64-nativesdk-libc.tar.xz;sha256sum=5ec5a9276046e7eceeac749a18b175667384e1f445cd4526300a41404d98