From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> --- recipes-framework/tensorflow/keras_2.6.0.bb | 2 +-

From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> --- recipes-installer/python3-dasbus/python3-dasbus_1.6.bb | 2 +-

Hi, Yes. Likely you just need to do: $ MACHINE=qemux86-64 bitbake your-image with the right configuration and then run it in docker. See below. There are at least three options depending on what

Hi Mihir I could reproduce your issue. I believe I built the system in the same way you did. An issue is that the kernel is built with CONFIG_SOUND=m CONFIG_SND=m ...plus other sound modules, but

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Bruce, Diane, Jate, Joshua, Márton, Michael, Randy, Richard, Saul, Stephen, Steve, Tim, Trevor ARs: -

<matthias.klein@...> wrote: Presumably, the kernel recipe you are using inherits kernel-yocto, and that whatever recipe is using a defconfig isn't also putting the kernel-cache into the

Hi all. I have this doubt. Is it possible the make a toolchain which can produce the same app for host machine? I try to explain my think. I produced an app for imx6dlsabresd with qt-5.6.2 using

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E:

Hello, I would like to create a linux-%.bbappend file and add the following to it, for example: KERNEL_FEATURES:append = " features/overlayfs/overlayfs.scc". Works also for all kernels

Hi Peter, After entering "aplay -l" I got message "aplay: device_list:274 : no soundcards found...". I am using virtual machine: VMware workstation with ubuntu 20.4.3 as a Linux host machine. Running

Check available sound cards in your system. 'aplay -L' It seems you have no suitable default one for speaker-test to use. If you have sound cards in your machine and want to point out

recently tried to add ALSA support to core-image-minimal . by adding following lines into local.conf: MACHINE_FEATURES+="alsa" DISTRO_FEATURES+="alsa" CORE_IMAGE_EXTRA_INSTALL+="alsa-utils" but got

I’m testing migrating one of my dunfell builds to master in anticipation of the upcoming LTS, and there is a difference in how packages are populated into deploy that is causing me problems. My

Hi JH, This would typically mean that you are actually connected to a wifi network but the interface did not receive a DHCP lease for the IP address. the 169.254. is local IPv4 IP address which the

Hi, I have tested the state mirror locally with my own http mirror and it works perfectly. There are no problems with the concurrent connections. I'm more sure that the root cause is some

<trevor.gamblin@...> wrote: Merged as 52d5f76f54eac384f9480dffe96df089d9ee8f33 in OE-core

Personally, I think where the checksums are present, we should check them regardless of url type though. I think I have an open bug related to this and the uninative fetching. Cheers, Richard

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> This commit just adds some documentation on how to use the machine generation recipe. Signed-off-by: Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> Some of these recipes ended up overriding the ZEPHYR_MODULES we set elsewhere. As well, zephyr-lvgl tries to apply a patch we already

From: Eilís Ní Fhlannagáin <elizabeth.flanagan@...> Trying to handwrite all the machine defintions in zephyr would be an enormous task. This commit creates a patch to zephy which abuses