Hi Ida, We have a "tasty menu of bugs" ;-) for people who are new to Yocto: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bug Let me know if any of those appeal to you or just register in the

#yocto #python #linux

Thanks... Yesterday I decided to go with ntpq/ntpdate/and a ntpstat script which does some basic stats through ntpd/ntpq/ntpdate and Chrony. We will see how it goes might be enough... Steve

#systemd #yocto #linux

closed you can get is qemuarm64, you can also use package management in image and install/update/remove individual packages. something like https://imxdev.gitlab.io/tutorial/How_to_apt-get_to_the_Yoct

#linux #devtool #yocto

Hi all, I'm using Yocto warrior building a system based on NIVIDA tegra TX2i. My tree is using an external toolchain, gcc linaro 7.2.1 (specified through EXTERNAL_TOOLCHAIN variable in local.conf). I'

#yocto #toolchain #linux

Hi Sheng Leong, Start from a core-image-minimal and add packages manually. Only the packages that are specified to be installed explicitly in your image recipe and the packages specified in RDEPENDS a

#linux #yocto #cups #hplip

I think you could start by defining new tune files for this look into meta/conf/machine/include/riscv/arch-riscv.inc and also tune-riscv.inc to understand the underlying mechanism, we currently have l

#devtool #linux #toolchain #yocto

Hello Martin and Josef, I will try to include the patch in a append-recipe... Thanks a lot for your help, Bernd

#linux #qemu #yocto

What I did was, ran the following command to see what all gets installed.. bitbake <image> -e |grep -v ^# |grep "^DISTRO_FEATURES=\|^IMAGE_FEATURES=" Then used DISTRO_FEATURES_remove in the local.conf

#linux #yocto

Hi Scott, Up till there, this discussion would probably fit some kernel communities more than the Yocto one. A few things though: - Bear in mind that using bitbake -c menuconfig virtual/kernel, the ch

#yocto #linux

I assume you tried to compile on the target using the resulting image, if that's the case the package isn't installed. By using 'oe-pkgdata-util find-path */libc.a' in your build workspace, you could

#sdk #yocto #linux

Hi, I apply a few small patches in linux-raspberrypi to use a custom logo depending on an environment variable MY_VENDOR_NAME: I have added MY_VENDOR_NAME to BB_ENV_EXTRAWHITE, and based on the value

#yocto #raspberrypi #linux

I am trying to print using Yocto, but I am clueless on how to enable the printing. The printer I am using is HP Deskjet 2135 Ink Advantage. CUPS version: 2.2.8 HPLIP version: 3.15.6 Avahi version: 0.8

#cups #linux #yocto

Hi, when i am trying to add meta-python from meta-openembedded i am getting following error i have kept meta-openembedded,meta-raspberrypi into same branch dunfell /Raspberrypi4-yocto$ bitbake-layers

#linux #raspberrypi #yocto

Am soory paul, But i was actually trying to check if sdimage is generated or not. I was unaware of . wic. bz2 image. So suggested the above commands. Sorry pankaj. Thanks Siddhartha V

#linux #yocto

hello sir, Thanks for the reply. I searched for what you have suggested, but it looks like I am missing something here. I didn't see kernel.conf file I have shared my bblayers.conf details also , plea

#yocto #raspberrypi #linux

You did nothing wrong, precisely. core-image-base is a base image that doesn’t do much beyond boot into a working command line environment. If you want a working toolchain (gcc and friends) on the ima

#apt #linux #yocto

Not sure if there is a dedicated layer for firecracker, but you can start with QEMU/KVM which is supported and then extend/customise it

#linux #yocto

Hi, Following up on my earlier email; it seems that a BSP layer targeting the Firecracker VM model could/should pay some dividends. Recapping the Firecracker 'board' model is: "only 5 emulated devices

#linux #yocto

Those recipes exist in other layers, meta-printing is dead so please don't use it. Ross

#cups #yocto #linux