This is provided by wireless-regdb https://git.yoctoproject.org/poky/tree/meta/recipes-kernel/wireless-regdb/wireless-regdb_2023.02.13.bb This is provided by linux-firmware-imx-sdma-imx7 https://git.y

#imx6 #kirkstone #yocto #linux #bitbake

Hi, I am trying to build an image using kas built tool for ti TDA4VM. For this I have created the attached j721e.yml file. When I put machine as j721e-evm it is showing the below error " Overrides cou

#bitbake #kirkstone #yocto

On 2023-02-02 10:15, Gary Huband via lists.yoctoproject.org wrote: Yes please, it does cherry-pick back cleanly but I didn't take the time to build/test. FYI: https://www.openembedded.org/wiki/How_to_

#kirkstone

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

Hi Yocto community, I figured out what happened, hopefully this is useful to anyone. We did use parts from the meta-cloud-service repository, to be specific the meta-openstack. That layer has a qemu_6

#kirkstone #sdk

Is there documentation for the bootimg-efi plugin? Thanks Gary From: Mittal, Anuj <anuj.mittal@...> Sent: Wednesday, December 7, 2022 10:05 PM To: Gary Huband <Gary@...>; yocto@lis

#kirkstone #systemd

I am new to Yocto, and am trying to build core-image-minimal with multilib using the latest Kirkstone release. The image builds ok without the multilib config entries, but adding the entries (local.co

#kirkstone

Hi Sébastien, The logic seems reasonable to me, yes. We could have used the deploy directory instead and depend on the do_deploy task instead of the do_populate_sysroot but I think it is actually safe

#kirkstone

The Suricata recipe Python environment variable is PYTHON_SITEPACKAGES_DIR="/usr/lib64/python3.10/site-packages"

#kirkstone #bitbake

Related: https://github.com/rhboot/efivar/issues/220

#kirkstone

I'm having the exact same issue when just modifying a custom linux recipie which is essntially the same as the one provided but referencing 5.15 after transposing recipies from dunfell to kirkstone. T

#kirkstone #devtool #yocto

Hi community, I'm wondering how to manage the bootloader files contents in a X86_64 machine and if those files have a relation with the WKS.in file. By doing a bitbake -e <my_image> I can't figure out

#linux #kirkstone #yocto

Good Afternoon, I am updating a project from Honister to Kirkstone, Has anyone else run into an issue with python files with a #!/usr/bin/python header throwing the (abbreviated) Error below? This did

#python #kirkstone

Hello: I built kirkstone core-image-sato from scratch no modifications, clean build was going test kirkstone out… When I went to run using qemu I saw the following issue with “tun”, even after a manua

#kirkstone

Hi Joshua, It's 100% my fault, I'm mixed 2 variables: ROOTFS_POSTPROCESS_COMMAND IMAGE_POSTPROCESS_COMMAND My "ln " command have to be placed into IMAGE_POSTPROCESS_COMMAND, not ROOTFS_POSTPROCESS_COM

#kirkstone #python #bitbake

Forgot to mention that the build machine is x86_64 and I want to build for target aarch64. This is the generated bitbake recipe: # Auto-Generated by cargo-bitbake 0.3.15 # inherit cargo pkgconfig # If

#bitbake #toolchain #rust #kirkstone