AFAIK, passing arguments from a python function to a shell function is not allowed

#bitbake #yocto

It would appear that some or all of this patch is unnecessary. OE-core 166bb89f6d97495b6522786182b4f9623acd7ff4 implements part of this patch, which makes me think it's working there without any chang

I haven't, but it's on my radar to look at as it seems like it could be pretty useful. If you look into it, please share your findings!

Disables debuginfod when using MingGW. This feature brings in unbuildable dependencies and can't be used. Signed-off-by: Joshua Watt <JPEWhacker@...> --- conf/machine-sdk/include/mingw32-common.

It might be easier to manually enable the service with a symbolic link instead of using systemd.bbclass with something like: do_install() { install -Dm 755 ${D}${systemd_unitdir}/system/multi-user.tar

Fixes the MinGW builds for zstd Signed-off-by: Joshua Watt <JPEWhacker@...> --- recipes-extended/zstd/zstd_%.bbappend | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 recipes-extended/z

Is there some PROVIDES that this should have? How will recipes pull it in as a dependency? Probably don't need this comment?

In general, it seems like a lot of these changes should be in the upstream recipes, not the meta-rockchip bbappends. Also, the things that do belong in this layer need proper variable overrides to kee

Very good. TF-A should work "out of the box" in meta-rockchip, so I think changing it's baudrate to 1500000 makes sense at this point (at least until u-boot can pass the DTB) Please add Upstream-Statu

Ah, I was referring to the DTB used by the Kernel (which u-boot can switch), not the DTB used by u-boot itself (which AFAIK is compiled into u-boot and cannot be changed). > >> >> >> >> >> >

FWIW, I'd rather u-boot could automatcially detect what variant of the board it's running on and do the right thing (usually, just selecting the proper DTB from the FIT image). The only reason I did n

You might try splitting it up with two images; one that makes your CPIO and one that makes the wic image. Since the wic image (presumably?) doesn't even have the rootfs specified, it probably doesn't

Splits out the three variants of the rock-pi-4 (A, B & C) into their own machines. Unfortunately, it is not possible to have a single machine that works for all three, as there isn't any known ways fo

Ya, we can keep the old machine around for the old kernels

Ya, I saw that. We should probably remove the .patch file also.

Upstream OE Core has moved to Kernel 5.10 which fixed this problem, so remove the patch for 5.8 Signed-off-by: Joshua Watt <JPEWhacker@...> --- ...-resolve-supply-after-creating-regul.patch | 53

Splits out the three variants of the rock-pi-4 (A, B & C) into their own machines. Unfortunately, it is not possible to have a single machine that works for all three, as there isn't any known ways fo

When I use `linux-yocto-dev` as the kernel provider, it works just fine (in fact, I can't seem to find the commit that *fixes* the problem there....), so I think 5.10 will be OK? Is there something el

Fixes the serial port output stopping mid way through the boot process by reverting the kernel commit that caused it. Signed-off-by: Joshua Watt <JPEWhacker@...> --- ...-resolve-supply-after-cre

This means the recipe is having host contamination (where the UID of the user doing the build is leaking into the file system).