This is a copy of the issue reported under IPApproX here.
I'm from EnICS labs in Bar-Ilan university, Israel. We've recently started using Pulpino, and wanted some sort of Hardware Configuration Management system, and the features in IPApproX documentation seem to fit exactly to our needs.
When I started playing around with the code, I found out that project Pulpino is using branch verilator. update-ips.py script in Pulpino is specifically cloning this branch.
It looks like branch verilator is not actively maintained and does not support the more advanced features, specifically hierarchical flow, which makes it useless for our needs.
Can you tell, what it takes in order for us to use Pulpino with master of IPApproX?
This is a copy of the issue reported under IPApproX here.
I'm from EnICS labs in Bar-Ilan university, Israel. We've recently started using Pulpino, and wanted some sort of Hardware Configuration Management system, and the features in IPApproX documentation seem to fit exactly to our needs.
When I started playing around with the code, I found out that project Pulpino is using branch verilator. update-ips.py script in Pulpino is specifically cloning this branch.
It looks like branch verilator is not actively maintained and does not support the more advanced features, specifically hierarchical flow, which makes it useless for our needs.
Can you tell, what it takes in order for us to use Pulpino with master of IPApproX?
Thank you, noytzach