Enable xilinx uarch for nextpnr-himbaechel #160
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmi2k
force-pushed
the
himbaechel-enable-xilinx-uarch
branch
3 times, most recently
from
3746d95 to
c53f15d
Compare
jmi2k
changed the title
|
I don't think I can support this at this stage. himbaechel-xilinx is right now mostly an experiment for internal PnR development rather than anything intended for end user purposes, although this may change in the future. |
|
Sounds reasonable, I'll keep these changes in my fork then. Feel free to close the PR or leave it as is. May I ask if there's a "mature" OSS toolchain for Xilinx devices? I've seen |
jmi2k
force-pushed
the
himbaechel-enable-xilinx-uarch
branch
from
c53f15d to
4f72e6a
Compare
jmi2k
force-pushed
the
himbaechel-enable-xilinx-uarch
branch
from
4f72e6a to
46291bc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables support for the Xilinx uarch in
nextpnr-himbaechel. It builds the required tools from f4pga/prjxray, but makes use of the prebuilt f4pga/prjxray-db chip database.I've tested these changes on the
linux-x64workflow and it adds the following build time and tarball size to it:NOTE: the increase in time may be caused by having to rebuild everything from scratch. I'll update this comment when I have better data.
There were some concerns raised on #85 about the increase in build time and tarball size, and I originally planned to keep these changes on a private fork, but I decided to send a PR for the record.
Depends on nextpnr#1509.
There is a problem with the installedFixed by adding missing line from the source (thanks Arch User Repository)fasm2framestool: it doesn't work properly for some reason I fail to understand at the time of writing.