-
Notifications
You must be signed in to change notification settings - Fork 58
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
Unexpected behaviour of Record.connect()
#257
Comments
The direction of |
This confuses me each time. Maybe there is a better name for |
As I've said on IRC earlier, IMO we should deprecate |
Inverting that doesn't make the difference. Here are the variants: https://github.com/akukulanski/nmigen_testcase The confussion cames from the ambiguity that a module's port with FANIN (sink) has FANOUT (source) from inside the module. That's what makes that
Agree! |
I remember it by considering how it is used in the CSR bus with OR-multiplexing: |
Hi,
We saw that
connect()
won't connect the input and output records, nevertheless the signals are connected if they are individually described. Is that an expected behaviour?Thanks,
@akukulanski, @andresdemski
The text was updated successfully, but these errors were encountered: