<sf-slack>
<timo.callahan> @mithro , I might need permission on foss-fpga-tools-kokoro in order to use the image "opt-xilinx--2018-01-10". Or else I'm doing something else wrong. @litghost , I'm trying "gcloud compute disks create tcal-xlnx-172-disk --image-project=foss-fpga-tools-kokoro --image=opt-xilinx--2018-01-10 --zone=us-central1-a", and I get an error "The project 'foss-fpga-tools-kokoro' was not found."
OmniMancer1 has joined #symbiflow
OmniMancer has quit [Ping timeout: 256 seconds]
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 256 seconds]
wavedrom has quit [Ping timeout: 256 seconds]
kraiskil has joined #symbiflow
promach3 has quit [Quit: killed]
xobs has quit [Quit: killed]
abeljj[m] has quit [Quit: killed]
synaption[m] has quit [Quit: killed]
madushan1000[m] has quit [Quit: killed]
xobs has joined #symbiflow
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
promach3 has joined #symbiflow
synaption[m] has joined #symbiflow
abeljj[m] has joined #symbiflow
madushan1000[m] has joined #symbiflow
Bertl_zZ is now known as Bertl
ants` is now known as nats`
epony has quit [Ping timeout: 258 seconds]
OmniMancer1 has quit [Quit: Leaving.]
epony has joined #symbiflow
epony has quit [Remote host closed the connection]
lambda has quit [Quit: WeeChat 2.7.1]
lambda has joined #symbiflow
lambda has quit [Client Quit]
lambda has joined #symbiflow
vup2 is now known as vup
spasu has joined #symbiflow
spasu has quit [Remote host closed the connection]
kraiskil has quit [Ping timeout: 250 seconds]
kraiskil has joined #symbiflow
sorear has quit [Ping timeout: 240 seconds]
sorear has joined #symbiflow
<mithro>
timo.callahan: I think the project is actually called foss-fpga-tools rather than foss-fpga-tools-kokoro due to hysterical raisins
<tpb>
Title: LUT with FlipFlop Example SymbiFlow Verilog to XML (V2X) 0.0-441-g4bc9809 documentation (at python-symbiflow-v2x.readthedocs.io)
<mithro>
@daniellimws It could use work
<daniellimws>
I was reading about fasm https://symbiflow.readthedocs.io/projects/vtr/en/latest/utils/fasm.html . Am I right to say that fasm_mux does not generate a multiplexer in the HDL sense, like `o = s ? a : b`? But is used to decide which connection to make when generating the bitstream instead? Because the documentation states that "From the perspective of genfasm, the <direct> and <mux> tags are equivalent." which was confusing to me.
<tpb>
Title: Clock Examples SymbiFlow Verilog to XML (V2X) 0.0-441-g4bc9809 documentation (at python-symbiflow-v2x.readthedocs.io)
<mithro>
daniellimws: There are two types of muxes in an FPGA, those which are controlled via the bitstream (called routing muxes) and those controlled via user signals (sometimes called BELs or Logic muxes)
<tpb>
Title: SymbiFlow Parts Encyclopedia - Google Docs (at docs.google.com)
<daniellimws>
mithro: Because to generate a logic mux, we can define it in verilog using the `o = s ? a : b` syntax right? But is there any such syntax for routing muxes?
<mithro>
s would be a constant for a routing mux
<daniellimws>
Ah ok thanks, learning so many new things beyond hardware design from reading the VPR documentation/tutorials. Interesting stuff.
<daniellimws>
Wow this looks neat. By the way, shall we change to using the readthedocs theme instead of the material theme. The things feel out of place...
<mithro>
daniellimws: Hrm? We use the martial design theme for all the symbiflow docs
<mithro>
@daniellimws That looks like a bug, it should be rendered with the material design theme. Can you log an issue against https://github.com/SymbiFlow/symbiflow-docs repo?
<tpb>
Title: GitHub - SymbiFlow/symbiflow-docs: Documentation for SymbiFlow (at github.com)
<mithro>
FFY00: Are somewhat trying to wean myself off the GDocs habbit
<FFY00>
yeah
<mithro>
100% unsuccessfully however :-)
<FFY00>
they are super useful
<FFY00>
mithro, would it be fine to user circleci instead of travis
<FFY00>
don't know if you missed my message above
<mithro>
Travis is the preferred tool
<mithro>
Consistency is good :-)
<FFY00>
yes, but travis is missing native docker support
<FFY00>
which makes things a bit clunky
<FFY00>
since I will have to maintain a script outside .travis.yml to do things
<mithro>
FFY00: It's pretty common to have .travis.yml set up some stuff and then call a script a normal user would call (In fact that is probably the preferred way)
<tpb>
Title: Using Docker in Builds - Travis CI (at docs.travis-ci.com)
<mithro>
FFY00: I would say that Google Cloud Build would be the best option if you are thinking about something with more "docker native" support -- as we have a large amount of free resources there
<FFY00>
that works for me
OmniMancer has joined #symbiflow
<FFY00>
are you fine using it or do want travis?
<mithro>
I prefer travis, but would take cloud build