Merge activities with upstream

[unbtorsten]

This issue is a reminder to regularly review code and

• push tested code to upstream projects where possible.
• separate i) system requirements (readily available from upstream), ii) customization of upstream tools (make setup), and iii) minimum working examples (e.g. make blinky) whenever possible

For further details see #18 (comment)

[unbtorsten]

@hansfbaier, @jrrk2, @rwhitby et al.

After talking with @mithro, I advocate for merging the activity in this organization and its repositories entirely with F4PGA (formerly 'SymbiFlow'), cf. https://github.com/f4pga/f4pga. In fact, this is where I will place my focus as we are moving forward.

I believe that the code of this repo has its place in https://github.com/chipsalliance/f4pga-examples, anything related to setting up tools has a place in https://github.com/chipsalliance/f4pga-docs. Discussions of all sorts of related aspects take place in #f4pga's slack channel at https://slack-invite.chipsalliance.org/

[rwhitby]

I'm ok with that, but the slack link didn't work for me - it asks for a workspace URL.

[hansfbaier]

f4pga-example seem to be f4pga toolchain only. Do they accept nextpnr-xilinx examples?

[unbtorsten]

I'm ok with that, but the slack link didn't work for me - it asks for a workspace URL.

I updated the link: https://slack-invite.chipsalliance.org/

[unbtorsten]

f4pga-example seem to be f4pga toolchain only. Do they accept nextpnr-xilinx examples?

Wouldn't that go directly to https://github.com/gatecat/nextpnr-xilinx/tree/xilinx-upstream/xilinx/examples ? Either way, @gatecat may be able to answer that question for you.

[rwhitby]

I'm ok with that, but the slack link didn't work for me - it asks for a workspace URL.

I updated the link: https://chipsalliance.slack.com/

That doesn't seem to be a publicly accessible server? Is an invite required?

[unbtorsten]

That doesn't seem to be a publicly accessible server? Is an invite required?

Sorry about that.. yes, here is the link: https://slack-invite.chipsalliance.org/

[jrrk2]

It makes sense to not duplicate effort, however the F4FPGA(Symbiflow) flow has a lot more steps in it than the nextpnr flow, starting from the same prjxray-db database. The conversion to symbiflow doesn't actually work for Kintex7 at the moment, possibly because the prjxray-db is incomplete.