edaa-org / pyEDAA.ProjectModel

An abstract model of EDA tool projects.
https://edaa-org.github.io/pyEDAA.ProjectModel
Other
10 stars 1 forks source link

Add support for SystemRDL source files #47

Open RasmusGOlsen opened 1 year ago

RasmusGOlsen commented 1 year ago

Can you add support for the register description language SystemRDL?

Here is a link to the standard https://www.accellera.org/downloads/standards/systemrdl. There is also a great open-source community with a compiler and additional applications https://github.com/SystemRDL.

Paebbels commented 1 year ago

@RasmusGOlsen thanks for the interest in the project and proposing this feature. Also thanks for pull-request #48.

There I see a pySRDLModel.py file implementing at least the version numbers of SystemRDL.

This file would be shipped and installed underneath pyEDAA.ProjectModel, that's not where it should go...

Can can offer 2 solutions:

  1. The GitHub organisation SystemRDL creates a pySRDLModel repository or
  2. I can offer a pySRDLModel under the HDL organisation, or
  3. I can also offer a pySRDLModel under the EDA² organisation.

I think the first solution is the better choice. The repository doesn't need to be complicated and could be a clone of pySVModel. It would offer a separate repository and a matching PyPI package.

If you are an owner of SystemRDL, you could set me up as a maintainer for that repository and I'll take care of the initial setup from for code, documentation page, license, packaging etc.

RasmusGOlsen commented 1 year ago

Yes, I agree that the pySRDLModel should be its own repository. I'm not the owner of the SystemRDL organization, so I don't have any mandate to create it. I can see that the pyVHDLModel is under the HDL organization and the pySVModel is under the EDA2. When I was searching for the models I first looked at the EDA2 organization, for me that would make the most sense.

Paebbels commented 1 year ago

Lets create it at EDA² and propose a handover to SystemRDL. Can you create an issue there?

RasmusGOlsen @.***> schrieb am So., 18. Juni 2023, 21:39:

Yes, I agree that the pySRDLModel should be its own repository. I'm not the owner of the SystemRDL organization, so I don't have any mandate to create it. I can see that the pyVHDLModel is under the HDL organization and the pySVModel is under the EDA2. When I was searching for the models I first looked at the EDA2 organization, for me that would make the most sense.

— Reply to this email directly, view it on GitHub https://github.com/edaa-org/pyEDAA.ProjectModel/issues/47#issuecomment-1596246746, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHJNTIK4IL3RNWLD73YLP3XL5KPDANCNFSM6AAAAAAZK2KJRE . You are receiving this because you commented.Message ID: <edaa-org/pyEDAA. @.***>

Paebbels commented 1 year ago

I can see that the pyVHDLModel is under the HDL organization and the pySVModel is under the EDA2.

Just one tiny correction, pyVHDLModel is under VHDL, not HDL (but I have access to both organisations).

For pySVModel we don't have a host, so it's currently at EDA². Independent of the GitHub location, the package name at PyPI is reserved.

Paebbels commented 1 year ago
Paebbels commented 1 year ago

48 got merged.

Paebbels commented 1 year ago

I did some updates and bugfixes to SystemRDL introduced by copy&paste from SystemVerilog.