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: Add support for Cyclone V internal oscillator #530

Merged
merged 1 commit into from Nov 6, 2020

Conversation

kbeckmann
Copy link
Contributor

When using the default clock "cyclonev_oscillator" on Cyclone V devices, the internal oscillator will be used.

@codecov
Copy link

codecov bot commented Nov 6, 2020

Codecov Report

Merging #530 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #530   +/-   ##
=======================================
  Coverage   81.33%   81.33%           
=======================================
  Files          49       49           
  Lines        6461     6461           
  Branches     1289     1289           
=======================================
  Hits         5255     5255           
+ Misses       1016     1015    -1     
- Partials      190      191    +1     
Impacted Files Coverage Δ
nmigen/build/run.py 22.05% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bde37fe...440791c. Read the comment docs.

nmigen/vendor/intel.py Outdated Show resolved Hide resolved
nmigen/vendor/intel.py Outdated Show resolved Hide resolved
When using the default clock "cyclonev_oscillator" on Cyclone V devices,
the internal oscillator will be used.
@whitequark whitequark merged commit ebbdac9 into amaranth-lang:master Nov 6, 2020
@whitequark
Copy link
Member

Thanks!

@kbeckmann kbeckmann deleted the cyclonev_oscillator branch November 6, 2020 11:41
@kbeckmann
Copy link
Contributor Author

Thanks for the quick feedback, happy to contribute!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants