README specifies subset of SPI chips seen in the wild
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
Just a trace.
Here are the SPI chips observed in the wild to address/verify coherent [WP guarantees/statements in README](https://github.com/osresearch/heads/commit/73a3b6d08f6bab0b63a0ebaf97c70138bdade128#diff-04c6e90faac2675aa89e2176d2eec7d8R15) and move doc in heads-wiki altogether hereafter, not having duplicate to maintain and be clear on instructions to build, access CIs and documentation access altogether.
```
Bottom SPI chips (3):
"EN25QH64" "N25Q064..3E" "MX25L6436E/MX25L6445E/MX25L6465E/MX25L6473E"
Top SPI chips (2):
"MX25L3273E" "N25Q032..3E"
```
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 with the README statements linked from commit 73a3b6d and compare them with the listed top and bottom SPI chips. Update the documentation so the observed chips and WP guarantees are coherent, then move the relevant build, CI-access, and documentation instructions to heads-wiki without leaving duplicate guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100