Clash can't represent 300 MHz exactly
Opened this issue · 1 comments
martijnbastiaan commented
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 commented
Slack discussion (can't figure out how to properly copy stuff..):
