ChanServ changed the topic of #yosys to: Yosys Open SYnthesis Suite: https://github.com/YosysHQ/yosys/ | Channel logs: https://libera.irclog.whitequark.org/yosys/
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
gsmecher has quit [Ping timeout: 252 seconds]
bl0x has joined #yosys
lumo_e has joined #yosys
lumo_e has quit [Remote host closed the connection]
citypw_ has joined #yosys
bl0x has quit [Ping timeout: 252 seconds]
bl0x has joined #yosys
kristianpaul has quit [Read error: Connection reset by peer]
emeb_mac has quit [Ping timeout: 252 seconds]
kristianpaul has joined #yosys
FabM has joined #yosys
FabM has joined #yosys
FabM has quit [Changing host]
emeb_mac has joined #yosys
citypw_ has quit [Ping timeout: 276 seconds]
y__ has joined #yosys
<bluesceada> hey is there some kind of 'strict' mode in yosys ? like "multiple driver" is not an error!
<bluesceada> It is just like "Warning: Driver-driver conflict for ..."
<bluesceada> We are using yosys/nextpnr for teaching. Is there an option to make this an error?
vidbina has joined #yosys
vidbina has quit [Ping timeout: 252 seconds]
ec_ has quit [Ping timeout: 276 seconds]
peeps[zen] has joined #yosys
peepsalot has quit [Ping timeout: 252 seconds]
peepsalot has joined #yosys
peeps[zen] has quit [Ping timeout: 252 seconds]
gsmecher has joined #yosys
FabM has quit [Quit: Leaving]
<lofty> bluesceada: There's -e regex, so you could have your students run a script which is "yosys -e 'Driver-driver conflict'"
ec_ has joined #yosys
<xiretza[m]> for future semesters, have you ever considered using VHDL instead of (presumably) Verilog? The language is a lot stricter in general
<mewt> in what situations would multiple drivers be wanted?
<mewt> I don't know of any, at least
<mwk> pretty much the only case is tristate buses
<cr1901> I... well, I guess a tristate wire CAN be multiply driven. Huh...
<Sarayan> same for open-collector