Lines Matching refs:carrier
494 asserting carrier. It is similar to the Cisco EtherChannel min-links
497 (carrier on). This is useful for situations where higher level services
502 The default value is 0. This will cause carrier to be asserted (for
788 "carrier on," so if a driver does not support netif_carrier,
1676 TX packets:3286647 errors:1 dropped:0 overruns:1 carrier:0
1682 TX packets:1643167 errors:1 dropped:0 overruns:1 carrier:0
1689 TX packets:1643480 errors:0 dropped:0 overruns:0 carrier:0
1832 The MII monitor monitors only the carrier state of the local
1834 depending upon the device driver to maintain its carrier state, by
1839 then the MII monitor will rely on the driver for carrier state
1842 detect carrier loss on the device (e.g., when the cable is physically
1848 request fails (not just that it returns carrier down), then the MII
1941 instructs bonding to trust the driver to maintain carrier state.
1954 it does, then it may be that the driver checks the carrier state at a
1961 carrier state. It has no way to determine the state of devices on or
1963 traffic while still maintaining carrier on.
2418 the link is up (carrier available), but not pass traffic over the
2638 above). In general, miimon monitors the carrier state as sensed by