yocto@lists.yoctoproject.org

[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

By Naveen Saini · #53467 ·

[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

By Naveen Saini · #53466 ·

Re: [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.

By Bel Hadj Salem Talel <bhstalel@...> · #53465 ·

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

did you look into http://layers.openembedded.org/layerindex/recipe/135534/

By Khem Raj · #53464 ·

[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

By Bel Hadj Salem Talel <bhstalel@...> · #53463 ·

Re: 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

By Alessandro Tagliapietra · #53462 ·

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

Signed-off-by: Khem Raj <raj.khem@...> Cc: Ross Burton <ross.burton@...> --- .../files/0001-Fix-build-with-gcc-11.patch | 34 ++++++++++++++++++ .../0001-dram-Fix-build-with-gcc-11.patch

By Khem Raj · #53461 ·

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

According to [1] yes - you might want to consider back porting one of the more recent versions of numpy from [2], as you are using a pretty outdated one [1]

By Konrad Weihmann <kweihmann@...> · #53460 ·

[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"

By Bel Hadj Salem Talel <bhstalel@...> · #53459 ·

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

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

By Yann Dirson · #53458 ·

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

From: Yann Dirson <yann@...> As far as the AP6356S in NanoPi-m4 is concerned, the included wifi firmwa= re is for Rockchip's kernel tree, but for Bluetooth firmware this seems to b= e the

By Yann Dirson · #53457 ·

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

From: Yann Dirson <yann@...> --- conf/machine/include/nanopi-m4.inc | 5 ++++- recipes-kernel/linux/files/bsp/rockchip/nanopi-m4.cfg | 5 +++++ 2 files changed, 9

By Yann Dirson · #53456 ·

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

From: Yann Dirson <yann@...> This is required for wifi support on nanopi-m4 with kernel 5.10. This is dependant on poky commit commit

By Yann Dirson · #53455 ·

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

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

By Yann Dirson · #53454 ·

[meta-rockchip][PATCH v6 1/6] linux-yocto: add an initial NanoPi-M4 BSP

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

By Yann Dirson · #53453 ·

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

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

By Yann Dirson · #53452 ·

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

By Stephen Jolley · #53451 ·

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

By Mohammed Billoo · #53450 ·

Re: esdk issue using hardknott sources #yocto

It looks like you're using OE-Core and nodistro and we generally test the eSDK with poky. It also looks like you're using rm_work and we do not test that with eSDK on the autobuilder. For some reason

By Richard Purdie · #53449 ·

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

By Peter Balazovic <balazovic.peter@...> · #53448 ·

Messages