Port to Chisel5
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 6
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We should port the InterPRET to Chisel5. I guess this requires both FlexPRET and S4NOC to be ported first? @schoeberl, is there a plan for moving soc-comm to Chisel5?
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
Read the existing InterPRET, FlexPRET, S4NOC, and soc-comm implementations to map their dependencies and current Chisel usage. Confirm with maintainers whether Chisel5 migration is planned and which component should move first; done means the relevant components are ported and their existing behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100