08:42 <mithro> Just FYI - I'm at the RISC-V Workshop in Zurich today

08:42 <mithro> acomodi / litghost - btw duck2 is going to reach out to you about some stuff he has been doing with VtR

09:18 <sf-slack2> <acomodi> mithro: sure, I'll provide all the possible support

09:44 <mithro> https://github.com/leon575777642/vprgen/commit/ba3d8f95d5f0c23ac5129083d6f3dc5ecbfcf92f

09:44 <tpb> Title: Added support for metadata · leon575777642/vprgen@ba3d8f9 · GitHub (at github.com)

09:53 <mithro> duck2: If you haven't looked at https://github.com/leon575777642/vprgen - you should take a look

09:53 <tpb> Title: GitHub - leon575777642/vprgen: VPRs architecture description and routing resource graph XML generation API (at github.com)

11:27 <mithro> https://docs.google.com/drawings/d/15hSX1cHwz2_Lm-CxQxlelGUuVPP4AmEEljyRb1ncjjk/edit?usp=drivesdk

11:27 <tpb> Title: LiteX Ecosystem Diagram - Google Drawings (at docs.google.com)

18:24 <litghost> tmichalak2: I've killed some of the prjxray jobs to let https://github.com/SymbiFlow/prjxray/pull/879 run ahead. I've run it locally, and the runtime is back to "normal", e.g. 1 hr instead of 4-5

18:24 <tpb> Title: Avoid building full speed_model dict. by litghost · Pull Request #879 · SymbiFlow/prjxray · GitHub (at github.com)

19:54 <sf-slack2> <tmichalak> @litghost: you were actually able to generate a whole database in 1 hour? But even so it seems that is not the case with kokoro - the CI for 879 has been running for 2 so far

19:54 <litghost> tmichalak2: I was only referring to 074

19:56 <sf-slack2> <tmichalak> @litghost: makes sense then, let's see what will its runtime in PR 879

20:59 <sf-slack2> <tmichalak> @litghost: 2:26h for Zynq, looking good...