Searched +full:two +full:- +full:ethernet (Results 1 – 25 of 1014) sorted by relevance
12345678910>>...41
| /kernel/linux/linux-5.10/include/linux/ |
| D | etherdevice.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
7 * Definitions for the Ethernet handlers.
62 /* Reserved Ethernet Addresses per IEEE 802.1Q */
68 * is_link_local_ether_addr - Determine if given Ethernet address is link-local
69 * @addr: Pointer to a six-byte array containing the Ethernet address
91 * is_zero_ether_addr - Determine if give Ethernet address is all zeros.
92 * @addr: Pointer to a six-byte array containing the Ethernet address
110 * is_multicast_ether_addr - Determine if the Ethernet address is a multicast.
111 * @addr: Pointer to a six-byte array containing the Ethernet address
124 return 0x01 & (a >> ((sizeof(a) * 8) - 8)); in is_multicast_ether_addr()
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | etherdevice.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
7 * Definitions for the Ethernet handlers.
69 /* Reserved Ethernet Addresses per IEEE 802.1Q */
75 * is_link_local_ether_addr - Determine if given Ethernet address is link-local
76 * @addr: Pointer to a six-byte array containing the Ethernet address
98 * is_zero_ether_addr - Determine if give Ethernet address is all zeros.
99 * @addr: Pointer to a six-byte array containing the Ethernet address
117 * is_multicast_ether_addr - Determine if the Ethernet address is a multicast.
118 * @addr: Pointer to a six-byte array containing the Ethernet address
131 return 0x01 & (a >> ((sizeof(a) * 8) - 8)); in is_multicast_ether_addr()
[all …]
|
| /kernel/linux/linux-5.10/net/l2tp/ |
| 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 …]
|
| /kernel/linux/linux-6.6/net/l2tp/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/usb/gadget/legacy/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/usb/gadget/legacy/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/ |
| D | cortina,gemini-ethernet.txt | 1 Cortina Systems Gemini Ethernet Controller
4 This ethernet controller is found in the Gemini SoC family:
9 - compatible: must be "cortina,gemini-ethernet"
10 - reg: must contain the global registers and the V-bit and A-bit
12 - syscon: a phandle to the system controller
13 - #address-cells: must be specified, must be <1>
14 - #size-cells: must be specified, must be <1>
15 - ranges: should be state like this giving a 1:1 address translation
18 The subnodes represents the two ethernet ports in this device.
23 - port0: contains the resources for ethernet port 0
[all …]
|
| D | brcm,unimac-mdio.txt | 4 - compatible: should one from "brcm,genet-mdio-v1", "brcm,genet-mdio-v2",
5 "brcm,genet-mdio-v3", "brcm,genet-mdio-v4", "brcm,genet-mdio-v5" or
6 "brcm,unimac-mdio"
7 - reg: address and length of the register set for the device, first one is the
9 larger than 16-bits MDIO transactions
10 - reg-names: name(s) of the register must be "mdio" and optional "mdio_indir_rw"
11 - #size-cells: must be 1
12 - #address-cells: must be 0
15 - interrupts: must be one if the interrupt is shared with the Ethernet MAC or
16 Ethernet switch this MDIO block is integrated from, or must be two, if there
[all …]
|
| D | brcm,bcmgenet.txt | 1 * Broadcom BCM7xxx Ethernet Controller (GENET)
4 - compatible: should contain one of "brcm,genet-v1", "brcm,genet-v2",
5 "brcm,genet-v3", "brcm,genet-v4", "brcm,genet-v5", "brcm,bcm2711-genet-v5".
6 - reg: address and length of the register set for the device
7 - interrupts and/or interrupts-extended: must be two cells, the first cell
10 optional third interrupt cell for Wake-on-LAN can be specified.
11 See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
13 - phy-mode: see ethernet.txt file in the same directory
14 - #address-cells: should be 1
15 - #size-cells: should be 1
[all …]
|
| D | fsl-enetc.txt | 1 * ENETC ethernet device tree bindings
4 external) there are two supported link modes specified by
9 - reg : Specifies PCIe Device Number and Function
12 - compatible : Should be "fsl,enetc".
18 In this case, the ENETC node should include a "mdio" sub-node
19 that in turn should contain the "ethernet-phy" node describing the
21 already defined in Documentation/devicetree/bindings/net/ethernet.txt or
26 - phy-handle : Phandle to a PHY on the MDIO bus.
27 Defined in ethernet.txt.
29 - phy-connection-type : Defined in ethernet.txt.
[all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/net/hsr/ |
| 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 …]
|
| /kernel/linux/linux-5.10/net/hsr/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/networking/dsa/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/networking/dsa/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/dsa/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/net/usb/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 comment "Host-side USB support is needed for USB Network Adapter support"
16 tristate "USB CATC NetMate-based Ethernet device support"
19 Say Y if you want to use one of the following 10Mbps USB Ethernet
27 This driver makes the adapter appear as a normal Ethernet interface,
28 typically on eth0, if it is the only ethernet device, or perhaps on
29 eth1, if you have a PCI or ISA ethernet card installed.
35 tristate "USB KLSI KL5USB101-based ethernet device support"
38 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
40 ADS USB-10BT
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/usb/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
5 comment "Host-side USB support is needed for USB Network Adapter support"
16 tristate "USB CATC NetMate-based Ethernet device support"
19 Say Y if you want to use one of the following 10Mbps USB Ethernet
27 This driver makes the adapter appear as a normal Ethernet interface,
28 typically on eth0, if it is the only ethernet device, or perhaps on
29 eth1, if you have a PCI or ISA ethernet card installed.
35 tristate "USB KLSI KL5USB101-based ethernet device support"
38 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
40 ADS USB-10BT
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/ |
| 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 - Alexandru Tachici <alexandru.tachici@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 …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | armada3700-periph-clock.txt | 6 There are two different blocks associated to north bridge and south
14 -----------------------------------
35 -----------------------------------
36 0 gbe-50 50 MHz parent clock for Gigabit Ethernet
37 1 gbe-core parent clock for Gigabit Ethernet core
38 2 gbe-125 125 MHz parent clock for Gigabit Ethernet
39 3 gbe1-50 50 MHz clock for Gigabit Ethernet port 1
40 4 gbe0-50 50 MHz clock for Gigabit Ethernet port 0
41 5 gbe1-125 125 MHz clock for Gigabit Ethernet port 1
42 6 gbe0-125 125 MHz clock for Gigabit Ethernet port 0
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/ |
| D | armada3700-periph-clock.txt | 6 There are two different blocks associated to north bridge and south
14 -----------------------------------
35 -----------------------------------
36 0 gbe-50 50 MHz parent clock for Gigabit Ethernet
37 1 gbe-core parent clock for Gigabit Ethernet core
38 2 gbe-125 125 MHz parent clock for Gigabit Ethernet
39 3 gbe1-50 50 MHz clock for Gigabit Ethernet port 1
40 4 gbe0-50 50 MHz clock for Gigabit Ethernet port 0
41 5 gbe1-125 125 MHz clock for Gigabit Ethernet port 1
42 6 gbe0-125 125 MHz clock for Gigabit Ethernet port 0
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/dsa/ |
| 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 Device Tree Bindings
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Vivien Didelot <vivien.didelot@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
29 A two element list indicates which DSA cluster, and position within the
[all …]
|
12345678910>>...41