I am currently working on a kmeta BSP for the rockchip-based NanoPI M4 [1], and I'm wondering how I should be providing kernel patches, as just add ing "patch" directives in the .scc does not get them

Hello All, This is the full report for yocto-3.2.4.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== No high

<robert.joslyn@...> wrote: Given what I have seen so far, I am wondering if that is the right place to start. To summarize: There appears to be general agreement that the idea is a

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 *

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 *

(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

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

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.

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

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

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

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

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]

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"

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

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

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

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

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

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