Is it INIT_MANAGER = " sysvinit" , or INIT_MANAGER = "sysvinit" (no blank at the beginning)? Thank you, Zee _______ <sayinswapna@...> wrote:

Thanks Robert and Raj!! I am using Yocto 3.1 Dunfell release. You are right about the .bbappend file. Changed the name in the overlay to new-ver.bbappend and no longer see the warning. Tried setting

Why do I (always) point out the obvious? And I do need... Geniuses are not meant to fix The World to understand them!? Geniuses should understand The World (and act properly)! Extras to geniality,

Hi Quentin, obviously I didn't read that page carefully enough. Sorry for the noise and thanks for the hint. Cheers, Manuel Am Fr, 28. Mai 2021, um 11:35, schrieb Quentin Schulz:

Hi Manuel, There is an example in the commit you sent, so I would say: SSTATE_MIRRORS ?= " \ file://.* http://someserver.tld/share/sstate/PATH;user=username:password;downloadfilename=PATH

Hello all, to speed up builds, we would like to make the CI generated sstate-cache available via internet. Due to IP concerns, we don't want to make it publically available but for authenticated

zephyr can be build for 'acrn' with following configuration: MACHINE = "intel-x86-64" ZEPHYR_BOARD = "acrn" Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- conf/machine/acrn.conf | 9

User need to specify board value to ZEPHYR_BOARD in local.conf ZEPHYR_BOARD = "minnowboard" By default it set to MinnowBoard Max 'minnowboard' Currently 32-bit supported boards: * up_squared_32 *

With zephyr v2.5.0, EFI binary support has been added for x86 board (64-bit mode). To achieve this, an python tool[1] has been added to convert zephyr ELF file into an EFI appliable. But currently

User need to specify board value to ZEPHYR_BOARD in local.conf ZEPHYR_BOARD = "ehl_crb" By default it set to Elkhart Lake CRB 'ehl_crb' Currently 64-bit supported boards: * up_squared *

V2.6.0-rc1 patch is not merged as it is pre-release. Lets wait for stable release. Could you please rebase these patches for v2.5.0 latest master ? Regards, Naveen

Been trying added a uboot script to my fitImage ( in hardknott) Looks like the routine fiitmage_emit_section_boot_scrip Has not updated it syntax for node name or hash node Still using’@’

Please find out which layer is adding this bbappend you could use bitbake-layers show-appends sysvinit It seems recipe version is newer perhaps and the bbappend is still made for older recipe, these

it will depend on release, if you are on 3.0+ then yes single setting will work, older releases would mean above is needed.

as i recall, all of the above can be replaced by a single assignment to the INIT_MANAGER variable. rday

Hello Yocto team: I just started with yocto and would like to know the process for switching the init manager from systemd to sysvinit. I tried this options in config file VIRTUAL-RUNTIME_init_manager

Hello Folks, In order to continue to develop my: https://github.com/ZoranStojsavljevic/bbb-yocto And advance to yocto hardknott, I did the temporary moves: Cloned both jumpnow repos to my github

maybe take a look at some of the work toradex has done, maybe in their torizon tree you can find some creative ways

Hi everyone. I am trying to setup a Package Feed with signed ipk packages. For this, I first set up the key pair on my build host. This is the result of "$ gpg --list-keys" :

Has anyone seen suck an animal before, and if not, how hard would it be to launch a container, then get the output to install like a normal recipe does?