Re: gEDA-user: order of defparam vs. #(.) parameters in icarus

2009-02-17 Thread Matt Ettus
On Tue, Feb 10, 2009 at 4:23 PM, Stephen Williams wrote: > Matt Ettus wrote: >> In some Xilinx models, they make instantiations like this: >> >> block instance(ports); >> defparam instance.param=VALUE >> >> >> This normally works ok. The problem is that inside the block, >> generate statements ar

Re: gEDA-user: order of defparam vs. #(.) parameters in icarus

2009-02-10 Thread Stephen Williams
Matt Ettus wrote: > In some Xilinx models, they make instantiations like this: > > block instance(ports); > defparam instance.param=VALUE > > > This normally works ok. The problem is that inside the block, > generate statements are being used which are dependent on the value of > the parameter.

gEDA-user: order of defparam vs. #(.) parameters in icarus

2009-02-09 Thread Matt Ettus
In some Xilinx models, they make instantiations like this: block instance(ports); defparam instance.param=VALUE This normally works ok. The problem is that inside the block, generate statements are being used which are dependent on the value of the parameter. What appears to be happening is th