<Guest48>
that's the example I saw. I don't want to type in the ports, parameters, attributes etc. I want them to be parsed/inferred from the verilog file; like if you have 5 ready-valid channels with these suffixes & directions, it might be an axi-initiator etc.
<tpw_rules>
afaik that's not possible
<Guest48>
Basically I'm looking for something like magma's m.define_from_verilog_file
<Guest48>
It would be a great feature if it existed and would make integration much easier.