Home
last modified time | relevance | path

Searched refs:copper (Results 1 – 21 of 21) sorted by relevance

/openbmc/u-boot/board/freescale/t4qds/
H A DREADME85 direct attach cable(copper), the copper cable is used to emulate
88 another will use copper cable. An hwconfig env "fsl_10gkr_copper" is
89 introduced to indicate a XFI port will use copper cable, and U-Boot
94 "fsl_10gkr_copper", it will use copper cable, otherwise, fiber cable
97 hwconfig, then both four XFI ports will use copper cable.
99 XFI ports will use copper cable, the other two XFI ports will use fiber
/openbmc/u-boot/board/freescale/t208xqds/
H A DREADME91 direct attach cable(copper), the copper cable is used to emulate
94 another will use copper cable. An hwconfig env "fsl_10gkr_copper" is
95 introduced to indicate a XFI port will use copper cable, and U-Boot
100 "fsl_10gkr_copper", it will use copper cable, otherwise, fiber cable
103 hwconfig, then both four XFI ports will use copper cable.
105 XFI ports will use copper cable, the other two XFI ports will use fiber
/openbmc/linux/drivers/net/fddi/
H A DKconfig12 run over copper or fiber. If you are connected to such a network and
24 and 700-C (DEFZA-CA, copper) TURBOchannel network cards which
/openbmc/linux/drivers/net/ethernet/alacritech/
H A DKconfig24 both copper and fiber.
/openbmc/linux/drivers/net/hippi/
H A DKconfig12 can run over copper (25m) or fiber (300m on multi-mode or 10km on
/openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/
H A De1000.rst52 (Supported only on adapters with copper connections)
68 (Supported only on adapters with copper connections)
246 (This parameter is supported only on adapters with copper connections.)
344 For copper-based boards, the keywords interact as follows:
H A De1000e.rst327 between copper-based adapters and fiber-based adapters.
329 In the default mode, an Intel(R) Ethernet Network Adapter using copper
H A Di40e.rst370 between copper-based adapters and fiber-based adapters.
372 In the default mode, an Intel(R) Ethernet Network Adapter using copper
H A Dice.rst662 between copper-based adapters and fiber-based adapters.
664 In the default mode, an Intel(R) Ethernet Network Adapter using copper
/openbmc/linux/arch/arm64/boot/dts/marvell/
H A Darmada-8040-clearfog-gt-8k.dts327 cp0_copper_eth_phy_reset: copper-eth-phy-reset {
571 /* 1G copper */
/openbmc/linux/arch/arm64/boot/dts/hisilicon/
H A Dhip06.dtsi560 media-type = "copper";
569 media-type = "copper";
H A Dhip07.dtsi1472 media-type = "copper";
1482 media-type = "copper";
/openbmc/docs/designs/
H A Dthermal-control-modes.md23 in place of copper cables. These optical cables can report overtemp warnings to
/openbmc/linux/drivers/net/ethernet/marvell/
H A Dskge.c265 if (hw->copper) { in skge_supported_modes()
301 if (hw->copper) { in skge_get_link_ksettings()
1977 if (hw->copper) { in yukon_init()
2095 reg |= hw->copper ? GPC_HWCFG_GMII_COP : GPC_HWCFG_GMII_FIB; in yukon_mac_init()
3551 hw->copper = (pmd_type == 'T' || pmd_type == '1'); in skge_reset()
3578 hw->copper = 1; in skge_reset()
H A Dskge.h2413 u8 copper; member
/openbmc/u-boot/board/freescale/t208xrdb/
H A DREADME61 - Two on-board 10Gbps Base-T copper ports
/openbmc/linux/drivers/net/phy/
H A DKconfig391 Currently supports the DP83869 PHY. This PHY supports copper and
/openbmc/u-boot/doc/
H A DREADME.b4860qds74 - A Vitesse dual SGMII phy VSC8662 links the B4860 SGMII lines to 2xRJ-45 copper connectors
/openbmc/linux/Documentation/security/keys/
H A Dcore.rst298 00000892 I--QU- 1 perm 1f000000 0 0 user metal:copper: 0
/openbmc/linux/Documentation/networking/
H A Darcnet-hardware.rst2456 hint to the existence of a manufacturer at all is written in copper,
H A Dbonding.rst2733 A passthrough module (OPM or CPM, optical or copper,