15:43 <tortoise> Looking for some guidance on two fronts. The overview is that I'm trying to use meta-meson with radxa-zero board. I've submitted a PR but its a bit broken at the moment since the radxa-zero.dts isn't in the kernel until version 5.16 and meta-meson is fetching and building a 5.15 kernel.

15:45 <tortoise> First front would be quick fix using meta-meson's current 5.15 tree. I was wondering how I would cherry-pick this commit https://github.com/torvalds/linux/commit/26d1400f7457cdca3f1f86a7cccb0167f96e2edf

15:45 <tortoise> Should I just put a patch file in the recipes-kernel/linux directory.

15:45 <tortoise> I see there are many patches in recipes-kernel/linux/linux-meson64- 5.4 but recipes-kernel/linux/linux-meson64-5.15 has only the defconfig.

15:47 <tortoise> Second front, should I consider updating meta-meson's kernel version to something newer for the purpose of having the upstream meta-meson layer with radxa-zero support? If so, which version is preferred say 5.19 or should it be updated to a 6.x ?

15:54 <tortoise> scratch the first part about patching 5.15, seems very straightforward to do. But still interested in if updating the kernel is good idea and if I can help update meta-meson

19:53 <tortoise> feel good about the PR with cherry picked radxa-zero device tree patch. with the exception that I have no idea what this file does

19:53 <tortoise> recipes-bsp/trusted-firmware-a/amlogic-boot-fip.bb

19:53 <tortoise> and if adding radxa-zero to that was kosher or not

21:12 <tortoise> I think I understand it a bit now, and well there is a radxa-zero makefile in the commit referenced by the recipe

21:12 <tortoise> https://github.com/LibreELEC/amlogic-boot-fip/commit/7ff0004e0e4d261ba81334a2f46302bd06704aca

21:12 <tortoise> I take it these binarys are necessary for getting from the amlogic (or maybe it's ARM) hardcoded/ROM boot stage up to the mainline u-boot

23:02 <tortoise> I found a bug in a recipe, where it assumes that do_configure has run before do_populate_lic ... which doesn't appear to be true, at least on the first run of the recipe. Is there a way to specify dependencies between tasks, or re-order them?

23:02 <tortoise> sorry wrong channel, meant for #yocto not #linux-amlogic