====================================================================== IBIS INTERCONNECT MODELING AD HOC TASK GROUP MEETING MINUTES AND AGENDA http://www.eda.org/ibis/adhoc/interconnect/ Mailing list: ibis-interconn@freelists.org ====================================================================== Minutes from April 14, 2010: Attendees: ---------- (* denotes present) Agilent - Radek Biernacki, John Moore, Ken Wong Ansoft - Denis Soldo Cadence Design Systems - Terry Jernberg, Brad Griffin Green Streak Programs - Lynne Green Hewlett-Packard - Rob Elliott IBM - Greg Edlund*, Lijun Jiang, Yaping Zhou Intel - Michael Mirmak* I/O Methodology - Lance Wang Mentor Graphics Corp. - John Angulo*, Vladimir Dmitriev-Zdorov Micron Technology - Justin Butterfield*, Randy Wolff Sigrity - Sam Chitwood, Raymond Y. Chen, Tao Su, Brad Brim SiSoft - Walter Katz* Teraspeed Consulting Group - Bob Ross* ======================================================================== No patents were announced. No opens were raised. Michael Mirmak reviewed the binary TS2 document, called a proposed draft 4. Bob Ross suggested adding an explicit prohibition on the [End] statement. Michael responded by asking whether [End] is prohibited or ignored. Bob suggested that a binary bit count not be added. He has not decided yet about parser checking of binary data quality. Michael asked for confirmation of team agreement that only part of the file would be in binary format. No objections were raised. Bob noted that conversion is not performed on the entire file, just the binary section. No prohibition on sparse, mixed-mode, etc. Positioning of the keyword after [Network Data] is critical. John Angulo suggested that no comments be permitted after the [Binary] keyword; no other keywords. Michael asked about whether line-termination sequences should be optional before the binary data. Walter Katz noted that a line-termination sequence is needed before binary data; binary data delimiter shall be a 00000000 (binary) zero or NULL. Michael asked whether the team needs to worry about "past-proofing" the next editions. IBIS is different than TS in that TS2.0 calls out specific rules for specific versions of the specification. Bob suggested this was not a worry. The team discussed whether the [Binary] keyword was a command or simply a delimiter. The team agreed that [Binary] is not a command to a parser or EDA tool, but simply indicates where [Binary] data is stored. Bob confirmed tha the assumed input to any converter would be a regular TS2.1 file *without* the [Binary] keyword. Parsed data should always be correct as it is, not treated as instructions for a converter. Michael concluded the meeting by noting that further comments will be incorporated and reviewed in the next meeting. In addition, he will propose for next time a discussion on adopting the ANSI document format for Touchstone 2.0, to make editing easier. ARs: Michael: update document so that [End] statement should NOT be included if [Binary] used. From [Binary] through the end-of-file marker is to assumed all binary content. Michael: check TS2.0 language on placement of line-termination sequence. Is it permitted within a keyword or between keyword and arguments? No separation between Binary and its arguments is to be permitted?