Probably you have two packages that provides that Kernel module. Kernel's default one via kernel-module-split BBClass, and yours with your recipe. Try telling Yocto you have your own runtime provider

#kernel

You can add a kernel config fragment disabling/enabling needed drivers during build and you can either build them into kernel proper or as kernel modules. If you build them as kmods then you have to a

#sdk #yocto #imx8 #kirkstone #kernel

Hello all, I have created a basic image of raspberry pi4 with the help of yocto. That is only a bootable image nothing else there (rpi-basic-image). Now I wanted to apply Rt-patch in that. I searched

#raspberrypi #yocto #patch #dunfell #kernel

This was asked a while back with no answer that I could find, but I am running into the same issue where I can't use FILES:${PN} - to get a kernel udev source file into my build and am wondering if an

#kernel

I am working on a BSP build using Yocto. My physical board has two DSI ports to which panels are connected. Both are 4-lane DSI panels. Panels are defined in device tree and they are initialized and l

#yocto #kernel

Hi Rayaan, Currently DKMS is not supported in Yocto/OE and there are no imminent plans to change that. See the discussion on the topic at https://lists.openembedded.org/g/openembedded-core/message/159

#dunfell #kernel

Bruce, It's an honor to get help from the author himself! I'm starting to understand why they have this: do_configure_prepend() { cp "${S}/arch/${ARCH}/configs/${KBUILD_DEFCONFIG}" "${B}/.config" || b

#dunfell #yocto #kernel

Hi, I have been working on the audio driver. I am trying to access codec driver (TLV320AIC3104) connected to iMX8M over I2C3 and SAI2 lines. While checking for modprobe and modinfo of i2c driver, I'm

#linux #make #yocto #cmake #kernel

ensure that you are using same release branches for all layer repos generally RDEPENDS and RRECOMMENDS should be replaced with RDEPENDS_<pkgname> etc.

#kernel

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 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 wrote a kernel driver which exposes some header to userspace application. Application engineers use generated SDK, so I'd like to export that header file as part of SDK. I added my header to

#kernel #sdk

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

Hi Can you try this patch ( if you are using master ) and see if that helps diff --git a/recipes-devtools/clang/clang_git.bb b/recipes-devtools/clang/clang_git.bb index b8986be..b0c81f1 100644 --- a/r

#sdk #dunfell #yocto #kernel #linux

Hi, My comments are in-line. ... a legal battle maybe? Bring in the lawyers! I would also ask: "What is your use case?" "Did you ask Canonical?" "Does Canonical allow you to do this?" From [1]: "Copyr

#linux #yocto #kernel

I have gotten much closer with Yocto-check-layer, down to the same error for both layers, all other tests passing… Can someone explain what the error means, and what might be causing it ? Meta-intel-b

#yocto #kernel

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

Hi, Please see my comments in-line. I assume your sources are in /ede/tms/yocto/zeus/downloads/ Can you please try without the PATH at the end? The manual does not mention anything like PATH at the en

#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

Just a wild guess, but could your corporate proxy, which is kind of visible in the provided logs, intervene with this - to me it seems to be some MITM box. Do you have any chance to try it without tha

#yocto #kernel