Should we drop in a big commit and move the current logic to a meta-partner layer? I know we want to remove it from this layer, but we will have to add it all over again once we bring the latest bsp in a partner layer.

I think we can keep these removal commits and mimic them when we add these back to a partner layer.

The only issue is that most changes should later be applied at the same time, unless we break the removal into several commits (per logical blocks). I personally prefer with a big single commit, but fine with either way.

some more pieces to drop:

$ grep xlnx -r
meta-lmp-base/conf/distro/include/non-clangable.inc:OBJCOPY:pn-linux-lmp-xlnx:toolchain-clang = "${HOST_PREFIX}objcopy"
meta-lmp-base/conf/distro/include/non-clangable.inc:STRIP:pn-linux-lmp-xlnx:toolchain-clang = "${HOST_PREFIX}strip"
meta-lmp-base/conf/distro/include/non-clangable.inc:TOOLCHAIN:pn-u-boot-xlnx = "gcc"
meta-lmp-base/conf/distro/include/non-clangable.inc:# libmali-xlnx calls gcc directly on do_install
meta-lmp-base/conf/distro/include/non-clangable.inc:TOOLCHAIN:pn-libmali-xlnx = "gcc"
meta-lmp-bsp/recipes-kernel/linux/linux-lmp-xlnx_git.bb:KBRANCH = "xlnx_v5.15.y"

And also meta-lmp-bsp/dynamic-layers/xilinx-tools

Thanks José, I haven't realized xlnx is also a keyword

I prefer a huge commit, so I'm going to squash everything

updated