| *** tpb <[email protected]> has joined #symbiflow | 00:00 | |
| *** bl0x <bl0x!~bastii@p200300d7a7171600754b14ef62887bad.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 268 seconds) | 02:50 | |
| *** bl0x <bl0x!~bastii@p200300d7a715b8006904829f8c9caa58.dip0.t-ipconnect.de> has joined #symbiflow | 02:51 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has quit IRC (Read error: Connection reset by peer) | 04:37 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has joined #symbiflow | 04:55 | |
| *** josfemova <[email protected]> has joined #symbiflow | 07:40 | |
| *** josfemova <[email protected]> has quit IRC (Quit: Connection closed) | 07:49 | |
| sf-slack | <josfemova> Hello! Just bought some eos-s3 devkits (sparkfun quicklogic thing+) with some other three people. It seems there are different ways to set up an environment based on which documentation you are following, I would like to know if right now the correct way is the "symbiflow-examples" way. That workflow uses yosys 0.9 if I'm correct. I checked and some of the Quicklogic changes to Yosys were merged after that version, | 08:02 |
|---|---|---|
| sf-slack | so I'm not sure if the future workflow will have breaking changes in respect to the current way of doing things. I also saw mainline Symbiflow already uses yosys 12 so I'm kind of lost here. | 08:02 |
| sf-slack | <pgielda> Symbiflow is being developed actively. Symbiflow examples targets a "stable" version | 11:06 |
| sf-slack | <pgielda> So depends what you want to do... | 11:07 |
| sf-slack | <mkurc> @josfemova Hi, The symbiflow-examples way is correct. However, there have been development for EOS-S3 support happening recently and we are currently working on upstreaming it. If you want to use a more up-to-date yosys version then you can grab the upstream one. The synthesis flow for EOS-S3 resides in a plugin which you have to build and install too from https://github.com/SymbiFlow/yosys-symbiflow-plugins. | 11:14 |
| sf-slack | <josfemova> Nice, Thanks for the info! | 16:33 |
| sf-slack | <xanjohns> @acomodi @mithro I've opened up a pull request here to demonstrate how a PAT would be used in common-config, as requested in this issue. Feedback would be appreciated so that we can either move forward creating the PAT or start looking into another approach. | 17:55 |
| sf-slack | <acomodi> Hi @xanjohns, I think we can proceed with the generation of the PAT, I guess only thing needed is the access to the `common-config-robot` to create said PAT | 17:57 |
| sf-slack | <xanjohns> Correct, I have already made the bot account, but I'm not sure what the best way is to get the information to an administrator to create and add a PAT as a secret. @acomodi | 17:59 |
| mithro | acomodi / mkurc: https://github.com/SymbiFlow/fpga-interchange-tests/issues/81 should be a pretty easy fix? | 18:55 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!