You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/src/arch/reference.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2750,7 +2750,7 @@ The number of any additional wires or muxes created by scatter-gather specificat
2750
2750
Overview of how scatter-gather patterns work. First, connections from a switchblock location are selected according to the specification.
2751
2751
These selected connection are then muxed and passed through the scatter-gather node, which is typically a wire segment. The scatter-gather node then fans out or scatters in another switchblock location.
2752
2752
2753
-
.. note:: Scatter-Gather patterns are only supported for 3D architectures where the scatter-gather links are uni-directional and uni-directional 2D architectures. Bidirectional sg_links are not currently supported.
2753
+
.. note:: Scatter-Gather patterns are only supported for uni-directional 3D and uni-directional 2D architectures. Bidirectional sg_links are not currently supported.
2754
2754
2755
2755
When instantiated, a scatter-gather pattern gathers connections from a switchblock and passes the connection through a multiplexer and the scatter-gather node which is typically a wire segment, then scatters or fans out somewhere else in the device. These patterns can be used to define 3D switchblocks. An example is shown below:
Copy file name to clipboardExpand all lines: vpr/src/route/rr_graph_generation/interposer_cut.cpp
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -137,12 +137,12 @@ std::vector<RREdgeId> mark_interposer_cut_edges_for_removal(const RRGraphView& r
137
137
}
138
138
139
139
/**
140
-
* @brief Update a CHANY node's bounding box in RRGraph and SpatialLookup entries.
141
-
* This function assumes that the channel node actually crosses the cut location and
142
-
* might not function correctly otherwise.
143
-
*
144
-
* This is a low level function, you should use cut_channel_node that wraps this up in a nicer API.
145
-
*/
140
+
* @brief Update a CHANY node's bounding box in RRGraph and SpatialLookup entries.
141
+
* This function assumes that the channel node actually crosses the cut location and
142
+
* might not function correctly otherwise.
143
+
*
144
+
* This is a low level function, you should use cut_channel_node that wraps this up in a nicer API.
145
+
*/
146
146
staticvoidcut_chan_y_node(RRNodeId node, int x_low, int y_low, int x_high, int y_high, int layer, int ptc_num, int cut_loc_y, Direction node_direction, RRGraphBuilder& rr_graph_builder, RRSpatialLookup& spatial_lookup) {
// Add 2D scatter-gather link edges (the nodes have already been created at this point). These links are mostly used for interposer-crossing connections, but could also be used for other things.
0 commit comments