======================================================================
IBIS INTERCONNECT TASK GROUP
http://www.eda.org/ibis/interconnect_wip/
Mailing list:
ibis-interconnect@xxxxxxxxxxxxx<mailto:ibis-interconnect@xxxxxxxxxxxxx>
Archives at //www.freelists.org/archive/ibis-interconn/
======================================================================
Attendees from June 24 Meeting (* means attended)
ANSYS Curtis Clark*
Cadence Design Systems Bradley Brim
Cisco
David Siadat
Intel Corp. Michael
Mirmak*
Keysight Technologies Radek Biernacki
Mentor Graphics Arpad Muranyi*
Micron Technology Justin Butterfield*,
Randy Wolff*
Signal Integrity Software Walter Katz, Mike
LaBonte*
Teraspeed Labs Bob Ross*
University of Aveiro in Portugal Wael Dghais
No patents were declared. No opens. Some technical issues prevented sharing
early in the meeting.
The team discussed "Terminal" rules, particularly for "Terminal ID" and whether
rules can only be stated in a table or must always be presented using text with
tables for reference. Randy Wolff suggested that putting all the rules in a
table will be problematic, but the sentences needed in text would be (and are)
long and complicated.
Some confusion was expressed about the differences between terminals, pads,
pins, and packages. Arpad Muranyi highlighted that we call Terminals by the
signal names, and we are trying to name the Terminals but all of the Terminals
include the signal name. Signal names are really a "line" while Terminals are
"points". Michael Mirmak suggested a subway analogy, where Terminals (really
nodes) are stations, and the signal is the "line" or route. Arpad suggested
this was similar to a highway as well, but if you want to call the exits by
their names, you use the exit number not the highway name.
Randy suggested that the specification is linking everything by pin. Michael
asked whether each pin has to have a minimum number of terminal_IDs associated
with it. Randy replied that, seemingly, at least two are required.
Michael suggested adding introductory sentences to describe all of this, before
the actual syntax is covered. Arpad asked whether the edits should involve
reversing the order here, with A_signal appearing first in the list. Randy
asked whether this was instead of organizing by Terminals. The specification
needs a statement that if Pad_A_signal exists, you are connecting a buffer and
a pad. This is not actually stated. A_signal is the buffer, Pad_A_Signal is
the pad.
Bob asked whether the specification was clear whether one can cascade
Interconnect models. He suggested adding several diagrams. Randy shows
diagrams used in earlier discussions, including those related to C_comp. Mike
LaBonte suggested using continuous lines, rather than using names to
identify/mask lines. In addition, a key is needed for "Terminal ID" (italic,
colors, etc.). Arpad noted that A_signal keeps appearing, but in different
contexts.
Review will continue in the next meeting.
ARs
- Randy Wolff to send diagrams to the reflector for review
