Organizing Custom Builds, Recommended Practices?
Posted: Thu Feb 10, 2022 2:58 am
- COTS board with MP support, just tweak some #defines
- Same as (1) plus pre-compiled modules
- COTS board without MP support, but similar to an existing board / processor port
- My own board, but designed to be similar to an existing board / processor port
- COTS board, vendor provided MP library patches and modified MP standard PICO definition
Or like I was trying to do, keep one version of the MP repo?
What's the tipping point where a pull request should be made to add a new board vs keeping it local? When I built my own MP board for an experiment, it was obvious nobody would need it. But when I see a vendor with a somewhat well-known board distributing MP support as diff patches instead of putting it to MP proper via a pull request, I wonder what the threshold is for this.