@benklop, I am not so very experienced with Yocto distribution builds as of yet, but I will try to give you a good answer based on my current understanding. The short answer is that it still does use kernel bits and u-boot bits which were extracted and assembled from the Luckfox SDK. This took me a while to understand and was sorta painful, so I’m going to take the time to explain it for others:
Yocto builds Poky distributions with bitbake and has the concept of building up the system via ‘layers’ each of which contain various bitbake ‘recipes’ as .bb files. Layers can also modify and append recipes in underlying layers with .bbappend files. The repository contains only the meta-picocalc layer, but when you kick off the kas build, it will download and prepare the other layers which are defined in the kas build configuration here.
So the final list of recipes is built up through assembling everything defined in these layers, each of which comes from its own vendor. In this project it is:
(poky) → meta-arm → meta-rockchip → meta-rtlwifi → meta-rauc → meta-picocalc
The whole thing kicks off a build of the ‘picocalc-bundle’ recipe, and everything comes in as an enormous cascade of dependencies.
All the custom stuff required for the picocalc and the luckfox lyra including the kernel and u-boot customizations start with the recipes in the meta-picocalc-bsp-rockchip folder. This is where your question about the SDK stuff is relevant. The other folder of recipes in meta-picocalc-distro are related to assembling the Poky distribution and preparing the system images, and to my understanding none of these rely on anything special from Luckfox or Rockchip SDKs.
So, focusing on the kernel and u-boot which is where all the special vendor stuff is:
The kernel is built with this recipe which assembles the kernel source tree from the definition in SRC_URI. The base checkout is downloaded from @0xd61’s repo here. This repo contains an extract of the linux-6.1 kernel sources from the Luckfox SDK. The picocalc customizations and kernel configs are then applied.
The build of the u-boot is similar. The recipe again uses u-boot extracted from the Lyra SDK and contained in this repo. (Note the u-boot build also pulls down this repo from Rockchip that contains some sketchy x86-64 binaries that were the source of my frustration building on aarch64)
I havent personally invested time yet in understanding the extent that the luckfox kernel or u-boot are modified from mainline. I suspect that the need for downloading sketchy binaries could be removed from the u-boot build and I do plan to fix that, but further work could probably get u-boot working from upstream sources. The linux kernel I suspect is more challenging. I have extracted patchsets from vendor customized kernel sources before and done work to ease forward-porting, but I’m not sure I’m sufficiently motivated to do that kind of free work for Luckfox.