Yoctoproject

Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to show my journey trying to build a hello-qt application and reasons why I don't like Qt . As far as I can tell this is going to be a multi part blog post. Community not valued by the Qt Company Qt 5 was officially released on 19 December 2012 and on 31 August 2020 was the Qt 6 feature freeze so one would think the community prepares meta-qt6. But the Qt Company sufficiently pissed off well known and respected community members and contributors to meta-qt5 [1] so that it does not look like there will be community support for Qt 6 any time soon. [1] meta-qt5 is a community project outside of The Qt Company and it's a lot more stable and easier to maintain then the Qt 5 layer from Qt. The Qt Company decided to make their own meta-qt6 layer, but there are some concerns from the commun

Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives The goal of this blog post is to point out a well known and documented issue with kernel modules not ending up on the root file system which is likely overseen by people until they stumble over it.   Kernel module(s) So you created a brand new kernel module, or you just wanted to include all the kernel modules in the root file system, or just one of them. You reach out to the community mailing list or chat with something like this: I have MACHINE_EXTRA_RRECOMMENDS + = "kernel-modules" in my machine configuration. When I look into the rootfs I see no modules installed in /lib/modules/ $( uname -r ) . I get only a modules tarball in the deploy directory. I also tried MACHINE_EXTRA_RDEPENDS + = "kernel-modules" and it still does not work. What am I doing wrong? Check the Mega Manual If things d

Introduction This work is sponsored by Reliable Embedded Systems . You can find more information about our training/consulting services here . Objectives My favorite development setup is to have the boot loader load kernel/device tree over tftp and mount the rootfs over NFS. The first part does not work out of the box on a Raspberrypi 4 with meta-raspberrypi/dunfell since the default U-Boot (2020.01) does not yet support it. What to do in such a case? Interact with the community Report your problem I opened this issue at the meta-raspberrypi repo with that content: U-Boot does not seem to support networking on the Raspberry Pi 4 - 64 Bit Steps to reproduce the issue: U-Boot> setenv autoload no U-Boot> dhcp No ethernet found. U-Boot> ping 192.168.42.1 No ethernet found. ping failed; host 192.168.42.1 is not alive U-Boot> Describe the results you received: No ethernet found. Describe the results you expected: pong Additional information you deem important (e.