Include information about how open source PDKs should be structured #7
Comments
|
There is also the "Library Naming" section of the existing SkyWater-PDK at https://skywater-pdk.readthedocs.io/en/main/contents/libraries.html#library-naming |
mithro
added a commit
to mithro/gf180mcu-pdk
that referenced
this issue
Jul 24, 2022
Goal is to include common information about open source PDKs into the GF180MCU PDK documentation. This includes; * File naming information - google/open-source-pdks#7 * Versioning scheme - google/open-source-pdks#8 * Other open source PDKs that exist. Signed-off-by: Tim 'mithro' Ansell <[email protected]>
mithro
added a commit
to mithro/gf180mcu-pdk
that referenced
this issue
Jul 24, 2022
Goal is to include common information about open source PDKs into the GF180MCU PDK documentation. This includes; * File naming information - google/open-source-pdks#7 * Versioning scheme - google/open-source-pdks#8 * Other open source PDKs that exist. Signed-off-by: Tim 'mithro' Ansell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be good if this repository included information about how the Google open source PDKs are structure and how things are named.
I have tried to create a document at https://bit.ly/open-source-pdks-naming which includes information about this stuff.
The text was updated successfully, but these errors were encountered: