| /linux/net/l2tp/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # Layer Two Tunneling Protocol (L2TP)
7 tristate "Layer Two Tunneling Protocol (L2TP)"
12 Layer Two Tunneling Protocol
18 possible to both end-users and applications.
54 Layer Two Tunneling Protocol Version 3
58 The Layer Two Tunneling Protocol (L2TP) provides a dynamic
60 packet-oriented data network (e.g., over IP). L2TP, as
62 tunneling Point-to-Point Protocol (PPP) [RFC1661] sessions.
65 ethernet frames.
[all …]
|
| /linux/drivers/usb/gadget/legacy/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
23 # Gadget drivers are hardware-neutral, or "platform independent",
44 Gadget Zero is a two-configuration device. It either sinks and
47 conformance. The driver needs only two bulk-capable endpoints, so
[all …]
|
| /linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-jaguar-ethernet-switch.dtso | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
5 * Device Tree Overlay for the Ethernet Switch adapter for the Mezzanine
7 * (manual: https://embedded.cherry.de/jaguar-ethernet-switch-user-manual/)
9 * This adapter has a KSZ9896 Ethernet Switch with 4 1GbE Ethernet connectors,
10 * two user controllable LEDs, and an M12 12-pin connector which exposes the
12 * - RS232/RS485 (max 250Kbps/500Kbps, RX pin1, TX pin2)
13 * - two digital inputs (pin4 routed to GPIO3_C5 on SoC, pin5 to GPIO4_B4)
14 * - two digital outputs (pin7 routed to GPIO3_D3 on SoC, pin8 to GPIO3_D1)
15 * - two analog inputs (pin10 to channel1 of ADS1015, pin11 to channel2)
17 * RK3588 Jaguar can be powered entirely through the adapter via the M8 3-pin
[all …]
|
| /linux/Documentation/infiniband/ |
| H A 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/net/hsr/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 # IEC 62439-3 High-availability Seamless Redundancy
7 tristate "High-availability Seamless Redundancy (HSR & PRP)"
9 This enables IEC 62439 defined High-availability Seamless
15 needs (at least) two physical Ethernet interfaces.
18 with other HSR capable nodes. All Ethernet frames sent over the HSR
20 ports), giving a redundant, instant fail-over network. Each HSR node
24 For DANP, it must be connected as a node connecting to two
25 separate networks over the two slave interfaces. Like HSR, Ethernet
27 a redundant, instant fail-over network. Unlike HSR, PRP networks
[all …]
|
| /linux/Documentation/networking/dsa/ |
| H A D | lan9303.rst | 2 LAN9303 Ethernet switch driver
5 The LAN9303 is a three port 10/100 Mbps ethernet switch with integrated phys for
6 the two external ethernet ports. The third port is an RMII/MII interface to a
20 At startup the driver configures the device to provide two separate network
36 - Support for VLAN filtering is not implemented
37 - The HW does not support VLAN-specific fdb entries
|
| /linux/Documentation/devicetree/bindings/net/dsa/ |
| H A D | dsa.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Ethernet Switch
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Vladimir Oltean <olteanv@gmail.com>
15 This binding represents Ethernet Switches which have a dedicated CPU
16 port. That port is usually connected to an Ethernet Controller of the
21 $ref: /schemas/net/ethernet-switch.yaml#
[all …]
|
| H A D | vitesse,vsc73xx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
13 The Vitesse DSA Switches were produced in the early-to-mid 2000s.
19 Vitesse VSC7385 SparX-G5 5+1-port Integrated Gigabit Ethernet Switch
20 Vitesse VSC7388 SparX-G8 8-port Integrated Gigabit Ethernet Switch
21 Vitesse VSC7395 SparX-G5e 5+1-port Integrated Gigabit Ethernet Switch
22 Vitesse VSC7398 SparX-G8e 8-port Integrated Gigabit Ethernet Switch
24 This switch can use one of two different management interfaces.
[all …]
|
| /linux/Documentation/networking/pse-pd/ |
| H A D | pse-pi.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 the architecture of Power over Ethernet (PoE) systems. It is essentially a
9 eight-pin modular jack, commonly known as the Ethernet RJ45 port. This
11 over Ethernet cables.
14 ---------------------------
19 - Section "33.2.3 PI pin assignments" covers the pin assignments for PoE
20 systems that utilize two pairs for power delivery.
21 - Section "145.2.4 PSE PI" addresses the configuration for PoE systems that
22 deliver power over all four pairs of an Ethernet cable.
24 PSE PI and Single Pair Ethernet
[all …]
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | adi,adin1110.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ADI ADIN1110 MAC-PHY
10 - Marcelo Schmitt <marcelo.schmitt@analog.com>
13 The ADIN1110 is a low power single port 10BASE-T1L MAC-
14 PHY designed for industrial Ethernet applications. It integrates
15 an Ethernet PHY core with a MAC and all the associated analog
18 The ADIN2111 is a low power, low complexity, two-Ethernet ports
19 switch with integrated 10BASE-T1L PHYs and one serial peripheral
[all …]
|
| H A D | ti,k3-am654-cpsw-nuss.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/ti,k3-am654-cpsw-nuss.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: The TI AM654x/J721E/AM642x SoC Gigabit Ethernet MAC (Media Access Controller)
10 - Siddharth Vadapalli <s-vadapalli@ti.com>
11 - Roger Quadros <rogerq@kernel.org>
14 The TI AM654x/J721E SoC Gigabit Ethernet MAC (CPSW2G NUSS) has two ports
15 (one external) and provides Ethernet packet communication for the device.
16 The TI AM642x SoC Gigabit Ethernet MAC (CPSW3G NUSS) has three ports
[all …]
|
| H A D | marvell-orion-net.txt | 1 Marvell Orion/Discovery ethernet controller
4 The Marvell Discovery ethernet controller can be found on Marvell Orion SoCs
8 The Discovery ethernet controller is described with two levels of nodes. The
9 first level describes the ethernet controller itself and the second level
10 describes up to 3 ethernet port nodes within that controller. The reason for
12 set of controller registers. Each port node describes port-specific properties.
16 only one port associated. Multiple ports are implemented as multiple single-port
20 * Ethernet controller node
23 - #address-cells: shall be 1.
24 - #size-cells: shall be 0.
[all …]
|
| H A 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 …]
|
| H A D | cortina,gemini-ethernet.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/cortina,gemini-ethernet.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Cortina Systems Gemini Ethernet Controller
10 - Linus Walleij <linus.walleij@linaro.org>
13 This ethernet controller is found in the Gemini SoC family:
19 const: cortina,gemini-ethernet
23 description: must contain the global registers and the V-bit and A-bit
26 "#address-cells":
[all …]
|
| H A D | adi,adin.yaml | 1 # SPDX-License-Identifier: GPL-2.0+
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Marcelo Schmitt <marcelo.schmitt@analog.com>
13 Bindings for Analog Devices Industrial Ethernet PHYs
16 - $ref: ethernet-phy.yaml#
19 adi,rx-internal-delay-ps:
22 internal delay (phy-mode is 'rgmii-id' or 'rgmii-rxid') in pico-seconds.
26 adi,tx-internal-delay-ps:
29 internal delay (phy-mode is 'rgmii-id' or 'rgmii-txid') in pico-seconds.
[all …]
|
| H A D | microchip,lan966x-switch.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/net/microchip,lan966x-switch.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Microchip Lan966x Ethernet switch controller
10 - Horatiu Vultur <horatiu.vultur@microchip.com>
13 The lan966x switch is a multi-port Gigabit AVB/TSN Ethernet Switch with
14 two integrated 10/100/1000Base-T PHYs. In addition to the integrated PHYs,
15 it supports up to 2RGMII/RMII, up to 3BASE-X/SERDES/2.5GBASE-X and up to
16 2 Quad-SGMII/Quad-USGMII interfaces.
[all …]
|
| H A D | cavium-pip.txt | 1 * PIP Ethernet nexus.
3 The PIP Ethernet nexus can control several data packet input/output
4 devices. The devices have a two level grouping scheme. There may be
6 ports might be an individual Ethernet PHY.
10 - compatible: "cavium,octeon-3860-pip"
14 - reg: The base address of the PIP's register bank.
16 - #address-cells: Must be <1>.
18 - #size-cells: Must be <0>.
21 - compatible: "cavium,octeon-3860-pip-interface"
25 - reg: The interface number.
[all …]
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | mpc5200.txt | 2 ----------------------------
4 (c) 2006-2009 Secret Lab Technologies Ltd
8 ------------------
9 For mpc5200 on-chip devices, the format for each compatible value is
10 <chip>-<device>[-<mode>]. The OS should be able to match a device driver
11 to the device based solely on the compatible value. If two drivers
21 "fsl,mpc5200-<device>".
28 should have two items in the compatible list:
29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>";
34 ie. ethernet on mpc5200: compatible = "fsl,mpc5200-fec";
[all …]
|
| /linux/drivers/net/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 two machines with parallel ports using PLIP needs this, as well as
25 # All the following symbols are dependent on NETDEVICES - do not repeat
47 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
63 This is essentially a bit-bucket device (i.e. traffic you send to
123 If you have two serial connections to some other computer (this
124 usually requires two modems and two telephone lines) and you use
133 section 6.2 of the NET-3-HOWTO, available from
169 tristate "MAC-VLAN support"
175 iproute2 package starting with the iproute2-2.6.23 release:
[all …]
|
| /linux/arch/m68k/include/asm/ |
| H A D | mac_psc.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
6 * by the VIAs (Ethernet, DSP, SCC, Sound). This includes nine DMA
9 * The first seven DMA channels appear to be "one-shot" and are actually
10 * sets of two channels; one member is active while the other is being
12 * The one-shot channels are grouped together and are:
15 * 2. Ethernet Read
16 * 3. Ethernet Write
22 * The remaining two channels are handled somewhat differently. They appear
28 * Much of this was extrapolated from what was known about the Ethernet
30 * machine with easy-to-find patterns and looking for them in the DMA
[all …]
|
| /linux/Documentation/networking/ |
| H A D | bridge.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Ethernet Bridging
10 The IEEE 802.1Q-2022 (Bridges and Bridged Networks) standard defines the
12 standard, is a device that connects two or more network segments and operates
23 .. kernel-doc:: net/bridge/br_private.h
33 -------------------------
35 .. kernel-doc:: include/uapi/linux/if_link.h
39 ------------------------------
41 .. kernel-doc:: include/uapi/linux/if_link.h
45 ------------
[all …]
|
| /linux/drivers/net/ethernet/sunplus/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
11 If you have a network (Ethernet) card belonging to this
23 tristate "Sunplus Dual 10M/100M Ethernet devices"
27 If you have Sunplus dual 10M/100M Ethernet devices, say Y.
28 The network device creates two net-device interfaces.
|
| /linux/net/x25/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 entry point can carry several logical point-to-point connections
15 countries have public X.25 networks. X.25 consists of two
22 <file:Documentation/networking/x25-iface.rst>.
27 to "X.25 async driver" below) or over Ethernet using an ordinary
28 Ethernet card and the LAPB over Ethernet (say Y to "LAPB Data Link
29 Driver" and "LAPB over Ethernet driver" below).
|
| /linux/Documentation/networking/device_drivers/ethernet/cirrus/ |
| H A D | cs89x0.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Cirrus Logic LAN CS8900/CS8920 Ethernet Adapters
24 1.0 CIRRUS LOGIC LAN CS8900/CS8920 ETHERNET ADAPTERS
33 2.1 CS8900-based Adapter Configuration
34 2.2 CS8920-based Adapter Configuration
46 5.2.1 Diagnostic Self-Test
59 1. Cirrus Logic LAN CS8900/CS8920 Ethernet Adapters
66 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
67 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
68 computers on 10 Mbps Ethernet networks. The adapters are designed for operation
[all …]
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | phy-bindings.txt | 2 information about PHY subsystem refer to Documentation/driver-api/phy/phy.rst
8 #phy-cells: Number of cells in a PHY specifier; The meaning of all those
14 phy-supply: Phandle to a regulator that provides power to the PHY. This
24 #phy-cells = <1>;
38 confused with the Ethernet specific 'phy' and 'phy-handle' properties,
39 see Documentation/devicetree/bindings/net/ethernet.txt for these)
40 phy-names : the names of the PHY corresponding to the PHYs present in the
50 phy-names = "usb2phy", "usb3phy";
55 This node represents a controller that uses two PHYs, one for usb2 and one for
65 phy-names = "usbphy";
[all …]
|