Hi, Does anyone here know how to configure CUPS in Yocto to enable printing functionality? Your reply will be much appreciated Thanks Sheng Leong

#cups #yocto #linux

This meta-printing layer has worked well for me in the past: https://github.com/rossburton/meta-printing.git I was using the 'morty' branch with a meta-ti BSP, so I can't testify to how well it works

#cups #yocto #linux

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

#cups #yocto #linux

Hi, I'm exploring the use of yocto to build [kernels for Firecracker VM's (vmlinux, initrd and rootfs)](https://github.com/bbros-dev/firecracker-kernels/tree/develop). I'm still at the point of workin

#linux #yocto

In that case a tuned kernel build in a dedicated BSP would make sense, yes. Ross

#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

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

Hello, I built the image for Raspberrypi3B+ board. But when boot the board gcc, apt, sudo were not there. Actually only the poweron and poweroff and few basic commnds like, ls, mkdir, whoami were work

#apt #linux #yocto

Hello, I am building the xen minimal image using yocto warrior ("bitbake xen-image-minimal") by giving the target machine as "raspberrypi4". It reached 99% but at last I got below error and the whole

#yocto #raspberrypi #linux

Hi Siddhartha, Caveat: This is generally what I've done, and not specific to any rpi or rhel setup.... If you run `bitbake -e core-image-base | grep "^IMAGE_FEATURES" you'll be able to see what was co

#apt #linux #yocto

Howdy! Am 27.05.2020 um 12:06 schrieb Siddhartha V: This sounds like you actually want an ubuntu. Why not just use it, then? Beating a yocto build into shape will always just leave you wanting and com

#apt #linux #yocto

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

it seems XEN related options are missing from kernel config. Perhaps you can add a config fragment adding them and stitch it to linux-raspberrypi recipe via bbappend.

#yocto #raspberrypi #linux

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

Hi, I have built the image for raspberrypi4 and i have got the following images core-image-minimal.env rpi-ft5406-1-4.19.120+git0+9da67d7329-r0-raspberrypi4-20200521111428.dtbo core-image-minimal-rasp

#linux #yocto

Hello Pankaj, Try below mentioned steps, Hope it helps you, (there my image was"core-image-base-raspberrypi3.rpi-sdimg" replace it by your image ) plug sd card to pc then $: lsblk $: sudo umount /dev/

#linux #yocto

You should have core-image-base-raspberrypi3.rpi-sdimg this should be written to to the SD card. Please check it by following below steps. Hope this help you. then follow below steps to write the imag

#linux #yocto

Hi, i dont have image with .rpi-sdimg i have image with core-image-minimal-raspberrypi4.wic.bz2 core-image-minimal-raspberrypi4.wic.bmap core-image-minimal-raspberrypi4.testdata.json core-image-minima

#linux #yocto

Please follow below steps to check the image. In build directory : to check the sdimage for installing on SD card. $: ls tmp/deploy/images/raspberrypi3/core-image-base-raspberrypi3.rpi-sdimg Check the

#linux #yocto

Siddhartha, you're confusing the issue here by giving inaccurate advice. The original command posted by Pankaj was nearly correct: `sudo dd if=core-image-minimal-raspberrypi4.wic.bz2 of=/dev/sdb`. The

#linux #yocto