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

Module ports beyond io #101

Closed
grebe opened this issue Feb 13, 2016 · 3 comments
Closed

Module ports beyond io #101

grebe opened this issue Feb 13, 2016 · 3 comments

Comments

@grebe
Copy link
Contributor

grebe commented Feb 13, 2016

It is my understanding that firrtl doesn't care what input and output ports of a module are named. The current chisel3 frontend has a private variable called ports that is only clk, reset, and io.

I propose that we make this variable protected instead of private.

This will allow people to have input/output ports outside of the IO bundle, making chisel3 match firrtl more closely.

@aswaterman
Copy link
Member

Depending on the use case, #156 and/or #157 may satisfy the demand.

@chick
Copy link
Contributor

chick commented Feb 2, 2017

@grebe should this be open at this point

@ducky64
Copy link
Contributor

ducky64 commented Feb 2, 2017

Discussion should continue in #469 and #427

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

No branches or pull requests

4 participants