ChanServ changed the topic of #yosys to: Yosys Open SYnthesis Suite: https://github.com/YosysHQ/yosys/ | Channel logs: https://libera.catirclogs.org/yosys/ | Bridged to #yosys:matrix.org
tpb has quit [Remote host closed the connection]
tpb has joined #yosys
jn has quit [Ping timeout: 276 seconds]
jn_ has joined #yosys
jn_ has joined #yosys
jn_ has quit [Changing host]
<vancz> Does yosys do warning and linting and such? I accidentally some verilog where I did a two bit case statement on a register I accidentally made only 1 bit.
lofty[m] has joined #yosys
<lofty[m]> For linting use a linter; Verilator would probably catch it
<vancz> guess I need to combine more toolchains
<vancz> I have a basic question; can I assert a signal and then assert another signal to deassert it on the next clock cycle? or do I need a cycle extra in between to notice the deassert signal?
<vancz> specifically if I have two (software implementations of) chips, one asserts an IRQ, the other detects the IRQ and says to clear it with an IRQ_CLR signal
<vancz> can I do that in two clock cycles or do I need three?
* vancz wonders if he is asking what he actually means to ask
FabM has joined #yosys
FabM has joined #yosys
kristianpaul has joined #yosys
krispaul has quit [Ping timeout: 244 seconds]
anticw has quit [Ping timeout: 244 seconds]
anticw has joined #yosys
<csantosb> Hi, I wonder if this licensing issue with prjbeyond-db may be solved, https://github.com/YosysHQ-GmbH/prjbeyond-db/issues/2
<lofty[m]> csantosb: what's your intended usecase for that? to be quite honest it never worked amazingly well, and it's not like you can use the end result on real hardware
<csantosb> lofty[m]: packaging nextpnr and all of its supported devices under Guix, see https://issues.guix.gnu.org/78390
<tpb> Title: [PATCH electronics-team] gnu: nextpnr: Add ecp5 and himbaechel architectures. (at issues.guix.gnu.org)
<lofty[m]> csantosb: yeah, I wouldn't bother.
<lofty[m]> I think the venn diagram of Guix users and people interested in the NanoXplore FPGA is two separate circles
<csantosb> Unless a license is provided, it cannot be distributed, and this holds for all repositories.
<lofty[m]> then do not distribute it. nextpnr is modular enough that you can simply not build the ng-ultra uarch.
<csantosb> Any reason not to ?
<lofty[m]> have you actually tried to use that architecture?
<lofty[m]> you cannot use the output of it, because converting the nextpnr output to a usable bitstream requires a license for NanoXplore's Impulse toolchain
<csantosb> Sure, this is explained in the readme
<lofty[m]> sorry, I'm really confused here
<lofty[m]> why do you want to package a toolchain you cannot use for anything.
<csantosb> For exactly the same reason nextpnr considers it
<lofty[m]> I do not think your motivation here is "so I could still have a job"
<csantosb> ?
<tpb> Title: An open source FPGA toolchain for a European space-grade FPGA | Activities Portal (at activities.esa.int)
<lofty[m]> that ESA money partially went towards making sure I still had a job.
<lofty[m]> in terms of actually making an architecture open-source, this was a dead end from the start because of the dependence on Impulse
<csantosb> No, unrelated
<lofty[m]> we published it so we had stuff to show to ESA.
zero-xray6 has joined #yosys
zero-xray has quit [Ping timeout: 276 seconds]
zero-xray6 is now known as zero-xray
peepsalot has quit [Remote host closed the connection]
peepsalot has joined #yosys
FabM has quit [Ping timeout: 268 seconds]
smkz has quit [Quit: smkz]
smkz has joined #yosys
smkz has quit [Quit: smkz]
smkz has joined #yosys
nonchip has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nonchip has joined #yosys
flag has quit [Ping timeout: 252 seconds]
flag has joined #yosys
jn_ is now known as jn