21150-AB

Manufacturer Part Number21150-AB
DescriptionCommunications, Transparent PCI-to-PCI Bridge
ManufacturerIntel Corporation
21150-AB datasheet
 

Specifications of 21150-AB

CaseQFP  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
Page 61
62
Page 62
63
Page 63
64
Page 64
65
Page 65
66
Page 66
67
Page 67
68
Page 68
69
Page 69
70
Page 70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
Page 61/164:

Target Retry

Download datasheet (812Kb)Embed
PrevNext
After the 21150 makes 2
21150 asserts p_serr_l if the primary SERR# enable bit is set in the command register and the
implementation-specific p_serr_l disable bit for this condition is not set in the p_serr_l event
disable register. The 21150 stops initiating transactions in response to that delayed read transaction.
The delayed read request is discarded. Upon a subsequent read transaction attempt by the initiator,
the 21150 returns a target abort. See
4.8.4
Target Termination Initiated by the 21150
The 21150 can return a target retry, target disconnect, or target abort to an initiator for reasons other
than detection of that condition at the target interface.
4.8.4.1

Target Retry

The 21150 returns a target retry to the initiator when it cannot accept write data or return read data
as a result of internal conditions. The 21150 returns a target retry to an initiator when any of the
following conditions is met:
For delayed write transactions:
— The transaction is being entered into the delayed transaction queue.
— The transaction has already been entered into the delayed transaction queue, but target
response has not yet been received.
— Target response has been received but has not progressed to the head of the return queue.
— The delayed transaction queue is full, and the transaction cannot be queued.
— A transaction with the same address and command has been queued.
— A locked sequence is being propagated across the 21150, and the write transaction is not a
locked transaction.
For delayed read transactions:
— The transaction is being entered into the delayed transaction queue.
— The read request has already been queued, but read data is not yet available.
— Data has been read from the target, but it is not yet at the head of the read data queue, or a
posted write transaction precedes it.
— The delayed transaction queue is full, and the transaction cannot be queued.
— A delayed read request with the same address and bus command has already been queued.
— A locked sequence is being propagated across the 21150, and the read transaction is not a
locked transaction.
— The 21150 is currently discarding previously prefetched read data.
For posted write transactions:
— The posted write data buffer does not have enough space for address and at least 8 Dwords
of write data.
— A locked sequence is being propagated across the 21150, and the write transaction is not a
locked transaction.
Preliminary
Datasheet
24
attempts of the same delayed read transaction on the target bus, the
Section 7.4
for a description of system error conditions.
21150
53