Lines Matching +full:tx +full:- +full:device

8 dmfe \- Davicom Fast Ethernet driver for Davicom DM9102A
18 The \fBdmfe\fR Ethernet device provides 100Base-TX networking interfaces using
28 The 100Base-TX standard specifies an auto-negotiation protocol to automatically
30 performing auto-negotiation with the remote-end of the link (link partner) and
33 also supports a forced-mode of operation under which the driver selects the
38 The \fB/dev/dmfe\fR cloning character-special device is used to access all
43 with a particular device (ppa). The ppa ID is interpreted as an unsigned
44 integer data type and indicates the corresponding device instance (unit)
45 number. If the ppa field value does not correspond to a valid device instance
46 number for this system, an error (DL_ERROR_ACK) is returned. The device is
47 initialized on first attach and de-initialized (stopped) at last detach.
56 Maximum SDU is 1500 (ETHERMTU - defined in \fBsys/ethernet.h\fR).
80 The sap length value is -2, meaning the physical address component is
81 followed immediately by a 2-byte sap component within the DLSAP address.
97 By default, the \fBdmfe\fR driver performs auto-negotiation to select the speed
98 and mode of the link. Link speed and mode can be 100 Mbps (full or half-duplex)
99 or 10 Mbps (full or half-duplex) as described in the 100Base-TX standard.
102 The auto-negotiation protocol automatically selects speed mode (either 100 Mbps
103 or 10 Mbps) and operation mode (either full-duplex or half-duplex) as the
105 \fBdmfe\fR device supports all modes, this effectively selects the
106 highest-throughput mode supported by the other device.
112 operate at the specified speed. Additionally, you can set the full-duplex
113 parameter to 0 or 1 to disable or force full-duplex operation, respectively.
116 Note that specifying either "speed" or "full-duplex" explicitly disables
117 auto-negotiation. To enable the driver to determine the appropriate setting for
120 device is connected to an ancient device or hub that does not support
121 auto-negotiation), both parameters should be explicitly specified to match the
122 requirements of the external device.
130 Character special device
139 32-bit kernel module (x86)
148 64-bit kernel module (SPARC)
157 64-bit kernel module (x86)
194 \fIWriting Device Drivers\fR