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

Lacking usage documentation #2

Open
3 tasks
calebccff opened this issue Jan 28, 2025 · 1 comment
Open
3 tasks

Lacking usage documentation #2

calebccff opened this issue Jan 28, 2025 · 1 comment

Comments

@calebccff
Copy link

Heya! I'm really excited to see this repo, and in general more public resources from Qualcomm to make it easier for users to tinker with their devices.

From having a brief look through the repository, there are some useful scripts and config, it's nice that this is actively being used by meta-qcom-hwe and not just a code drop.

However it's hard to grasp how I might go about adding support for another board (e.g. the RB5, or perhaps some production device).

It would be great to see the README be expanded to explain:

  • the config format / how it works
  • the various XML files that are generated and consumed by the tools in this repo (or by e.g. qdl)
  • a description and example usage of each of the tools in the repo (what they do, when/how you might use msp.py for example)

I think these tools could become extremely useful for the community. There are a number of production smartphones which have EDL mode available which are also supported by U-Boot and Linux. With these tools it ought to be possible to produce a partition table much closer to the rb3gen2, where we could have leave lun 0 free so that it could be re-partitions at will (currently many devices put important partitions there and will refuse to boot if the partitions are missing). So I'm really excited to see what will be possible thanks to this!

@ndechesne
Copy link
Contributor

hey. thanks for starting the discussion. We are also trying to figure out how we are going to deal with that. The one thing we know is that we want a centralized location to host partition configurations for QCOM based dev kits, reference boards, ... instead of having these partition configuration scattered in each project (meta-qcom-hwe has its own, Ubuntu for RB3G2 has their own, ..).

It looks like what was done by Linaro (db-boot-tool), for an obivous reason ;-)

We are very much open into what we should do with it. But we need to make it useful!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants