meta-xilinx Kirkstone mitigations

This is a proposal for Yocto kirkstone improvements to https://github.com/Xilinx/meta-xilinx/tree/kirkstone-next which should make the branch better compatible with Yocto Project's kirkstone (LTS) release.

Although Xilinx recommends using the Yocto Project meta-xilinx mailing list for submitting patches, the https://git.yoctoproject.org/meta-xilinx/log/?h=kirkstone-next is lagging the Xilinx Github version of meta-xilinx repository, namely the latter contains Xilinx release 2022.2 whereas the former 2022.1. Therefore I have opted to open this pull request against the GitHub repository instead.

Apr 28 '23 09:04 nikomauno

@nikomauno Maybe you can send the patches to the meta-xilinx mailing list? It would be good if this could be merged.

Jun 12 '23 09:06 luckyfunky

@nikomauno Maybe you can send the patches to the meta-xilinx mailing list? It would be good if this could be merged.

Thanks - unfortunately there was a remarkable (390 commit) deviation between YP's and Github's meta-xilinx/kirkstone-next branches, which is why I originally chose to proceed with the latter which supported also 2022.2 in addition to 2022.1.

From Mark's answer I assume the YP's kirkstone-next branch is not going to get updated: https://lists.yoctoproject.org/g/meta-xilinx/topic/94568772#5241

Jun 13 '23 11:06 nikomauno