You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to add more info to flow/designs/src/*. At a minimum - ideally a link to the upstream project, the commit hash used to produce the .v, and ideally more info about how it was generated (e.g. what options were used). You should also import a copy of any license text and other attribution information, as most open source licenses require this.
[Really pleased to see you using Ibex as a benchmark for OpenROAD by the way - and looking forward to finding time to give the flow a go].
The text was updated successfully, but these errors were encountered:
Thanks for the feedback. I'll try to add this. Some designs needed to be "elaborated" using a different tool because Yosys doesn't currenty support system verilog so we may not be able to have it in it's original form.
But we should be able to provide trace-ability, license and information to how the verilog sources files were generated.
Information on commit hash, how it was produced etc is a huge improvement - thanks! I'm not a lawyer, but including the original license also seems like a big step forward there. Thanks for such a rapid turnaround.
It would be great to add more info to flow/designs/src/*. At a minimum - ideally a link to the upstream project, the commit hash used to produce the .v, and ideally more info about how it was generated (e.g. what options were used). You should also import a copy of any license text and other attribution information, as most open source licenses require this.
[Really pleased to see you using Ibex as a benchmark for OpenROAD by the way - and looking forward to finding time to give the flow a go].
The text was updated successfully, but these errors were encountered: