I made some modification in the cmake modules to adjust for the linker issue below, but now I appear to have uncovered an issue with the static libraries which meta-clang generated under the SDK…

JPG/PNG have become builtin in gdk-pixbuf 2.42.x (other formats are still external). Signed-off-by: Alexander Kanavin <alex.kanavin@...> --- config.json | 4 ++-- 1 file changed, 2

Hello Anton, Am Mi, 5. Mai 2021, um 15:34, schrieb Anton Antonov: The boot files (kernel, kernel parameters, device tree overlays, ...) served by TFTP are bit-identical to the ones present at `/boot`

Hi Sven, No, I do not use any custom go-based recipe. BR, Quentin

Hi Quentin, Thanks for your reply. Did you have success with this technique when compiling a go-mod recipe where some of the go dependencies sit in private repos? The standard git fetcher works for

I don't know what exactly you mean by "whenever the Raspi is booting over the network". When a machine boots from network (i,e. using DHCP/BOOTP) then usually DHCP server points to, for example, a

From: Yann Dirson <yann@...> There is a known issue in mainline kernel making the machine unusable once a HDMI screen is plugged. This patch lets VOPB be alone to use the HDMI port and

From: Yann Dirson <yann@...> This patch provides "standard" and "tiny" BSP. There is still much work to be done in dispatching feature to individual scc files - the more boards we can

From: Yann Dirson <yann@...> The Wifi/BT support requires firmware, to be properly packaged; BT support itself is still buggy in mainline; audio jack requires a couple of

Hello all, to be able to diagnose my problem, I worked on enabling uart console access to my Raspberry Pi 4B. It seems the Raspberry Pi puts `8250.nr_uarts=0` in the linux kernel cmdline whenever

All the libraries are under the SDK here: -L/disk0/scratch/smonsees/sbcbSTD_SDK/limws/3.0.4/sysroots/corei7-64-poky-linux/usr/lib I need the DRM libraries to be picked up correctly,

Khem: I only have the following libraries present for these: libclang.so libclang.so.9 libdrm_intel.so libdrm_intel.so.1 libdrm_intel.so.1.0.0 libdrm.so libdrm.so.2 libdrm.so.2.4.0

granted, that Q was a bit vague ... based on a suggestion of richard's, i was going to do an "audit" of OE/YP layers to see the effect of doing a particular minor cleanup, but it's not clear

The following code is an effective workaround. It must be added after the core-image is inherited. python () { pseudo_ignore_paths = d.getVar('PSEUDO_IGNORE_PATHS') result = ','.join([x for

I was attempting an image build with Yocto Hardknott, and I ran into a chown problem during do_rootfs(). I traced it down to ${WORKDIR}/intercept_scripts showing up in the PSEUDO_IGNORE_PATHS

Helllo Robert, I don't have an context in the email you are referring to. Can you include it please? Supported will mean different things to different people. -Armin

the cmd seems to pass --sysroot correctly so can you search in SDK sysroot if you have libclang.a libdrm_intel.a and libdrm.a ? On Tue, May 4, 2021 at 3:20 PM Monsees, Steven C (US) via

We have discussed extending it but we currently only have the funding for the originally planned 2 years. Discussions are continuing but since we do all  agree that the next LTS will start then, we

Yes, LLVM & Clang…

(sorry, previous answer _is_ empty, wrong button) Hm, good catch, I ended up not activating the AP6356S in this first patch, since it would be non-functional without the proper firmware, and that one