Many boards fail to boot with V0.3 release.

[vkraleti]

Observing bootup issues on many boards after migrating to qcom-dtb-metadata v0.3 release even after updating the compatible strings as recommended in 48629e8.

Please refer to qualcomm-linux/meta-qcom#1673 for exact changes made and suggest if anything is incorrect.

Sample logs from meta-qcom CI jobs where this issues are seen:
iq-9075-evk failed to boot: https://github.com/qualcomm-linux/meta-qcom/actions/runs/22671764891/job/65717535475

rb3gen2 also failed to boot: https://github.com/qualcomm-linux/meta-qcom/actions/runs/22671764891/job/65717535542

[amrianan]

issue: https://github.com/qualcomm-linux/meta-qcom/actions/runs/22671764891/job/65717535542
in below case: the soc-id is 0x1F2 and revision is 0x10000.

Hence from metadata, sub-string qcs6490 should be part of the bucket list. However, this is not added:

this is bucket list: {qcs6490 is missing}
qcom, iot, subtype5, emmc, 4GB+, softsku0,

This is metadata:
qcs6490 {
msm-id = <0x000001f2>;
};
ref- https://github.com/qualcomm-linux/qcom-dtb-metadata/blob/main/qcom-metadata.dts#L35C1-L37C5

UEFI has not added qcs6490 into the bucket. This seems to be due latest change in uefi which has not yet promoted.
UEFI would be still look for soc-id name along with revision.