Additional templates / Future of Corsair

[LukiLeu]

Hi @esynr3z

First of all, thanks for your tool. It makes it really simple to generate and maintain consistent registers in hardware, software, and documentation. We even encourage students at our university to use such a tool in their theses.

Over the last few years, we have developed a tool that will enable students to start working with FPGAs quickly. The tool allows to control Vivado and Vitis easily and also provides an interface to read/write data streams and/or registers over Ethernet. To generate the registers, we rely on corsair.

As we think that this tool might also be helpful for other people, we would like to move forward and open-source our tool in the next few months. However, currently we are using a clone of corsair (see here). We added a bunch of new templates and also added some bugfixes to these templates.

We now wanted to ask if there is a way to incorporate these templates into corsair v1 and having a new release? When we release our first official version, we would really like to rely on the official package from corsair instead of doing some "hacks" and providing the templates with our tool.

Alternatively, how do you see the future/timeline of corsair? We can also imagine to switch to corsair v2 if that reaches a stable state.