| /linux/drivers/net/dsa/sja1105/ |
| H A D | sja1105_ethtool.c | 92 .area = MAC, 99 .area = MAC, 106 .area = MAC, 113 .area = MAC, 121 .area = MAC, 128 .area = MAC, 135 .area = MAC, 142 .area = MAC, 149 .area = MAC, 156 .area = MAC, [all …]
|
| /linux/Documentation/networking/ |
| H A D | oa-tc6-framework.rst | 4 OPEN Alliance 10BASE-T1x MAC-PHY Serial Interface (TC6) Framework Support 29 The MAC-PHY solution integrates an IEEE Clause 4 MAC and a 10BASE-T1x PHY 32 to existing low-end microcontrollers which do not integrate a MAC 38 The MAC-PHY is specified to carry both data (Ethernet frames) and control 54 low to the MAC-PHY and ends with the deassertion of CSn high. In between 78 10BASE-T1x MAC-PHY Serial Interface Specification, 88 | | | MAC-PHY | 90 | SPI Host | | | SPI Slave | | MAC | | PHY | | 107 | MAC Driver |<--->| OPEN Alliance TC6 Framework | 121 | 10BASE-T1x MAC-PHY Device | [all …]
|
| H A D | sfp-phylink.rst | 11 directly connected to a MAC without needing to re-initialise the 26 the PHY, and pass them to the MAC driver. We expect the MAC driver 32 Fixed mode is the same as PHY mode as far as the MAC driver is 64 to the MAC through the SGMII control word, and the MAC is expected to 66 :c:func:`mac_link_down` functions must not force the MAC side link 82 link-up part now includes configuring the MAC for the link settings. 176 This function is replaced by a different form of MAC updates 186 Finally, note that the MAC driver has no direct access to the PHY 204 return the phylink MAC capabilities that are supported for the passed 211 from the MAC, and report back the settings that the MAC is currently [all …]
|
| H A D | phy-link-topology.rst | 21 | MAC | ------ | PHY | ---- | Port | ---... to LP 31 Here, we have 2 basic scenarios. Either the MAC is able to output a serialized 38 | MAC | ------- | SFP Module | 44 | MAC | -------- | PHY (on SFP) | 52 as media-converters, to translate the non-serialized MAC MII interface to a 56 | MAC | ------- | PHY (media converter) | ------- | PHY (on SFP) |
|
| /linux/Documentation/translations/zh_CN/networking/ |
| H A D | timestamping.rst | 564 包含自己的时间戳时钟,并具有在自身 MAC上执行网络时间戳的能力,因此路径延迟 578 的数据包之前调用的钩子。这是必需的,因为硬件时间戳在实际 MAC 传输后才可 612 的 MAC驱动程序进行中介。因此,与 DSA 交换机不同,需要对每个单独的 MAC 驱动 616 为真或假。如果是,则 MAC 驱动程序不应处理此请求,而应将其传递给 PHY 使用 620 在 plain ``netif_rx()`` 和类似情况下,MAC 驱动程序必须检查是否 633 况下,确实需要显式 MAC 驱动程序支持),但函数也 piggybacks 从 634 ``skb_tx_timestamp()`` 调用,许多 MAC 驱动程序已经为软件时间戳目的执行。 635 因此,如果 MAC 支持软件时间戳,则它不需要在此阶段执行任何其他操作。 646 3.2.4 MAC 驱动程序的其他注意事项 649 堆叠 PHC 可能会暴露 MAC 驱动程序的错误,这些错误在未堆叠 PHC 时无法触发。一个 [all …]
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | fujitsu_uncore_pmu.rst | 7 This driver supports the Uncore MAC PMUs and the Uncore PCI PMUs found 9 Each MAC PMU on these chips is exposed as a uncore perf PMU with device name 29 This driver supports the following events for MAC: 32 This event counts MAC cycles at MAC frequency. 34 This event counts the number of read requests to MAC. 36 This event counts the number of read requests including retry to MAC. 38 This event counts the number of responses to read requests to MAC. 55 This event counts the number of write requests to MAC (including zero write, 58 This event counts the number of full write requests to MAC (not including 61 This event counts the number of partial write requests to MAC. [all …]
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | hisilicon-femac.txt | 1 Hisilicon Fast Ethernet MAC controller 9 The first region is the MAC core register base and size. 10 The second region is the global MAC control register. 11 - interrupts: should contain the MAC interrupt. 12 - clocks: A phandle to the MAC main clock. 13 - resets: should contain the phandle to the MAC reset signal(required) and 24 The MAC address will be determined using the optional properties
|
| H A D | qcom-emac.txt | 3 This network controller consists of two devices: a MAC and an SGMII 5 connects the MAC node to its corresponding internal phy node. Another 10 MAC node: 14 - mac-address : The 6-byte MAC address. If present, it is the default 15 MAC address.
|
| H A D | hisilicon-hix5hd2-gmac.txt | 14 The first region is the MAC register base and size. 16 - interrupts: should contain the MAC interrupt. 23 - resets: should contain the phandle to the MAC core reset signal(optional), 24 the MAC interface reset signal(optional) 33 The MAC address will be determined using the properties defined in
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A D | mac-phy-support.rst | 5 DPAA2 MAC / PHY support 13 The DPAA2 MAC / PHY support consists of a set of APIs that help DPAA2 network 20 network interface) and DPMAC objects (abstracting a MAC). The dpaa2-eth driver 54 | MC firmware polling MAC PCS for link | 62 Depending on an MC firmware configuration setting, each MAC may be in one of two modes: 65 the MC firmware by polling the MAC PCS. Without the need to register a 88 - .validate() will populate the supported linkmodes with the MAC capabilities 92 - .mac_config() will configure the MAC in the new configuration using the 95 - .mac_link_up() / .mac_link_down() will update the MAC link using the same 107 (3) In order to configure the HW MAC, the MC Firmware API [all …]
|
| /linux/Documentation/firmware-guide/acpi/dsd/ |
| H A D | phy.rst | 14 for connecting PHYs on the MDIO bus [dsd-properties-rules] to the MAC layer. 23 For each MAC node, a device property "phy-handle" is used to reference 25 network interfaces that have PHYs connected to MAC via MDIO bus. 43 Later, during the MAC driver initialization, the registered PHY devices 44 have to be retrieved from the MDIO bus. For this, the MAC driver needs 61 MAC port, which is linked in the _DSD package via 115 DSDT entries representing MAC nodes 118 Below are the MAC nodes where PHY nodes are referenced. 146 MAC node example where "managed" property is specified. 162 MAC node example with a "fixed-link" subnode.
|
| /linux/net/bridge/netfilter/ |
| H A D | Kconfig | 92 The ebtables nat table is used to define rules that alter the MAC 93 source address (MAC SNAT) or the MAC destination address (MAC DNAT). 110 This option adds the among match, which allows matching the MAC source 112 MAC/IP address pairs can be matched, f.e. for anti-spoofing rules. 201 This option adds the MAC DNAT target, which allows altering the MAC 219 This option adds the MAC redirect target, which allows altering the MAC 227 This option adds the MAC SNAT target, which allows altering the MAC
|
| /linux/Documentation/networking/device_drivers/ethernet/stmicro/ |
| H A D | stmmac.rst | 27 Currently, this network device driver is for all STi embedded MAC/GMAC 32 DesignWare(R) Cores Ethernet MAC 10/100/1000 Universal version 3.70a 35 DesignWare(R) Cores XGMAC - 10G Ethernet MAC and DesignWare(R) Cores 36 Enterprise MAC - 100G Ethernet MAC. 46 | Ethernet MAC Universal | N/A | 3.73a | GMAC | 50 | XGMAC - 10G Ethernet MAC | 2.10a | N/A | XGMAC2+ | 52 | XLGMAC - 100G Ethernet MAC | 2.00a | N/A | XLGMAC2+ | 71 - MAC Loopback 233 tested on DesignWare(R) Cores Ethernet MAC Universal version 3.41a and later. 263 checks to the HW using MAC and PHY loopback mechanisms:: [all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-intel-m10-bmc | 21 Description: Read only. Returns the first MAC address in a block 22 of sequential MAC addresses assigned to the board 32 Description: Read only. Returns the number of sequential MAC
|
| H A D | configfs-usb-gadget-ncm | 11 host_addr - MAC address of host's end of this 13 dev_addr - MAC address of device's end of this
|
| H A D | configfs-usb-gadget-ecm | 14 - MAC address of host's end of this 17 - MAC address of device's end of this
|
| H A D | configfs-usb-gadget-eem | 12 host_addr MAC address of host's end of this 14 dev_addr MAC address of device's end of this
|
| H A D | configfs-usb-gadget-subset | 12 host_addr MAC address of host's end of this 14 dev_addr MAC address of device's end of this
|
| H A D | configfs-usb-gadget-rndis | 12 host_addr MAC address of host's end of this 14 dev_addr MAC address of device's end of this
|
| /linux/drivers/net/ethernet/aeroflex/ |
| H A D | Kconfig | 7 tristate "Aeroflex Gaisler GRETH Ethernet MAC support" 12 Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
|
| /linux/Documentation/leds/ |
| H A D | well-known-leds.txt | 86 the PHY and those by the MAC. In theory both can be present at the 88 MAC and PHY. 91 and are not unique. They also don't differentiate between MAC and PHY. 93 ** MAC LEDs 99 The first part must uniquely name the MAC controller. Then follows the
|
| /linux/drivers/net/ethernet/wiznet/ |
| H A D | Kconfig | 26 W5100 is a single chip with integrated 10/100 Ethernet MAC, 28 the MAC and PHY functions only, onchip TCP/IP is unused. 39 W5300 is a single chip with integrated 10/100 Ethernet MAC, 41 the MAC and PHY functions only, onchip TCP/IP is unused.
|
| /linux/drivers/net/ethernet/altera/ |
| H A D | Kconfig | 3 tristate "Altera Triple-Speed Ethernet MAC support" 12 This driver supports the Altera Triple-Speed (TSE) Ethernet MAC.
|
| /linux/drivers/net/ethernet/nxp/ |
| H A D | Kconfig | 3 tristate "NXP ethernet MAC on LPC devices" 8 Say Y or M here if you want to use the NXP ethernet MAC included on
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | iavf.rst | 110 - 1 unicast MAC address reserved per VF 111 - 16 MAC address filters for each VF 228 If the MAC address of the VF is set by the PF (Physical Function) of the 230 tries to sync the backup slave's MAC address to the same MAC address as the 232 if the VF's MAC address is not set by the PF. 243 section "MAC and VLAN anti-spoofing feature" in this readme document. 277 MAC address of Virtual Function changes unexpectedly 279 If a Virtual Function's MAC address is not assigned in the host, then the VF 280 (virtual function) driver will use a random MAC address. This random MAC 282 MAC address in the host machine. This static MAC address will survive
|