TODO for MSI platforms (post merge needed work)
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
> @Tonux599 as known; Dasharo+Heads had bad press on MSI.
> From what I got (memory based, please correct me) from @zirblazer
> HCL is important (should be stated in board configs)
> - CPU needs to include IGPU otherwise support request will flow.
> - Documentation needs to exist for external initial flashing, rom hole doc, etc
> At bare minimum, expected to work HCL should point to Dasahro docs, in board configs.
> Thanks for this work @Tonux599. Not sure how to do this politically, but current dasahro+heads users will want to know existence of these test binaries, in today's Dasharo DUG terms, being a "rapid" release.
_Originally posted by @tlaurion in https://github.com/linuxboot/heads/issues/1995#issuecomment-3643551151_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MSI board configurations and the Dasharo documentation referenced by the issue, then compare the expected HCL and flashing guidance with current entries. Done means the board configs point to the expected HCL and documentation covers external initial flashing and the ROM hole.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, embedded-iot
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100