lan9116 Standard Microsystems Corp., lan9116 Datasheet - Page 45

• Manufacturer Part Number: lan9116
• Description: Lan9116 Highly Efficient Single-chip 10/100 Non-pci Ethernet Controller
• Manufacturer: Standard Microsystems Corp.

Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller
Datasheet
SMSC LAN9116
3.12.1
3.12.2
TX Buffer Format
TX buffers exist in the host’s memory in a given format. The host writes a TX command word into the
TX data buffer before moving the Ethernet packet data. The TX command A and command B are 32-
bit values that are used by the LAN9116 in the handling and processing of the associated Ethernet
packet data buffer. Buffer alignment, segmentation and other packet processing parameters are
included in the command structure. The following diagram illustrates the buffer format.
Figure 3.13, "TX Buffer Format", shows the TX Buffer as it is written into the LAN9116. It should be
noted that not all of the data shown in this diagram is actually stored in the TX data FIFO. This must
be taken into account when calculating the actual TX data FIFO usage. Please refer to
"Calculating Actual TX Data FIFO Usage," on page 49
actual TX data FIFO usage.
TX Command Format
The TX command instructs the TX FIFO controller on handling the subsequent buffer. The command
precedes the data to be transmitted. The TX command is divided into two, 32-bit words; TX command
‘A’ and TX command ‘B’.
There is a 16-bit packet tag in the TX command ‘B’ command word. Packet tags may, if host software
desires, be unique for each packet (i.e., an incrementing count). The value of the tag will be returned
in the RX status word for the associated packet. The Packet tag can be used by host software to
uniquely identify each status word as it is returned to the host.
Host Write
Order
2nd
3rd
Last
1st
Figure 3.13 TX Buffer Format
31
DATASHEET
Offset + Data DWORD0
Optional offset DWORDn
Optional offset DWORD0
Optional Pad DWORD0
Optional Pad DWORDn
TX Command 'A'
TX Command 'B'
Last Data & PAD
45
.
.
.
.
.
.
.
.
.
.
.
for a detailed explanation on calculating the
0
Revision 1.5 (07-11-08)
Section 3.12.5,