we’ve made changes in this area , this is correct. We made 1 change in LK for a ‘special’ case : if there is only 1 DTB appended to the kernel compressed Image, then LK should go ahead and use it without checking for board ID vs CDT data.
We have made this change for both DB410c and DB820c, btw.
The board-id mechanism is a non standard, non upstreamable solution, and it was causing issues for kernel developers working with mainline. We no longer have to use dtbTool to patch the DTB (and add the board-id).
However this change is an ‘addition’, and you can continue to use LK/dtbTool as before. Since we completely removed the qcom,board-id data, you have to add it back, but then everything should continue to work as before in your case.
We are also thinking about adding some level of support for DTS overlay in LK. What we are going to do is not clearly defined yet… but the need is there. E.g. we need mechanisms to support DTS overlay in LK to support various mezzanines… I suspect you could be interested by that too. The very first use case for us is support for various camera configs…