Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Find common location for machine specific partitioning related data #69

Open
ricardosalveti opened this issue Nov 13, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@ricardosalveti
Copy link
Contributor

Follow up from #67 (comment), we should have a dedicated repository for the partitioning related data that is consumed by meta-qcom-hwe but not hosted by the layers.

This is so we can start sharing with other common distributions (e.g. debian) later on.

@lumag
Copy link
Contributor

lumag commented Nov 15, 2024

As a note, we have been using https://git.codelinaro.org/linaro/qcomlt/db-boot-tools to contain data for supported devkits. Consider using that repo and using merge requests to provide data for newer boards.

@ndechesne
Copy link
Contributor

We are currently looking into that. In meta-qcom-hwe we've been using an intermediate file format (partition.conf) instead of the XML files. We are planning to have a standalone repo to host these files outside of meta-qcom-hwe. we probably want to host it on a qualcomm github repo. let me think about that.

@lumag
Copy link
Contributor

lumag commented Nov 18, 2024

We settled on using CLO repo as this allowed us to use build artifacts in rescue package generation. If you switch to any other location, please pull in all boards definitions from the repo I have pointed to.

What is the benefit of using non-structured, non-verifiable file format?

@ndechesne
Copy link
Contributor

yes, the distribution of prebuilt binary/rescue package is important, I am aware. For the additional/alternate file format, I am not sure why it was created, and I will check. It does not seem very useful, especially since the tool that converts to XML is not doing much processing, I will investigate more on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

3 participants