Hi, I'd li to include as a kernel module the huawei_cdc_ncm.c file and autoloaded as a kernel object. I did this in the main recipie file, but it's not enogh: KERNEL_MODULE_AUTOLOAD += "cdc_ncm.ko" I

#kernel

I am still seeing the Nothing PROVIDES 'init-system-helpers-service'... I am currently working around this be over-writing the "mountnfs.sh" script, but I want resolve this issue so we are 100% Yocto

#yocto #kernel

From shell... I just checked the mega-manual, will rerun as described...

#yocto #kernel

not sure why that wouldn't work, it's what i've used for years. rday

#yocto #kernel

Hi, I m working on the yocto project. I can be able to create image (core-image-base) and u-boot (imx-boot-sd.bin). I can able to boot these images from the sdcard. But I want to boot u-boot from eMMC

#yocto #kernel #uboot #linux

in this case you might be lucky we already have recipe http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/socketcan/can-isotp_git.bb?h=master its blacklisted because it needs

#yocto #dunfell #apt #tx2 #kernel

you need to add openssl to RDEPENDS for busybox.

#kernel

Ok, so I am trying to understand the impact of the following issue seen under our “zeus” based Intel platform build: https://patchwork.kernel.org/project/dri-devel/patch/20190905181834.6234-1-daniel.v

#yocto #zeus #kernel

Dear all, I have 4 different topics on which I can't find a correct answer on internet. I am developing a new system base on the Raspberrypi CM3+ with our custom board. I am using Yocto with the meta-

#raspberrypi #rpi #cm3 #dunfell #kernel

Hi, I'm new to Yocto Project/Embedded Linux. I had added hostapd recipe (https://layers.openembedded.org/layerindex/recipe/28409/) into my build image, and when I try to run "hostapd hostapd.conf" in

#linux #kernel #dunfell

lists.yoctoproject.org wrote: The log indicates that it is missing a dependency which ships "rpc/rpc.h". Some googling turned up this discussion on the openembedded-core mailing list: https://lists.op

#yocto #kernel #zeus

As you mentioned updating the kernel does not fix the other packages. And we don't have know how about each linux package so its not that easy to fix it by ourself. So, I am trying to know if there is

#kernel #linux #yocto #zeus

Mb build was setup and done under one layer, with “distro” and “bsp“ at the same layer, I wanted to split them up into separate layers inorder to better conform to the Yocto standard…. (Note my kernel

#yocto #kernel

Greetings ! I am trying to integrate the ubuntu 20.04 Root file system with the yocto build . Ultimately my final image should consists of : Bootloader and Kernel : From default yocto build system. Ro

#linux #yocto #kernel

What would cause this “opkg” to not pull in these components ?, and how do I ensure “opkg” can find these components : “inetutils-rsh” and “inetutils-rshd” ? Using “zeus”…, error log attached… Build o

#yocto #kernel

Hi Alexandre, Thanks for your guidance. I have updated my device tree with dummy codec as linux. Still the sound card is not properly added. When i tried to verify that using aplay, i got error messag

#kernel #yocto

Hello, I need Clang compiler apart from currently available default gcc compiler as I am trying to compile eBPF which will run on my custom yocto which is based on core-image-minimal. Therefore I adde

#sdk #dunfell #yocto #kernel #linux

I am developing a pair of driver modules that share some functionality. Thus it would be convenient for the source files of the drivers to share a directory with the source files of the shared functio

#kernel #linux

Hi Group, I am trying to add a new layer for a custom RTOS which supports RISCV32 architecture. When i run bitbake i bumped into following error: " ERROR: /home/gitee-ohos/ohos/AllScenariosOS/sources/

#kernel

Thanks a lot for the pointers! I had a deeper look and that is apparently completely expected behavior that barebox uses the internal device tree for booting the kernel as long as global.bootm.oftree

#kernel