platforms/iq-x7181-evk/spinor: update product name to Hamoa_IOT.LE.0.0

[guanquan (GuanquanTian)]

Update product name from Hamoa_IOT.UBUN.1.0 to Hamoa_IOT.LE.0.0

APT team feedback that triggering Axiom jobs for Hamoa on meta-qcom 0.0 builds, are encountering an SP mismatch issue. Instead of the expected Hamao_IOT.LE.0.0, it is showing Hamao_IOT.UBUN.1.0.

For meta-qcom build, it will use the contents.xml. in file in qcom-ptool.

For ubuntu build, it will use this file：
https://github.com/qualcomm-linux/qcom-distro-images/blob/main/platform/hamoa-evk/contents.xml.in

[Dmitry Baryshkov (lumag)]

Why?

[guanquan (GuanquanTian)]

Hi Dmitry Baryshkov (@lumag) ,
APT team feedback that triggering Axiom jobs for Hamoa on mtea-qcom 0.0 builds, are encountering an SP mismatch issue.
Instead of the expected Hamao_IOT.LE.0.0, it is showing Hamao_IOT.UBUN.1.0.

[Dmitry Baryshkov (lumag)]

First of all, it's not Hamao, you have a typo. Second, qcom-ptool files are not tied to an SP or exact product. Ubuntu vs LE is irrelevant for the qcom-ptool point of view.

[guanquan (GuanquanTian)]

thanks, typo issue fixed. At present, during the compilation process of meta-qcom, qcom-ptool is used to generate contents.xml files, and the final product name in the contents.xml generated in meta-qcom build is Hamoa_IOT.UBUN.1.0. The APT team hopes that it is the correct Hamoa_IOT.LE.0.0 .

[Dmitry Baryshkov (lumag)]

thanks, typo issue fixed. At present, during the compilation process of meta-qcom, qcom-ptool is used to generate contents.xml files, and the final product name in the contents.xml generated in meta-qcom build is Hamoa_IOT.UBUN.1.0. The APT team hopes that it is the correct Hamoa_IOT.LE.0.0 .

But then the contents will be unsuitable for Ubuntu. And also all platforms report as 0.0, both for QLI 0.0 and QLI 2.0 branches. So, I don't think it is a correct fix. Please implement the fix on the distro side

[guanquan (GuanquanTian)]

For ubuntu build, it will use this file：
https://github.com/qualcomm-linux/qcom-distro-images/blob/main/platform/hamoa-evk/contents.xml.in

About all platforms report as 0.0, both for QLI 0.0 and QLI 2.0 branches.
Can we consider changing it to Hamoa_IOT. LE. x.0 ? Instead of writing a specific version.

[Shoudi Li (shoudil)]

thanks, typo issue fixed. At present, during the compilation process of meta-qcom, qcom-ptool is used to generate contents.xml files, and the final product name in the contents.xml generated in meta-qcom build is Hamoa_IOT.UBUN.1.0. The APT team hopes that it is the correct Hamoa_IOT.LE.0.0 .

But then the contents will be unsuitable for Ubuntu. And also all platforms report as 0.0, both for QLI 0.0 and QLI 2.0 branches. So, I don't think it is a correct fix. Please implement the fix on the distro side

Currently hamoa ubuntu don't consume the contents.xml.in from qcom-ptool due to the different image directory structure.
The structure on ubuntu is more clear.
qcom-ubuntu-iot-resolute-desktop-canonical.images/iq-x7181-evk$ tree -L 1
.
|-- nvme
|-- spinor
`-- ufs

[Dmitry Baryshkov (lumag)]

Currently hamoa ubuntu don't consume the contents.xml.in from qcom-ptool due to the different image directory structure.

That needs to be fixed. contents.xml for all distros should be generated here.

[Shoudi Li (shoudil)]

Currently hamoa ubuntu don't consume the contents.xml.in from qcom-ptool due to the different image directory structure.

That needs to be fixed. contents.xml for all distros should be generated here.

Add different contents.xml.in for diff distros or share one common contents.xml ? If we want to share contents.xml for different distros, then the image directory structure should be aligned.

[Dmitry Baryshkov (lumag)]

Currently hamoa ubuntu don't consume the contents.xml.in from qcom-ptool due to the different image directory structure.

That needs to be fixed. contents.xml for all distros should be generated here.

Add different contents.xml.in for diff distros or share one common contents.xml ? If we want to share contents.xml for different distros, then the image directory structure should be aligned.

Yes. Is it not?

[Shoudi Li (shoudil)]

Currently hamoa ubuntu don't consume the contents.xml.in from qcom-ptool due to the different image directory structure.

That needs to be fixed. contents.xml for all distros should be generated here.

Add different contents.xml.in for diff distros or share one common contents.xml ? If we want to share contents.xml for different distros, then the image directory structure should be aligned.

Yes. Is it not?

Not align currently, on ubuntu (qcom-distro-images repo), we organized image folder per storage types. and HLOS images are nearly shared across targets (dtb.bin/rootfs.img are common, efi.bin have diff sector size configuration between eMMC/NVMe and UFS).
qcom-ubuntu-iot-resolute-desktop-canonical.images/iq-x7181-evk$ tree -L 1
.
|-- nvme
|-- spinor
`-- ufs

Actually we also raised similar PR for meta-qcom, could you help review it ?
qualcomm-linux/meta-qcom#1736