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
One reason I've hesitated to merge #40 so far is that I think the oMigen conventions for CDC primitives are a bit annoying. I think a better situation than the current one would be:
Instead of arguments named domain, idomain, rdomain, etc, which only allow a single letter for domain designation, use domain, i_domain, r_domain, pll_domain, etc.
All modules which are likely to be transformed with DomainRenamer right after creation should allow changing the domain names through arguments. Notably this would include AsyncFIFO, which is probably responsible for most uses of DomainRenamer, but all other CDC primitives as well. Non-CDC modules may or may not allow that depending on intended use.
Comment by whitequark Thursday Sep 12, 2019 at 20:08 GMT
Since nMigen uses domain and not cd everywhere in the public API, I changed the convention slightly to match that, see original comment.
I've adjusted lib.cdc for this convention since it was not very invasive. I've also adjusted lib.fifo for this convention, and also have consistent naming elsewhere, but that is a larger diff, so I haven't committed it to master yet. Diff.
Issue by whitequark
Tuesday Jun 11, 2019 at 04:06 GMT
Originally opened as m-labs/nmigen#97
One reason I've hesitated to merge #40 so far is that I think the oMigen conventions for CDC primitives are a bit annoying. I think a better situation than the current one would be:
domain
,idomain
,rdomain
, etc, which only allow a single letter for domain designation, usedomain
,i_domain
,r_domain
,pll_domain
, etc.DomainRenamer
right after creation should allow changing the domain names through arguments. Notably this would includeAsyncFIFO
, which is probably responsible for most uses ofDomainRenamer
, but all other CDC primitives as well. Non-CDC modules may or may not allow that depending on intended use.Thoughts? @sbourdeauducq @jordens @Wren6991
The text was updated successfully, but these errors were encountered: