03:29 <mkk_> [Noah Moroze, skywater-pdk] Hi all, I wanted to confirm whether or not the requirement that “The project must be fully open. The project must contain a GDSII layout, which must be reproducible from source contained in the project.” means that the entire RTL->GDSII flow must be reproducible using open tooling? I.e. are we allowed to use proprietary or unreleased software as part of the build flow?

06:18 <mkk_> [Olof Kindgren, skywater-pdk] @Lucas Koerner I was speaking to someone recently who was also interested in the testing side and was wondering what was available in the open source ecosystem. It feels to me like one of the many underserved areas of chip design. Would be great to have more people working on this

11:17 <mkk_> [Rob Taylor, skywater-pdk] @Lucas Koerner That project should definitely exist! It might be interesting to talk with the folk at Devtank

17:54 <mkk_> [Tim 'mithro' Ansell, skywater-pdk] @Jean - I'm pretty sure the Caravel framework is *not* routed using closed source tools.

17:55 <mkk_> [Tim 'mithro' Ansell, skywater-pdk] The foundry does use some closed source tools as part of the production but that is transparent to the person supplying the GDS.

18:26 <mkk_> [Jean M. Cyr, skywater-pdk] Sorry, I said that backwards. Seems obvious the riscv core was place and routed using commercial tools.

19:35 <mkk_> [Tim 'mithro' Ansell, skywater-pdk] @Jean You keep saying commercial -- I think you mean proprietary / closed source

19:36 <mkk_> [Tim 'mithro' Ansell, skywater-pdk] @Jean And again, the riscv core in caravel was placed and routed using the open source tools *not* the closed source ones

23:13 <mkk_> % make openlane

23:13 <mkk_> docker pull efabless/openlane:current

23:13 <mkk_> Error response from daemon: manifest for efabless/openlane:current not found: manifest unknown: manifest unknown

23:13 <mkk_> [Matt Liberty, skywater-pdk] Has anyone seen this problem today:

23:13 <mkk_> make: *** [Makefile:158: openlane] Error 1

23:16 <mkk_> [Matt Liberty, skywater-pdk] it's gone now, it must have been some transient issue