
IBM3206K0424
Preliminary
IBM Processor for Network Resources
pnr25.chapt05.01
August 14, 2000
Cell/Packet Re-assembly (REASM)
Page 331 of 676
12.4: REASM Status Register
Used to surface REASM and sub-entity status. This register contains the status bits for the REASM
sub-entities. See
Note on Set/Clear Type Registers on page 93
for more details on addressing.
Length
32 bits
Type
Read/Write
Address
XXXX 1600 and 604
Power On Value
X
’
00000000
’
Restrictions
None
Reserved
R
B
R
B
R
R
R
R
R
R
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10
9
8
7
6
5
4
3
2
1
0
Bit(s)
Description
31-28
Reserved.
27
RXBUF cell buffer threshold exceeded. This bit is set when the number of receive cell buffers exceeds the threshold set
in RXBUF Receive Buffer Threshold. This bit is sticky and must be reset by software after being set.
26
Bad LCD receive offset detected. This bit is set when a receive LCD is used that does not have a good receive offset.
Either the receive offset does not allow for enough room for the configured packet header, or there is not enough room
for the DMA list entry that would have been written.
25
RXQUE deque state machine is locked. This bit is set when an RXQUE deque operation is attempted in order to get a
piece of user data for the DMA list and there is no data available. When using two pieces of data in a DMA list entry, both
must be available.
24
Bad LCD update operation. This bit is set when a receive LCD update was attempted on an offset that falls in the transmit
portion of the LCD, or when an LCD that is out of range is updated.
23-20
RXAAL nano status. These bits can be set from the RXAAL nano code. If they are used, they are documented in the
code load instructions (that is, aal.txt). They may or may not be used.
19-16
RXCRC nano status. These bits can be set from the RXCRC nano code. If they are used, they are documented in the
code load instructions (that is, crc.txt). They may or may not be used.
15-12
RXXLT drop 3 nano status. These bits can be set from the RXXLT nano code for drop 3. If they are used, they are docu-
mented in the code load instructions (that is, atm.txt). They may or may not be used.
11-8
RXXLT drop 2 nano status. These bits can be set from the RXXLT nano code for drop 2. If they are used, they are docu-
mented in the code load instructions (that is, atm.txt). They may or may not be used.
7-4
RXXLT drop 1 nano status. These bits can be set from the RXXLT nano code for drop 1. If they are used, they are docu-
mented in the code load instructions (that is, atm.txt). They may or may not be used.
3-0
RXXLT drop 0 nano status. These bits can be set from the RXXLT nano code for drop 0. If they are used, they are docu-
mented in the code load instructions (that is, atm.txt). They may or may not be used.