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.

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

Clash can't represent 300 MHz exactly #2811

Open
martijnbastiaan opened this issue Sep 24, 2024 · 1 comment
Open

Clash can't represent 300 MHz exactly #2811

martijnbastiaan opened this issue Sep 24, 2024 · 1 comment

Comments

@martijnbastiaan
Copy link
Member

See: bittide/bittide-hardware#643

I don't think Bittide's case makes a particular strong case for changing anything. "Normal" projects don't care about a couple of PPMs clock differences. This might however prohibit writing multicycle path constraints.
@martijnbastiaan
Copy link
Member Author

Slack discussion (can't figure out how to properly copy stuff..):

Screenshot from 2024-09-24 15-41-43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@martijnbastiaan