Can we fix the placement and naming of connect modules in this release? 7.8.4 - 3rd "2)" - The connect module for a port shall be instantiated in the context of the ports upper connection Should be something like - Connect modules are instantiated in the nearest parent instance of the drivers being converted for a d2a, or the nearest parent instance of the receivers for an a2d, or the nearest parent instance of both for a bidir. - that means the port's lower connection. The naming is less critical, but it should avoid depending on anything variant so using the discipline is a bad idea, I'd suggest keeping it simple with just : SigName__<mode> Where <mode> is a2d, d2a or bidir - noting the current scheme doesn't handle having separate d2a and a2d on the same signal in the same instance. I see no need to differentiate merged and split, and the other stuff (ModuleName, BottomDiscipline, InstName, PortName) isn't necessary if you are instantiating on the low side of the ports. Note: the placement is important for correct behavior in back-annotation and locating implicit signals (power etc.), the name is mostly for debugging purposes. Kev. -- True Circuits Inc. - http://www.truecircuits.com Tel: (650) 949 3400 Ext 3415 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Mar 27 17:33:49 2008
This archive was generated by hypermail 2.1.8 : Thu Mar 27 2008 - 17:33:58 PDT