whitequark changed the topic of #yosys to: Yosys Open SYnthesis Suite: https://github.com/YosysHQ/yosys/ | Channel logs: https://libera.irclog.whitequark.org/yosys/ | Bridged to #yosys:matrix.org
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
bjorkintosh has quit [Read error: Connection reset by peer]
bjorkintosh has joined #yosys
bjorkintosh has joined #yosys
bpye has quit [Quit: Ping timeout (120 seconds)]
bpye has joined #yosys
<famubu[m]> <lofty> "If you run "help synth_gowin..." <- Oh... I see it now..
<famubu[m]> <lofty> "But if you're just trying to..." <- 👍️ That was my primary aim.
<famubu[m]> <lofty> "If you're doing this to learn..." <- Also interested in this. Been reading the yosys manual from here and there.
<famubu[m]> <lofty> "LUT5/6/7/8: it's true that Gowin..." <- Ah.. right.
<famubu[m]> <lofty> "(which is all done as part of..." <- That what should be used? Not`read_verilog file.v; synth_gowin -top top -json top.json`?
<famubu[m]> * That's what, * used? Not `read_verilog file.v;
<famubu[m]> And I didn't totally get what specify does in verilog. I mean, it says it's for mentioning some delay in a module. But what delay? And where does it come in handy?
<famubu[m]> Are specify blocks used only during timing?
<famubu[m]> * Are specify blocks used only during timing analysis? They are otherwise inert?
<lofty> famubu[m]: yes, they're mainly used in timing analysis, although they're also used in some cases to describe possible paths through cells, such as flops.
lexano has joined #yosys
tlwoerner_ has joined #yosys
tlwoerner has quit [Remote host closed the connection]
tlwoerner__ has joined #yosys
tlwoerner_ has quit [Ping timeout: 248 seconds]
nak has quit [Ping timeout: 255 seconds]
nonchip has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nonchip has joined #yosys
philtor has quit [Read error: Connection reset by peer]