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

Thanks kapllaj. Yes I use imx6ull, I've looked those config files, nothing set to run 4.19. I setup PREFERRED_PROVIDER_virtual/kernel = "linux-yocto", I have to say, it has been running for a year

Hi, it actually shouldn't be that hard to set the kernel. IMX_DEFAULT_KERNEL is a variable that sets the kernel name (the recipe) and not the version. I don't know on which yocto version you are

Hi All, I'm trying to install the Tokbox library into the build, but the tar file is not getting extracted into the folder. Here is my recipe code, kindly please help me where I went

Thanks kapllaj, It has linux-imx and ${IMX_DEFAULT_KERNEL}, but I could not find what is defined for ${IMX_DEFAULT_KERNEL} I defined IMX_DEFAULT_KERNEL = "5.10.%" in local.conf, still download

Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-security/selinux/semodule-utils_3.0.bb | 7 ------- recipes-security/selinux/semodule-utils_3.1.bb | 7 +++++++ 2 files changed, 7

Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-security/selinux/selinux-gui_3.0.bb | 7 ------- recipes-security/selinux/selinux-gui_3.1.bb | 7 +++++++ 2 files changed, 7 insertions(+),

Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-security/selinux/selinux-sandbox_3.0.bb | 7 ------- recipes-security/selinux/selinux-sandbox_3.1.bb | 7 +++++++ 2 files changed, 7