danieljabailey has quit [Quit: ZNC 1.6.6+deb1ubuntu0.1 - http://znc.in]
<sorear>
does icetime do multiclock?
acksys_ has quit [Ping timeout: 256 seconds]
<corecode>
i doubt, how would it know
ZipCPU|Laptop has joined #yosys
ZipCPU|Laptop has quit [Ping timeout: 245 seconds]
ZipCPU|Laptop has joined #yosys
ZipCPU|Laptop has quit [Read error: Connection reset by peer]
<lutsabound>
sorear: nextpnr supports multiple clock timing. There's no longer any need for icetime
<sorear>
lutsabound: mm, can you instruct corecode on how to use nextpnr to compute a timing analysis for a bitstream generated by iCEcube? I was under the impression that was not possible with nextpnr
<lutsabound>
I'd have to go back to the nextpnr docs myself
<lutsabound>
I know its in there, I've seen the capability, but havent done multiple clocks yet myself
<lutsabound>
daveshah knows more about it than I do
<sorear>
specifically I was under the impression icetime could ingest an externally-generated bitstream, but nextpnr was limited to timing bitstreams it itself generated
<lutsabound>
Hmm... that may be the case
_whitelogger has joined #yosys
emeb has quit [Quit: Leaving.]
emeb_mac has joined #yosys
gsi__ has joined #yosys
gsi_ has quit [Ping timeout: 246 seconds]
citypw has joined #yosys
rohitksingh_work has joined #yosys
citypw has quit [Remote host closed the connection]
leviathanch has joined #yosys
citypw has joined #yosys
citypw has quit [Excess Flood]
citypw has joined #yosys
lutsabound has quit [Quit: Connection closed for inactivity]
danieljabailey has joined #yosys
pie___ has joined #yosys
pie___ has quit [Remote host closed the connection]
pie___ has joined #yosys
pie__ has quit [Ping timeout: 268 seconds]
Cerpin has quit [Quit: leaving]
citypw has quit [Ping timeout: 245 seconds]
citypw has joined #yosys
Cerpin has joined #yosys
chaseemory has quit [Remote host closed the connection]
leviathanch has quit [Remote host closed the connection]