AMD
P R E L I M I N A R Y
172
Am79C965
time.
BUFF
is
set
by
the
PCnet-32 controller and cleared
by the host.
25
STP
START OF PACKET indicates
that this is the first buffer used by
the PCnet-32 controller for this
frame. It is used for data chaining
buffers. STP is set by the
PCnet-32 controller and cleared
by the host.
24
ENP
END OF PACKET indicates that
this is the last buffer used by the
PCnet-32
controller
for
this
frame. It is used for data chaining
buffers. If both STP and ENP are
set, the frame fits not one buffer
and there is no data chaining.
ENP is set by the PCnet-32 con-
troller and cleared by the host.
23-16
RES
Reserved locations. These loca-
tions should be read and written
as ZEROs.
15-12 ONES
These four bits must be written
as ONES. They are written by the
host and unchanged by the
PCnet-32 controller.
11-0
BCNT
BUFFER BYTE COUNT is the
length of the buffer pointed to by
this descriptor, expressed as the
two’s complement of the length
of the buffer. This field is written
by the host and unchanged by
the PCnet-32 controller.
RMD2
Bit
Name
Description
31-24
RCC
Receive Collision Count. Indi-
cates the accumulated number of
collisions on the network since
the last frame was successfully
received,
excluding
collisions
that occurred during transmis-
sions
from
this
node.
The
PCnet-32 controller implementa-
tion of this counter may not be
compatible with the ILACC RCC
definition. If network statistics are
to be monitored, then CSR114
should be used for the purpose of
monitoring Receive collisions in-
stead of these bits.
23-16
RPC
Runt Packet Count. Indicates the
accumulated number of runts
that were addressed to this node
since the last time that a receive
packet
was
successfully
re-
ceived and its corresponding
RMD2 ring entry was written to
by the PCnet-32 controller. In or-
der to be included in the RPC
value, a runt must be long
enough to meet the minimum re-
quirement of the internal address
matching logic. The minimum re-
quirement for a runt to pass the
internal
address
matching
mechanism is: 18 bits of valid
preamble plus a valid SFD de-
tected, followed by 7 bytes of
frame data. This requirement is
unvarying, regardless of the ad-
dress matching mechanisms in
force at the time of reception (i.e.
physical, logical, broadcast or
promiscuous).
The
PCnet-32
controller implementation of this
counter may not be compatible
with the ILACC RPC definition.
15-12 ZEROs
This field is reserved. PCnet-32
controller will write ZEROs to
these locations.
11-0
MCNT
MESSAGE Byte COUNT is the
length in bytes of the received
message, expressed as an un-
signed binary integer. MCNT is
valid only when ERR is clear and
ENP is set. MCNT is written by
the
PCnet-32
controller
and
cleared by the host.
RMD3
Bit
Name
Description
31-0
RES
Reserved locations. All bits must
be ZEROs.