Changes between Version 8 and Version 9 of Component/Mapping Table


Ignore:
Timestamp:
Feb 11, 2008, 10:49:59 AM (16 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Component/Mapping Table

    v8 v9  
    8181 * all VCI targets must have different indexes.
    8282 * all VCI initiators must have different indexes.
    83  * The initiator index must be equal to the VCI SRCID value. Most hardware interconnects (such
    84    as the [wiki:Component/PibusBcu PibusBcu] or the [wiki:Component/VciVgmn VciVgmn] components)
    85    make the assumption that the initiator indexes are between 0 and M -1 , where M is the total number of VCI initiators.
     83 * The initiator index must be equal to the VCI SRCID value.
    8684 * The VCI ADDRESS field is structured in two fields:  `| MSB | OFFSET |`
    8785   * The MSB field is decoded by the flat interconnect to route the command packet to the proper VCI target.
    8886   * The OFFSET field is decoded by the VCI target.
    8987 * The VCI SRCID field is used by the interconnect to route the response packet to the proper VCI initiator.
    90  * Most flat hardware interconnects (such as the [wiki:Component/PibusBcu PibusBcu] or the
     88 * Most hardware interconnects (such as the [wiki:Component/PibusBcu PibusBcu] or the
    9189   [wiki:Component/VciVgmn VciVgmn] components) make the assumption that the target indexes are
    92    between 0 and T -1 (where T is the total number of VCI targets), and the initiator indexes are between
    93    0 and M -1 (where M is the total number of VCI initiators).
     90   between 0 and T-1 (where T is the total number of VCI targets), and the initiator indexes are between
     91   0 and M-1 (where M is the total number of VCI initiators).
    9492
    95 The flat interconnect must contain a ROM implementing a '''routing table''' indexed by the
     93The hardware interconnect contains a ROM implementing a '''routing table''' indexed by the
    9694VCI address MSBs and containing the corresponding target index.
    9795The content of this '''routing table''' is automatically computed by a method associated to the mapping table.
    … …  
    10098
    10199With a two-level interconnect, the hardware architecture is supposed to be split into several subsystems
    102 (or clusters), with a global interconnect for inter-cluster communications, and one local interconnect in
    103 each cluster for intra-cluster communications.
     100(or clusters). There is a global interconnect  (such as the [wiki:Component/VciVgmn VciVgmn] for inter-cluster communications, and one local interconnect (such as the [wiki:Component/VciLocalCrossbar VciLocalCrossbar] in each cluster for intra-cluster communications.
    104101
    105102 * each VCI component is identified by a structured index containing two indexes:
    106103   * a global index that identifies the subsystem (or cluster) index.
    107104   * a local index, that identifies the VCI component in the cluster.
    108  * all VCI components in the same cluster must have the same global index.
     105 * all VCI components in the same cluster have the same global index.
    109106 * all VCI components in the same cluster must have different local indexes.
    110107 * The VCI ADDRESS field is structured in three fields : `| MSB | LSB | OFFSET |`
    … …  
    117114
    118115The services provided by the Mapping Table for a two level interconnect are the following :
    119  * It generates the '''Global Routing Table''', indexed by the VCI ADDRESS MSB bits, and containing
    120    the corresponding global index (cluster index). This Global Routing Table is used by the global interconnect.
    121  * It generates - for each cluster - the '''Local Routing Table''', indexed by the VCI ADDRESS LSB bits
    122    and containing the corresponding target local index. Depending on the mapping, each cluster can
    123    have a different Local Routing Table.
     116 * It generates the '''Global Routing Table''', implemented as a ROM by the global interconnect. This table is indexed by the VCI ADDRESS MSB bits, and contains the corresponding global index (cluster index).
     117 * It generates - for each cluster - the '''Local Routing Table''', implemented as a ROM by the local interconnect. This table is indexed by the VCI ADDRESS LSB bits and contains the target local index. Depending on the mapping, each cluster can have a different Local Routing Table.
    124118