<Zevv>
is there a way for yosys+nextpnr to estimate max timing for a 'loose' verilog module without having to place it in a larger design and constraint it to IO?
<Zevv>
I'd like to optimize at a more fine grained level and get timing details for the individual modules of my design
bjorkintosh has quit [Ping timeout: 240 seconds]
emeb_mac has quit [Quit: Leaving.]
<gatecat>
Zevv: You can use --out-of-context for nextpnr, but I think this is only implemented for ECP5 at the moment
<Zevv>
thanks
<Zevv>
not having any clue of what i'm doing, I ported that ooc code to ice40, and at least i'm able to get me device utilisation stats now. that's nice already.
flokli has quit [Ping timeout: 268 seconds]
flokli has joined #yosys
flokli has quit [Client Quit]
bjorkintosh has joined #yosys
bjorkintosh has quit [Changing host]
bjorkintosh has joined #yosys
lexano has joined #yosys
emeb_mac has joined #yosys
flokli has joined #yosys
notgull has joined #yosys
notgull has quit [Ping timeout: 256 seconds]
notgull has joined #yosys
notgull has quit [Ping timeout: 268 seconds]
notgull has joined #yosys
ec has quit [Ping timeout: 255 seconds]
ec has joined #yosys
jleightcap has quit [Remote host closed the connection]
ymherklotz has quit [Remote host closed the connection]
muuo has quit [Read error: Connection reset by peer]