forked from pulp-platform/pulp_cluster
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'update-cluster-interconnect-rebase-balasr' into 'master'
Update pulp_cluster interconnect # **Merge queue** After !56, this branch root source # **Overview** This PR upgrades pulp_cluster interconnects aligning with the new version recently introduced in [pulp-open](pulp-platform/pulp#49) (still not in master). # **Checklist** - [x] Bump version of several cluster IPs (`pulp_cluster`, `icache_mp_128_pf`, `hier-icache`, `cluster_peripherals`, `cluster_interconnect`, `mchan`) - [x] Bump `axi` to v0.28.0 - [x] Glue the updated IP with control_pulp hw - [x] Update CHANGELOG with more detailed information on IP bump versions and cluster interconnect changes - [x] Adopt novel AXI clock domain crossing setup in the cluster-soc communication (required `axi >= v0.28.0`) - [x] Adopt the use of 32-bit private icache to prevent issues arisen with Mobilenet workload in pulp-open (test still to be included here) # **Fixes** Fixes pulp-platform#22 # **Notes** ~~- I wasn't able to properly `git subtree pull` the `axi` repo. A lot of (unexpected) conflicts arised. To shorten the process, I removed the axi IP directory and called `git subtree add` again. This should not have implications on the history itself. Yet it is a bit of a ugly solution, but I hope non-blocking for the merge. Otherwise, we can figure out alternatives by rebasing~~ ~~- I was able to bump some IPs without the `--squash` option only, perhaps because they were added in that flatten way originally as well. Again, hope this is not a blocking issue~~ **NB** Previous notes were fixed by workarounding `git subtree pull` command See merge request balasr/control-pulp!67
- Loading branch information
Showing
12 changed files
with
1,237 additions
and
1,293 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.