[PATCH][linux-yocto][linux-yocto v5.10/standard/sdkv5.4/xlnx-soc][linux-yocto-dev standard/xlnx-soc] arm: fix IPI_CPU_BACKTRACE wrong number and handler missing issue

From: Quanyang Wang IPI_CPU_BACKTRACE should be 7 not 8 and the handler for IPI_CPU_BACKTRACE was dropped when I porting SDK patches. Let's add it back to fix the issue when echo "l" to /proc/sysrq-trigger failed. Signed-off-by: Quanyang Wang --- arch/arm/kernel/smp.c | 18 ++

[yocto] [meta-zephyr][PATCH 0/3] Fix efi generation and add x86 MACHINE confs (cover letter)

(1) zephyr-kernel-src: fix efi generation failure for x86 boards With zephyr v2.5.0, EFI binary generation support has been added for x86 board (64-bit mode). To achieve this, an python tool[1] has been added to convert zephyr EFL file into an EFI appliable. But unfortunately at current this

[yocto] [meta-zephyr][PATCH 3/3] intel-x86-32.conf: add common MACHINE for x86 (32-bit) BOARDS

User need to specify board value to ZEPHYR_BOARD in local.conf ZEPHYR_BOARD = "minnowboard" By default it set to MinnowBoard Max 'minnowboard' Currently 32-bit supported boards: * up_squared_32 * minnowboard Ref: https://docs.zephyrproject.org/latest/boards/x86/index.html Signed-off-by: Naveen

[yocto] [meta-zephyr][PATCH 2/3] intel-x86-64.conf: add common MACHINE for x86 (64-bit) BOARDS

User need to specify board value to ZEPHYR_BOARD in local.conf ZEPHYR_BOARD = "ehl_crb" By default it set to Elkhart Lake CRB 'ehl_crb' Currently 64-bit supported boards: * up_squared * ehl_crb_sbl * ehl_crb Ref: https://docs.zephyrproject.org/latest/boards/x86/index.html Signed-off-by: Naveen

[yocto] [meta-zephyr][PATCH 1/3] zephyr-kernel-src: fix efi generation failure for x86 boards

With zephyr v2.5.0, EFI binary support has been added for x86 board (64-bit mode). To achieve this, an python tool[1] has been added to convert zephyr ELF file into an EFI appliable. But currently this does not work with Yocto cross-compilation env. This patch fix this issue and allow to build

Re: [linux-yocto][linux-yocto v5.10/standard/sdkv5.4/xlnx-soc][linux-yocto-dev standard/xlnx-soc][PATCH 0/2] xilinx-zynqmp: fix issues for DP

Hi Bruce, On 5/11/21 11:08 AM, Bruce Ashfield wrote: In message: [linux-yocto][linux-yocto v5.10/standard/sdkv5.4/xlnx-soc][linux-yocto-dev standard/xlnx-soc][PATCH 0/2] xilinx-zynqmp: fix issues for DP on 10/05/2021 quanyang.w...@windriver.com wrote: From: Quanyang Wang Hi Bruce and

Re: [yocto] [zeus] python3-dlib #yocto #zeus #python

Thanks for the suggestion, but they are using the C++ API as well. I already created a recipe for the C++ API of dlib and it is working, the only thing needed is compitling the Python API. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#53465):

Re: [yocto] [zeus] python3-dlib #yocto #zeus #python

On Tue, May 11, 2021 at 1:00 PM Bel Hadj Salem Talel wrote: > > Hi All, > > Did anyone manage to create a recipe for python dlib from the official site > https://github.com/davisking/dlib ? > They provide C++ and Python API, (CMakeLists + setup.py). All recipes found > for dlib are inheriting

[yocto] [zeus] python3-dlib #yocto #zeus #python

Hi All, Did anyone manage to create a recipe for python dlib from the official site https://github.com/davisking/dlib ? They provide C++ and Python API, (CMakeLists + setup.py). All recipes found for dlib are inheriting cmake for C++. But when inheriting setuptools3 error occurs. Thanks, Talel

Re: [yocto] Improving NPM recipe build speed

Hi Nicolas, Thank you for the advice, that would work for files outside the npm packages! Hopefully there's a way to improve npm install speed too, I was hoping there was a way to just run npm install instead of going through the yocto npm process (which takes 30 mins vs < 1 min that npm takesi

[yocto] [meta-rockchip][PATCH] trusted-firmware-a: Fix rk3399 build with gcc11

Signed-off-by: Khem Raj Cc: Ross Burton --- .../files/0001-Fix-build-with-gcc-11.patch| 34 ++ .../0001-dram-Fix-build-with-gcc-11.patch | 34 ++ ...-Use-compatible-.asciz-asm-directive.patch | 31

Re: [yocto] [zeus] python3-numpy: No module named 'numpy.core._multiarray_umath' #yocto #zeus #python

