rust-embedded
Add new section 'Supporting a new SoC'
vendors could opt to implement their PACs & HALs directly in
embassyrather than having them separate?
This is not required by embassy, and vendors typically prefer to keep their codebases in their own org/repo so they can control access to them, there's no doubts about ownership, etc.
Also: maybe ask dirbaio before you start suggesting that everyone shove their code in his project's repo?
Also: maybe ask dirbaio before you start suggesting that everyone shove their code in his project's repo?
sorry, this wasn't meant as a "hey, everyone should be doing this!" and more as a "is it the idea that this could/should be done?". sorry if that didn't come across like that
CC @Dirbaio
Sorry to have lost track — where are we with this? The commits are marked "outdated" but I don't know what that means: Github is hard.
I'd be happy to review and merge it if this is the time.
The commits are marked "outdated" but I don't know what that means: Github is hard.
@BartMassey: the comments are marked outdated because @mbrossard pushed a new commit on top, i.e. the comments are no longer attached to the newest commit. the PR itself is still marked as draft - @mbrossard: if you believe that the PR is ready for review could you please mark it as such?
@rursprung Ah, thanks. I'm used to folks force-pushing amended updates to PRs, which I don't believe does this?
@rursprung Ah, thanks. I'm used to folks force-pushing amended updates to PRs, which I don't believe does this?
it does the same (source: i very regularly force-push amended commits to open PRs)
Based on input from @diondokter, @jamesmunns, @adamgreig, @therealprof, @BartMassey and others at RustWeek Unconference.