Hi Paul Barker, No, ${WORKDIR}/tokbox directory is empty, it is not getting placed. I can only see it in the downloads directory. I'm Yocto Project Dunfell version. Thanks, Vijay Rakesh.

<vijayrakeshmunganda@...> wrote: Does the .tgz file get placed in ${WORKDIR} without being extracted? Also, which Yocto Project version/branch are you using? Thanks, -- Paul Barker Konsulko

Hi Jupiter, [...] [...] Not sure this will fly nicely (the kernel headers being older than your kernel). Otherwise ok. And here we have the winner :) You don't have a 5.10 linux-yocto recipe so

Hi Zoran, Thanks for the reply. The reason behind CMakeLists.txt does not appear is because tgz file is getting extracted into the source folder, it is empty when I checked. My recipe is unable to

Just maybe... This web pointer can help

Anyone, please suggest. Thanks, Vijay Rakesh

Thanks Quentin, here are results: $ bitbake -e virtual/kernel | grep -e

Hello everyone, I'm trying to improve the Yocto Project's license tracing based on a proof-of concept implementation of linking sources with SPDX headers to output files by Richard at

Hi Marek, Is it: A) Comes from master and is a problem on dunfell or B) it is reproducible on the master branch? Given that you said: I suspect it's A only. Right? What are your small

HI Randy, <randy.macleod@...> wrote: Yes this comes from master branch. BR, marek -- as simple and primitive as possible ------------------------------------------------- Marek Belisko -

Quite an opposite. It must be defined to be exported, and to appear in Module.symvers . If it is NOT defined as exported (EXPORT_SYMBOL, EXPORT_SYMBOL_GPL), it will behave as from your initial post,

Marek, Does this happen if you use the master branch? Hongxu, Any tips for Marek? ../Randy > -- # Randy MacLeod # Wind River Linux

If I think more... For driver development the Out Of (OOT) Tree driver is a must, and so far the most efficient way is to have native tool environment presence on the target, so the quick

Hello, I use yocto version 3.0.3 (zeus) and tried to install some node packages as described in the yocto manual [1]. I experienced that manipulating a sha512 checksum in a package-lock.json file does

No, no... I did not mean in the makefile to change m to y. Please, maybe you can try to set your makefile to lookalike as these

Hi Zoran, Thanks, I modified the Makefile: obj-m := huawei_cdc_ncm.o Kconfig (obj-y := huawei_cdc_ncm.o) SRC := $(shell pwd) all: $(MAKE) -C $(KERNEL_SRC) M=$(SRC) modules_install: $(MAKE) -C

Hello Zoltan, Please, try to set Kconfig (obj-y := huawei_cdc_ncm.o) to y, I guess 99.9% that the kernel compilation (actually, driver compilation) will pass. I think YOCTO (recipe) behaves

What would cause this “opkg” to not pull in these components ?, and how do I ensure “opkg” can find these components : “inetutils-rsh” and “inetutils-rshd” ? Using “zeus”…,

Hi Folks, I bitbaked a Huawei E3372h driver into the distro with this recipe file: SUMMARY = "Huawei Stick kernel module" LICENSE = "CLOSED" inherit module SRC_URI = "file://Makefile \

Hi, So we can stop half guessing and help you can you give us the output of: bitbake -e virtual/kernel | grep -e "^PREFERRED_PROVIDER_" bitbake -e virtual/kernel | grep -e