On 11.05.21 18:14, Bel Hadj Salem Talel wrote: Hi All, I integrated python3-numpy in my image and when trying to import it I get this error: (python3 version: 3.7.7) -- >>> import cv2 OpenCV bindings requires "numpy" package. Install it via command:     pip install numpy Traceback (most

[yocto] [zeus] python3-numpy: No module named 'numpy.core._multiarray_umath' #yocto #zeus #python

Hi All, I integrated python3-numpy in my image and when trying to import it I get this error: (python3 version: 3.7.7) -- >>> import cv2 OpenCV bindings requires "numpy" package. Install it via command: pip install numpy Traceback (most recent call last): File

[yocto] [meta-rockchip][PATCH v6 6/6] WIP NanoPi-M4: activate BT support

From: Yann Dirson Take the firmware from rbwifibt, as a compatible one does not seem to be available in broadcom-bt-firmware. Disclaimer: I have only been able to scan/pair with devices, I could not establish a connection. However, with the same board I've had the same results with the board

[yocto] [meta-rockchip][PATCH v6 5/6] WIP Import rkwifibt-firmware from vendor's meta-rockchip

From: Yann Dirson As far as the AP6356S in NanoPi-m4 is concerned, the included wifi firmware is for Rockchip's kernel tree, but for Bluetooth firmware this seems to be the proper "upstream" package. Changes from Rockchip's version: - use /lib/firmware/brcm/, not /system/etc/firmware/ - include

[yocto] [meta-rockchip][PATCH v6 4/6] NanoPi-M4: activate Wifi support

From: Yann Dirson --- conf/machine/include/nanopi-m4.inc| 5 - recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg | 5 + 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/nanopi-m4.inc index

[yocto] [meta-rockchip][PATCH v6 1/6] 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),

[yocto] [meta-rockchip][PATCH v6 2/6] WIP linux-yocto: add workaround to disable VOPL usage on HDMI

From: Yann Dirson There is a known issue in mainline kernel making the machine unusable once a HDMI screen is plugged. This patch lets VOPB be alone to use the HDMI port and avoids the issue while providing wupport for the largest set of video modes, at the expense of double-screen support.

[yocto] [meta-rockchip][PATCH v6 0/6] kmeta BSP for nanopi-m4

From: Yann Dirson With this version the Wifi works (requires recent poky master for a linux-firmware fix). I'm not especially happy with the BT support: - it uses the rkwifibt repo because I don't have any other BT firmware for this chip - I was not able to get it to work on the board I have

[yocto] [meta-rockchip][PATCH v6 3/6] linux-firmware: import variables file for ap4356s firmware from armbian

From: Yann Dirson This is required for wifi support on nanopi-m4 with kernel 5.10. This is dependant on poky commit commit 698fd81c551b52ff7f4a26e42d9acf9ad4ce5639, "linux-firmware: include all relevant files in -bcm4356". This file was fetched from

Re: [linux-yocto] [PATCH v5.10 0/1] Add ACPI fixup for rcu_nocb/nohz "N" alias

[Re: [linux-yocto] [PATCH v5.10 0/1] Add ACPI fixup for rcu_nocb/nohz "N" alias] On 10/05/2021 (Mon 23:03) Bruce Ashfield wrote: > In message: [PATCH v5.10 0/1] Add ACPI fixup for rcu_nocb/nohz "N" alias > on 07/05/2021 Paul Gortmaker wrote: > > > Bruce, Yocto kernel folks, > > > > This is a

[yocto] Yocto Project Status WW19`21

Current Dev Position: YP 3.4 M1 Next Deadline: 7th June 2021 YP 3.4 M1 build Next Team Meetings: * Bug Triage meeting Thursday May 13th at 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *

[yocto] Kernel/application signing and verification

Hi, I'm not sure if this is the appropriate mailing list to ask this question. I am working on customizing a BSP for an Nvidia Jetson Nano based board (using the meta-tegra layer as the basis for most of the development). One of the requirements for the project is to get secure-boot working,

Re: [yocto] esdk issue using hardknott sources #yocto

On Mon, 2021-05-10 at 21:13 -0700, sateesh m wrote: > Hi Guys, > >              I have successfully built core-image-base image using hardknott > sources.  I am trying to build  > sdk & populate_sdk_ext. I have built successfully.but when I running > ./oecore-x86_64-riscv64-toolchain-ext- >

[yocto] How to use xtensa/gcc

Hello All, I wonder if there is a chance to use xtensa compiler within Yocto to run the code at DSP/IP? I would like to ask you if there are some examples to compile and run such example code or recommendation to do so? Thank you. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to

Re: [yocto] KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Hi Martin! On Mon, 10 May 2021, 12:25, Martin Jansa wrote: > On Mon, May 10, 2021 at 12:08:22PM +0300, Thomas Hill via > lists.yoctoproject.org wrote: > > On Fri, 7 May 2021, 15:28, Richard Purdie > > > > > On Fri, 2021-05-07 at 10:10 +0300, Thomas Hill via lists.yoctoproject.org > > >

[yocto] Split deploy result in multiple partitions

Hi all I have a simple question. Is possible to generate as artifacts the single partition results as IMG type for each partition and a total result as wic image? Michael -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#53446):

[yocto] [meta-gplv2][PATCH] conf/distro: Restore btrfs-tools since it was relicensed

libbtrfsutil was relicensed from LGPL-3.0+ to LGPL-2.1+, so it is no longer necessary to remove btrfs-tools. Signed-off-by: Robert Joslyn --- conf/distro/include/disable-gplv3.inc | 1 - 1 file changed, 1 deletion(-) diff --git a/conf/distro/include/disable-gplv3.inc