No release/tag

[lool]

Hi,

There was a recent change to pathnames to partition files in qcom-ptool that broke the reference Debian images. This didn't affect meta-qcom because it uses a sha to refer to a particular qcom-ptool commit.

Dmitry's suggestion was to use a sha for the Debian images, but I find this awkward, and I think we should have a place where we can document changes/news ongoing inside qcom-ptool, much like we'd do with qdl or other dependencies.

Could we have a 1.0 qcom-ptool tag / release? :-)

Thanks

[lumag]

It would be awkward too, since there can be several parallel branches targeting different QLI targets. Also what does particular release mean for example for RB1? Or for RB3 Gen2? I really think this is a rolling repo with no particular "releases".

[lool]

The current situation is awkward as it's not clear what partition requirements are expected by the boot firmware or the OS, yet somehow they must all align, but it's the same problem whether it's a git sha being referred to or a version number. The difference with proper tags/versions/releases is that we have a moment to broadcast that some changes have been implemented and to make corresponding downstream changes.

I guess I'm seeing this repo as the most logical place to host some definition of our boot contract between boot firmware and OS. I wish it gets updated if boot firmware is updated to new conventions, perhaps with backwards compatibility in mind or broadcasting the changes to OS implementations.

[ricardosalveti]

I guess I'm seeing this repo as the most logical place to host some definition of our boot contract between boot firmware and OS. I wish it gets updated if boot firmware is updated to new conventions, perhaps with backwards compatibility in mind or broadcasting the changes to OS implementations.

I think it is valid to set some sort of tag/release based on the boot firmware release used by qualcomm linux (as there is indeed a contract expectation), but I also understand that not every target here will be covered as part of qualcomm linux. At least a tag/release can contain its own changelog saying why certain changes were done (e.g. new partitions, etc).