Searched +full:ethernet +full:- +full:switch (Results 1 – 25 of 922) sorted by relevance
12345678910>>...37
/Linux-v5.4/drivers/net/dsa/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 2 menu "Distributed Switch Architecture drivers" 8 tristate "Broadcom Starfighter 2 Ethernet switch support" 15 ---help--- 16 This enables support for the Broadcom Starfighter 2 Ethernet 17 switch chips. 20 tristate "DSA mock-up Ethernet switch chip support" 23 ---help--- 24 This enables support for a fake mock-up switch chip which 31 ---help--- [all …]
|
/Linux-v5.4/Documentation/networking/dsa/ |
D | dsa.rst | 5 This document describes the **Distributed Switch Architecture (DSA)** subsystem 13 The Distributed Switch Architecture is a subsystem which was primarily designed 14 to support Marvell Ethernet switches (MV88E6xxx, a.k.a Linkstreet product line) 19 they configured/queried a switch port network device or a regular network 22 An Ethernet switch is typically comprised of multiple front-panel ports, and one 24 presence of a management port connected to an Ethernet controller capable of 25 receiving Ethernet frames from the switch. This is a very common setup for all 26 kinds of Ethernet switches found in Small Home and Office products: routers, 27 gateways, or even top-of-the rack switches. This host Ethernet controller will 32 using upstream and downstream Ethernet links between switches. These specific [all …]
|
D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 DSA switch configuration from userspace 7 The DSA switch configuration is not integrated into the main userspace 10 .. _dsa-config-showcases: 13 ----------------------- 15 To configure a DSA switch a couple of commands need to be executed. In this 19 Every switch port acts as a different configurable Ethernet port 22 Every switch port is part of one configurable Ethernet bridge 25 Every switch port except one upstream port is part of a configurable 26 Ethernet bridge. [all …]
|
D | bcm_sf2.rst | 2 Broadcom Starfighter 2 Ethernet switch driver 5 Broadcom's Starfighter 2 Ethernet switch hardware block is commonly found and 8 - xDSL gateways such as BCM63138 9 - streaming/multimedia Set Top Box such as BCM7445 10 - Cable Modem/residential gateways such as BCM7145/BCM3390 12 The switch is typically deployed in a configuration involving between 5 to 13 13 ports, offering a range of built-in and customizable interfaces: 15 - single integrated Gigabit PHY 16 - quad integrated Gigabit PHY 17 - quad external Gigabit PHY w/ MDIO multiplexer [all …]
|
/Linux-v5.4/Documentation/devicetree/bindings/net/ |
D | keystone-netcp.txt | 5 Ethernet packets. NetCP has a gigabit Ethernet (GbE) subsystem with a ethernet 6 switch sub-module to send and receive packets. NetCP also includes a packet 12 Keystone II SoC's also have a 10 Gigabit Ethernet Subsystem (XGbE) which 13 includes a 3-port Ethernet switch sub-module capable of 10Gb/s and 1Gb/s rates 14 per Ethernet port. 16 Keystone NetCP driver has a plug-in module architecture where each of the NetCP 17 sub-modules exist as a loadable kernel module which plug in to the netcp core. 18 These sub-modules are represented as "netcp-devices" in the dts bindings. It is 19 mandatory to have the ethernet switch sub-module for the ethernet interface to 20 be operational. Any other sub-module like the PA is optional. [all …]
|
D | mdio-mux.txt | 1 Common MDIO bus multiplexer/switch properties. 3 An MDIO bus multiplexer/switch will have several child busses that are 5 bus multiplexer/switch will have one child node for each child bus. 8 - #address-cells = <1>; 9 - #size-cells = <0>; 12 - mdio-parent-bus : phandle to the parent MDIO bus. 14 - Other properties specific to the multiplexer/switch hardware. 17 - #address-cells = <1>; 18 - #size-cells = <0>; 19 - reg : The sub-bus number. [all …]
|
D | mscc-ocelot.txt | 1 Microsemi Ocelot network Switch 4 The Microsemi Ocelot network switch can be found on Microsemi SoCs (VSC7513, 8 - compatible: Should be "mscc,vsc7514-switch" 9 - reg: Must contain an (offset, length) pair of the register set for each 10 entry in reg-names. 11 - reg-names: Must include the following entries: 12 - "sys" 13 - "rew" 14 - "qs" 15 - "ptp" (optional due to backward compatibility) [all …]
|
D | hisilicon-hns-nic.txt | 4 - compatible: "hisilicon,hns-nic-v1" or "hisilicon,hns-nic-v2". 5 "hisilicon,hns-nic-v1" is for hip05. 6 "hisilicon,hns-nic-v2" is for Hi1610 and Hi1612. 7 - ae-handle: accelerator engine handle for hns, 9 see Documentation/devicetree/bindings/net/hisilicon-hns-dsaf.txt 10 - port-id: is the index of port provided by DSAF (the accelerator). DSAF can 16 In NIC mode of DSAF, all 6 PHYs are taken as ethernet ports to the CPU. The 17 port-id can be 2 to 7. Here is the diagram: 18 +-----+---------------+ 20 +-+-+-+---+-+-+-+-+-+-+ [all …]
|
D | ralink,rt2880-net.txt | 1 Ralink Frame Engine Ethernet controller 4 The Ralink frame engine ethernet controller can be found on Ralink and 8 directly and/or via a (gigabit-)switch. 10 * Ethernet controller node 13 - compatible: Should be one of "ralink,rt2880-eth", "ralink,rt3050-eth", 14 "ralink,rt3050-eth", "ralink,rt3883-eth", "ralink,rt5350-eth", 15 "mediatek,mt7620-eth", "mediatek,mt7621-eth" 16 - reg: Address and length of the register set for the device 17 - interrupts: Should contain the frame engines interrupt 18 - resets: Should contain the frame engines resets [all …]
|
D | mdio-mux-gpio.txt | 1 Properties for an MDIO bus multiplexer/switch controlled by GPIO pins. 8 - compatible : mdio-mux-gpio. 9 - gpios : GPIO specifiers for each GPIO line. One or more must be specified. 16 compatible = "cavium,octeon-3860-mdio"; 17 #address-cells = <1>; 18 #size-cells = <0>; 23 An NXP sn74cbtlv3253 dual 1-of-4 switch controlled by a 27 mdio-mux { 28 compatible = "mdio-mux-gpio"; 30 mdio-parent-bus = <&smi1>; [all …]
|
/Linux-v5.4/Documentation/infiniband/ |
D | opa_vnic.rst | 2 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) 5 Intel Omni-Path (OPA) Virtual Network Interface Controller (VNIC) feature 6 supports Ethernet functionality over Omni-Path fabric by encapsulating 7 the Ethernet packets between HFI nodes. 11 The patterns of exchanges of Omni-Path encapsulated Ethernet packets 12 involves one or more virtual Ethernet switches overlaid on the Omni-Path 13 fabric topology. A subset of HFI nodes on the Omni-Path fabric are 14 permitted to exchange encapsulated Ethernet packets across a particular 15 virtual Ethernet switch. The virtual Ethernet switches are logical 18 nodes across the fabric exchange encapsulated Ethernet packets over a [all …]
|
/Linux-v5.4/drivers/net/dsa/sja1105/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 3 tristate "NXP SJA1105 Ethernet switch family support" 9 This is the driver for the NXP SJA1105 automotive Ethernet switch 10 family. These are 5-port devices and are managed over an SPI 13 - SJA1105E (Gen. 1, No TT-Ethernet) 14 - SJA1105T (Gen. 1, TT-Ethernet) 15 - SJA1105P (Gen. 2, No SGMII, No TT-Ethernet) 16 - SJA1105Q (Gen. 2, No SGMII, TT-Ethernet) 17 - SJA1105R (Gen. 2, SGMII, No TT-Ethernet) 18 - SJA1105S (Gen. 2, SGMII, TT-Ethernet) [all …]
|
/Linux-v5.4/drivers/infiniband/ulp/opa_vnic/ |
D | opa_vnic_encap.h | 26 * - Redistributions of source code must retain the above copyright 28 * - Redistributions in binary form must reproduce the above copyright 32 * - Neither the name of Intel Corporation nor the names of its 52 * and decapsulation of Ethernet packets 63 * ETHERNET MANAGEMENT 84 #define OPA_VNIC_EMA_DATA (OPA_MGMT_MAD_SIZE - IB_MGMT_VENDOR_HDR) 102 /* VNIC Ethernet link status */ 118 * struct opa_vesw_info - OPA vnic switch information 119 * @fabric_id: 10-bit fabric id 120 * @vesw_id: 12-bit virtual ethernet switch id [all …]
|
/Linux-v5.4/drivers/staging/fsl-dpaa2/ethsw/ |
D | README | 1 DPAA2 Ethernet Switch driver 4 This file provides documentation for the DPAA2 Ethernet Switch driver 11 Creating an Ethernet Switch 23 The Ethernet Switch in the DPAA2 architecture consists of several hardware 31 drivers/staging/fsl-mc/README.txt 33 The Ethernet Switch is built on top of a Datapath Switch (DPSW) object. 37 --------------------- 38 | DPAA2 Switch driver | 39 --------------------- 42 ---------- [all …]
|
/Linux-v5.4/Documentation/devicetree/bindings/net/dsa/ |
D | vitesse,vsc73xx.txt | 4 This defines device tree bindings for the Vitesse VSC73xx switch chips. 8 The currently supported switch chips are: 9 Vitesse VSC7385 SparX-G5 5+1-port Integrated Gigabit Ethernet Switch 10 Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch 11 Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch 12 Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch 14 This switch could have two different management interface. 17 reside inside a SPI bus device tree node, see spi/spi-bus.txt 19 When the chip is connected to a parallel memory bus and work in memory-mapped 25 - compatible: must be exactly one of: [all …]
|
D | b53.txt | 1 Broadcom BCM53xx Ethernet switches 6 - compatible: For external switch chips, compatible string must be exactly one 18 "brcm,bcm11360-srab" and the mandatory "brcm,cygnus-srab" string 20 For the BCM5310x SoCs with an integrated switch, must be one of: 21 "brcm,bcm53010-srab" 22 "brcm,bcm53011-srab" 23 "brcm,bcm53012-srab" 24 "brcm,bcm53018-srab" 25 "brcm,bcm53019-srab" and the mandatory "brcm,bcm5301x-srab" string 27 For the BCM5831X/BCM1140x SoCs with an integrated switch, must be one of: [all …]
|
D | dsa.txt | 1 Distributed Switch Architecture Device Tree Bindings 2 ---------------------------------------------------- 12 - ports : A container for child nodes representing switch ports. 16 - dsa,member : A two element list indicates which DSA cluster, and position 17 within the cluster a switch takes. <0 0> is cluster 0, 18 switch 0. <0 1> is cluster 0, switch 1. <1 0> is cluster 1, 19 switch 0. A switch not part of any cluster (single device 26 - #address-cells : Must be 1 27 - #size-cells : Must be 0 30 - reg : Describes the port address in the switch [all …]
|
D | lantiq-gswip.txt | 1 Lantiq GSWIP Ethernet switches 6 - compatible : "lantiq,xrx200-gswip" for the embedded GSWIP in the 8 - reg : memory range of the GSWIP core registers 17 - compatible : "lantiq,xrx200-mdio" for the MDIO bus inside the GSWIP 25 - compatible : "lantiq,xrx200-gphy-fw", "lantiq,gphy-fw" 26 "lantiq,xrx300-gphy-fw", "lantiq,gphy-fw" 27 "lantiq,xrx330-gphy-fw", "lantiq,gphy-fw" 30 - lantiq,rcu : reference to the rcu syscon 35 - reg : Offset of the GPHY firmware register in the RCU 37 - resets : list of resets of the embedded GPHY [all …]
|
D | mt7530.txt | 1 Mediatek MT7530 Ethernet switch 6 - compatible: may be compatible = "mediatek,mt7530" 8 - #address-cells: Must be 1. 9 - #size-cells: Must be 0. 10 - mediatek,mcm: Boolean; if defined, indicates that either MT7530 is the part 11 on multi-chip module belong to MT7623A has or the remotely standalone 16 - core-supply: Phandle to the regulator node necessary for the core power. 17 - io-supply: Phandle to the regulator node necessary for the I/O power. 18 See Documentation/devicetree/bindings/regulator/mt6323-regulator.txt 23 - reset-gpios: Should be a gpio specifier for a reset line. [all …]
|
D | lan9303.txt | 1 SMSC/MicroChip LAN9303 three port ethernet switch 2 ------------------------------------------------- 6 - compatible: should be 7 - "smsc,lan9303-i2c" for I2C managed mode 9 - "smsc,lan9303-mdio" for mdio managed mode 13 - reset-gpios: GPIO to be used to reset the whole device 14 - reset-duration: reset duration in milliseconds, defaults to 200 ms 18 The integrated switch subnode should be specified according to the binding 19 described in dsa/dsa.txt. The CPU port of this switch is always port 0. 23 auto-detected and mapped accordingly. [all …]
|
D | ksz.txt | 1 Microchip KSZ Series Ethernet switches 6 - compatible: For external switch chips, compatible string must be exactly one 8 - "microchip,ksz8765" 9 - "microchip,ksz8794" 10 - "microchip,ksz8795" 11 - "microchip,ksz9477" 12 - "microchip,ksz9897" 13 - "microchip,ksz9896" 14 - "microchip,ksz9567" 15 - "microchip,ksz8565" [all …]
|
/Linux-v5.4/drivers/net/ethernet/ti/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 10 ---help--- 11 If you have a network (Ethernet) card belonging to this class, say Y. 25 ---help--- 26 This driver supports TI's DaVinci Ethernet . 35 ---help--- 44 ---help--- 49 tristate "TI CPSW Switch Support" 55 ---help--- 56 This driver supports TI's CPSW Ethernet Switch. [all …]
|
/Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 15 ---help--- 16 Core driver for low level functionality of the ConnectX-4 and 17 Connect-IB cards by Mellanox Technologies. 26 ---help--- 31 sandbox-specific client drivers. 34 bool "Mellanox 5th generation network adapters (ConnectX series) Ethernet support" 35 depends on NETDEVICES && ETHERNET && INET && PCI && MLX5_CORE 39 ---help--- 40 Ethernet support in Mellanox Technologies ConnectX-4 NIC. [all …]
|
/Linux-v5.4/arch/arm/boot/dts/ |
D | orion5x-netgear-wnr854t.dts | 9 /dts-v1/; 11 #include <dt-bindings/gpio/gpio.h> 12 #include <dt-bindings/input/input.h> 13 #include "orion5x-mv88f5181.dtsi" 16 model = "Netgear WNR854-t"; 17 compatible = "netgear,wnr854t", "marvell,orion5x-88f5181", 29 stdout-path = "serial0:115200n8"; 38 gpio-keys { 39 compatible = "gpio-keys"; 40 pinctrl-0 = <&pmx_reset_button>; [all …]
|
/Linux-v5.4/drivers/net/ethernet/sun/ |
D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0 10 ---help--- 11 If you have a network (Ethernet) card belonging to this class, say Y. 24 ---help--- 37 ---help--- 39 This is Sun's older 100baseT Ethernet device. 48 ---help--- 49 This driver supports the "qe" 10baseT Ethernet device, available as 61 ---help--- 63 <http://docs.oracle.com/cd/E19455-01/806-3985-10/806-3985-10.pdf>. [all …]
|
12345678910>>...37