chipsalliance / diplomacy Goto Github PK

Currently, diplomacy supports both build-form-source and build-from-ivy for chisel3 and cde.
However, before resolving chipsalliance/cde#20 issue, we are not able to build-from-ivy automatically.
To build-from-ivy, users should run mill __.publishLocal at cde repository, then make compile in diplomacy repository.

Diplomacy are split form RocketChip, which should return to RocketChip as ivy dependency.
chipsalliance/rocket-chip#2741 prototypes this replacement, but it is build-from-source, after #1 and #2 closed, we should publish this repository.

Originally, diplomacy was a part of TileLink, which was tested by elaboration. After splitting from RocketChip, a desire to full test is increasing, it can help diplomacy to have a CI flow, and also use real code to show usage to users.

BaseNode.serial, LazyModule.index, LazyModule.scope should be a context dependent value.

public and private API should be discussed at RocketChip Working Group or Chisel Working Group.
Currently since diplomacy are split from RocketChip, most of APIs are public, and some of them should not be public, we need gather feedback from users to decide a public API.

Originally, @sequencer added documentation to diplomacy.
After diplomacy being split from rocket-chip, most of links are dead or out-of-date.
We need to re-edit the documentation, helping users to understand diplomacy.

We need to publish diplomacy to maven, which makes RocketChip and other repository being able to use this without compiling from source, I have added the publish CI infrastructure, beside this we still need to set environments below:

PGP_PASSPHRASE: ${{ secrets.PGP_PASSPHRASE }}
PGP_SECRET: ${{ secrets.PGP_SECRET }}
SONATYPE_PASSWORD: ${{ secrets.SONATYPE_PASSWORD }}
SONATYPE_USERNAME: ${{ secrets.SONATYPE_USERNAME }}

I can provide my GitHub PGP key for signing and publishing, beside this, SONATYPE_USERNAME and SONATYPE_PASSWORD should be provided too, asking @mgielda for help.