Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider vendoring vpi_user.h #78

Open
ArcaneNibble opened this issue Mar 1, 2017 · 4 comments
Open

Consider vendoring vpi_user.h #78

ArcaneNibble opened this issue Mar 1, 2017 · 4 comments

Comments

@ArcaneNibble
Copy link
Collaborator

I don't want to have to install Icarus Verilog just to get this one header file.

@whitequark
Copy link
Collaborator

Well gpcosim is not useful without iverilog, is it?

@ArcaneNibble
Copy link
Collaborator Author

Theoretically you should be able to use another Verilog simulator along with gpcosim (e.g. a proprietary one). Not sure why exactly you would do that, but...

@whitequark
Copy link
Collaborator

whitequark commented Mar 1, 2017

iverilog's vpi_user.h's license (GPLv2+) is not compatible with openfpga's (LGPLv2.1+).

@ArcaneNibble
Copy link
Collaborator Author

@azonenberg and I discussed this IRL at DefCon and he mentioned that he isn't a huge fan of VPI and might consider a completely different interface for the cosimulation code. He mentioned that he has/will have something that just uses $fread and $fwrite on pipes as an example of one possible way to build a new cosimulation framework. The IRL discussion then spiraled into a discussion about whether the potential new framework would be used for cosimulation, mixed-language simulation, or both, and then the discussion turned into a bikeshed about what exactly needs to be expressible in a potential new framework. No conclusions were reached, but I'm just writing this down so that we can remember that this happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants