Hi Bryan, > 2. PIPEs should at least have the following configuration options: > > b. H/W depth of the pipe - since this needs be compiled I am concerned about making this a requirement since it would impose restrictions on the implementation that I don't think are necessary. If we included this in the standard we would have to define what it means in terms of behavior of the pipe. That is, it only makes sense to include this if it has an observable effect on the behavior of the test. Implementations should be free to choose how to implement the buffering in the pipes. They may choose to put all buffering on the HW side, or split it between SW and HW sides. So setting the HW depth may not make sense in some implementations. > c. H/W max width of the pipe - since this needs to be > compiled I assume this is the same as the width of the data argument in the pipe calls on the HDL side? Per -- Per Bojsen Email: <bojsen@zaiqtech.com> Zaiq Technologies, Inc. WWW: http://www.zaiqtech.com 78 Dragon Ct. Tel: 781 721 8229 Woburn, MA 01801 Fax: 781 932 7488Received on Thu Mar 9 07:02:53 2006
This archive was generated by hypermail 2.1.8 : Thu Mar 09 2006 - 07:02:58 PST