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.

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

intel_alm: drop quartus support #4367

Merged
merged 1 commit into from
May 21, 2024
Merged

Conversation

Ravenslofty
Copy link
Collaborator

I have some spare cycles to work on this, so let's get some things out of the way while I can.

The biggest issue with supporting Quartus is that it imposes awkward requirements on memories that cannot easily be satisfied:

  • memories must be grouped together with "logical RAM names", which is incredibly unclear and not very helpful.
  • the Quartus cells have parameters to support memory initialisation, but it ignores them, forcing you to use their proprietary .mif format (formats like .hex get converted to .mif, so .mif might as well be used directly). Yosys does not have the infrastructure to output a bunch of files like this.

This means that Arria V and Cyclone 10GX support gets removed too, but with no easy way to test for regressions, they're extremely vulnerable to bitrot, and I'd rather explicitly remove support than let it quietly break.

@Ravenslofty Ravenslofty force-pushed the lofty/intel_alm-drop-quartus branch from 5767222 to 8cc9aa7 Compare May 3, 2024 10:32
@whitequark
Copy link
Member

whitequark commented May 3, 2024

  • Yosys does not have the infrastructure to output a bunch of files like this.

This is actually something we've discussed on a JF a few months ago (see the notes) and it's something I'm still interested in. There is some support available right now in write_verilog but I think it might not be enough for Quartus.

@nakengelhardt nakengelhardt merged commit 24f9329 into main May 21, 2024
35 checks passed
@nakengelhardt nakengelhardt deleted the lofty/intel_alm-drop-quartus branch May 21, 2024 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants