I've been looking to improve the introduction of new boards to the supported kernel for some time, and this takes us most of the way there. Now with a machine.conf and a defconfig you can create an initial working environment for BSP development with no manual/workaround steps.
When creating a new BSP there isn't always an upstream branch to validate SRCREVs against. Therefore, creating a new BSP required extra manipulations of the git repository, even though the branch for the build would be dynamically created. To fix this, provide a fallback to the 'standard' branch if WRMACHINE is not assigned a specific value for the given MACHINE. The fallback saved in KBRANCH, and represents the branch that we should build, even if no fallback is required. Some substeps of the recipe have been updated to use KBRANCH rather than enforcing MACHINE-KERNELTYPE. There will be one additional change to not track the SRCREV of wrs_meta as a fallback, but I wasn't able to get the standard branch tracking working, so I'm sending this as-is for now. I've tested this with my kernel development layer, and with the stock meta directories only. Either way, I was able to build and test a 'qemumips-variant' quickly. Cheers, Bruce Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: zedd/kernel Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel Thanks, Bruce Ashfield <bruce.ashfi...@windriver.com> --- Bruce Ashfield (2): linux-wrs: implement BSP bootstrapping via fallback branches linux-wrs: BSP bootstrap .../conf/distro/include/poky-default-revisions.inc | 2 +- meta/recipes-kernel/linux/linux-wrs_git.bb | 40 ++++++++++++++++---- 2 files changed, 33 insertions(+), 9 deletions(-) _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
