====================================================================== IBIS INTERCONNECT MODELING AD HOC TASK GROUP MEETING MINUTES AND AGENDA http://www.eda.org/ibis/adhoc/interconnect/ Mailing list: ibis-interconn@xxxxxxxxxxxxx ====================================================================== Meeting Time 9 AM US Pacific Time Wednesday, June 02, 2010, 09:00 AM US Pacific Time 916-356-2663, Bridge: 4, Passcode: 994-6362 Live Meeting: https://webjoin.intel.com/?passcode=9946362 Agenda - Attendance - Opens - Call for patents - Review of TS2.x Binary Proposal Document ====================================================================== Minutes from May 26, 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 opens. No patents. Michael Mirmak reviewed the latest draft of the binary proposal document, with changes collated by Bob Ross. Michael inquired whether noise data will ever need to extend beyond two ports. Greg Edlund and Bob both responded that this was not known, but unlikely. The current draft will add the Noise Data section to the binary data, optionally, and reinstate the [End] keyword. This will allow [Binary] to appear up to twice in the same document. Bob also suggested removal of the T1, T2 and T3 internal notations. Michael asked whether separate precisions were needed for frequency and data sections. Walter responded that we do indeed need separate precisions, with high precision required for frequency information and lower precision needed for the actual data. The team discussed how the hexadecimal representation is to be used in the document. The current example shows "00 00 00" but it's unclear whether this is the first data section or the data separator. From Walter's statements, a byte is a single ASCII character, with the first pair therefore being the separator. The next 8 bytes form the 64 bit frequency data. The team agreed that the hex codes are just a visualization, and additional text is needed to explain this. For future meetings, the team will address port/node mapping. Michael inquired whether sparse or mixed-mode matrices will interfere with binary representations. Walter suggested that combining binary and sparse notations will be very helpful for connectors. Nothing special, though, should be needed for mixed-mode or sparse treatments in binary. In addition, no line-length limits or line termination sequences should be needed in the final documents. Walter suggested that the C code for streaming conversions of binary data be put on the web. Walter also suggested that additional documents be considered by the team: wrappers for combining PCB and device interconnects, and wrappers for treating both connectors and packages. ARs John Angulo: recheck the hexadecimal codes in the specification doc. ------------------------------------------------------------------ The IBIS Ad Hoc Interconnect Task Group Mailing List Archives are available at: http://www.freelists.org/archives/ibis-interconn TO UNSUBSCRIBE: Send a message to "ibis-interconn-request@xxxxxxxxxxxxx" with a subject of "unsubscribe" To administer your subscription status from the web, visit: http://www.freelists.org/list/ibis-interconn