
TABLE 4-11 Read-Only  Link Partner Capabilities (Continued)
| Parameter | Description | |
| 
 | 
 | 
 | 
| lp_cap_10hdx | 0 | = No 10 Mbit/sec  | 
| 
 | 1 | = 10 Mbit/sec  | 
| lp_cap_asm_pause | 0 | = Not asymmetric pause capable | 
| 
 | 1 | = Asymmetric pause towards link partner capability | 
| lp_cap_pause | 0 | = Not symmetric pause capable | 
| 
 | 1 | = Symmetric pause capable | 
| 
 | 
 | 
 | 
If the link partner is not capable of autonegotiation (when lp_autoneg_cap is 0),
the remaining information described in is not relevant and the parameter value = 0.
If the link partner is capable of autonegotiation (when lp_autoneg_cap is 1), then the speed and mode information is displayed when you use autonegotiation and the link partner capabilities.
TABLE 
TABLE 4-12 Transmit and Receive Parameters
| Parameter | Description | 
| 
 | 
 | 
| 
 | Number of Physical layer  | 
| xcvr_inits | link parameters using NDD this increments. | 
| rev_id | Revision ID of the GigaSwift Ethernet device useful for recognition | 
| 
 | of device being used in the field. | 
| xcvr_addr | GMII/MII Physical layer device address for management interface. | 
| xcvr_id | GMII/MII Physical layer device Identification Decimal copy of MII | 
| 
 | registers 2 and 3. | 
| lb_mode | Copy of the Loopback mode the device is in, if any. | 
| qos_mode | When zero, the TX queues operate in a simple round robin | 
| 
 | queueing scheme, based on TCP/UDP destination port number. If | 
| 
 | set the TX queues operate in a scheme designed to provide VLAN | 
| 
 | priorities. | 
| tx_starts | Number of times that the driver attempted to transmit a packet. | 
tx_dma_bind_fail Number of times a page table entry was not available to allow the driver to map the kernel memory to device accessible memory for
| 
 | transmission. | 
| tx_queue0 | Number of packets queued for transmission on the first hardware | 
| 
 | transmit queue. | 
| 
 | 
 | 
Chapter 4 Configuring Driver Parameters 41