Skip to content

Add an RFC for InternalPort. #78

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

wanda-phi
Copy link
Member

@wanda-phi wanda-phi commented May 30, 2025

@whitequark whitequark added meta:nominated Nominated for discussion on the next relevant meeting area:core RFC affecting APIs in amaranth-lang/amaranth labels May 30, 2025
@whitequark
Copy link
Member

whitequark commented Jun 9, 2025

We have discussed this RFC on the 2025-06-09 weekly meeting. The disposition was to merge, resolving the unresolved questions as follows:

  • Using InternalPort with a DDRBuffer in simulation causes the buffer to elaborate to an unspecified glitch-free model driving the port triple.
  • Using InternalPort with a DDRBuffer in synthesis is forbidden. If a need to abstract over unknown implementations of DDR buffer exists for a component, this should be done by using io.DDRBuffer.signature in the component interface rather than using InternalPort or similar objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:core RFC affecting APIs in amaranth-lang/amaranth meta:nominated Nominated for discussion on the next relevant meeting
Development

Successfully merging this pull request may close these issues.

2 participants