ICM Issue Resolution Document  (IIRD)

IIRD ID#:        8
ISSUE TITLE:     Distinct Model_pinmap and Model_nodemap Names
REQUESTOR:       Bob Ross, Teraspeed Consulting Group
DATE SUBMITTED:  September 22, 2004
DATE REVISED:    
DATE ACCEPTED BY IBIS OPEN FORUM: 

****************************************************************************
****************************************************************************

STATEMENT OF THE ISSUE:

Model_pinmap and Model_nodemap names under [Tree Path Description] and
[Nodal Path Description] need to be distinct to allow interfacing with IBIS
or other types of connections.

****************************************************************************

STATEMENT OF THE RESOLVED SPECIFICATIONS:

Change instructions are indicated by |* lines

|*-----

|* Under [Tree Path Description], and under the following section:

              Model_pinmap

              A path description begins with the required subparameter 
              Model_pinmap.  This subparameter is followed by the name of a 
              "pin map" which names the pins on that end of the interconnect.  
              A second Model_pinmap is used at the end of the path description 
              to reference the pin map used for the other end of the 
              interconnect.  The Model_pinmap subparameter can also be used to 
              reference a pin map for the pins at the end of any Fork.  Note 
              that the pin map name given as an argument to a Model_pinmap 
              subparameter must match the name of a pin map defined by a 
              subsequent [ICM Pin Map] keyword.

              The argument to the Model_pinmap subparameter and the sub-
              parameter itself are separated by whitespace.  There can be as 
              many Model_pinmap subparameters as required, but each must be on 
              a single line.
 
|* Delete this paragraph:

              In general, an interconnect will have a single pin map that is 
              referenced at the beginning and end of a path description.

|* Replace with:

              One or more Model_pinmap lines can exist, but each argument must
              be unique, even if the referenced [ICM Pin Map] contents are
              identical.

|* Change the Model_pinmap arguments in Example 1 from

[Tree Path Description]
Model_pinmap  Example1_pinmap                 |* change
  Section Mult=1 Diagonal_matrix1
Model_pinmap  Example1_pinmap                 |* change
  .
  .
  .
[End ICM Model]

|* To:

[Tree Path Description]
Model_pinmap  Example1_pinmap1
  Section Mult=1 Diagonal_matrix1
Model_pinmap  Example1_pinmap2
  .
  .
  .
[End ICM Model]

|*-----

|* Under [Nodal Path Description] and under the following section:

              Model_nodemap

              The required subparameter Model_nodemap is used to reference the 
              [ICM Node Map] keyword which provides a mapping between the 
              actual data book pin (or signal) names and the node names used 
              in the path description.

              A path description must have at least one occurrence of the
              required subparameter Model_nodemap, but can have as many
              Model_nodemap subparameters as needed to adequately describe
              the interconnect.  The number of Model_nodemap subparameters  
              used in a path description would be typically the same as the
              number of ends or sides in a connector or interconnect.  Each
              Model_nodemap subparameter must be on a single line.

              The Model_nodemap subparameter is followed by one argument,  
              which the name of a node map.  The argument must match the name 
              of a node map defined by a subsequent [ICM Node Map] keyword.  
              The argument and the subparameter must be separated by at least 
              one white space.

|* Add this paragraph:

              One or more Model_nodemap lines can exist, but each argument
              must be unique, even if the referenced [ICM Node Map] contents
              are identical.

|*-----

****************************************************************************

ANALYSIS PATH/DATA THAT LED TO SPECIFICATION:

Originally it was assumed that if the pinout at each end of an interconnect
such as a connector had the same pin numbers, then the same [ICM Pin Map]
table could be used as referenced by the Model_pinmap.

However, this leads to ambiguous begin-end conditions for straight through
paths and possible ambiguity for splitter topologies possible in both the
Tree Path Description] and [Nodal Path Description] when a specific end
needs to be connected externally.  So unique Model_pinmap and Model_nodemap
names are explicitly specified to assist in the correct connection.

This prepares ICM for a possible IBIS BIRD to connect IBIS with ICM using
the multi-lingual format.

The language is not changed regarding possible single Model_pinmap and
Model_nodemap lines.  And Unmated model will have a single Model_*map line.

****************************************************************************

ANY OTHER BACKGROUND INFORMATION:

IIRD8 assumes that IIRD6 will be rejected.

The golden parser must be corrected to accept only one Model_*map or else
test that the arguments of several are unique.

****************************************************************************