Skip to content

New flow to determine control signals #803

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Oct 3, 2024
Merged

New flow to determine control signals #803

merged 2 commits into from
Oct 3, 2024

Conversation

chungshien-chai
Copy link
Contributor

This huge change reimplement the flow to determine control signals:

For multiple possible of control signal assignment:

  • The original flow decide which primitive is used based on the primitive sequence in the list
  • New flow decide which primitive is used based on the table-driven database which define the priority

@alaindargelas alaindargelas merged commit d885811 into main Oct 3, 2024
1 check passed
@alaindargelas alaindargelas deleted the yosys-control-signals branch October 3, 2024 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alaindargelas alaindargelas Awaiting requested review from alaindargelas

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@chungshien-chai @alaindargelas