Файловый менеджер - Редактировать - /var/www/html/ethernet.zip
Ðазад
PK ! �L��! ! aeroflex/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Aeroflex Gaisler network device configuration # config GRETH tristate "Aeroflex Gaisler GRETH Ethernet MAC support" depends on SPARC select PHYLIB select CRC32 help Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC. PK ! (wm� � aeroflex/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Aeroflex Gaisler network device drivers. # obj-$(CONFIG_GRETH) += greth.o PK ! v�$q; ; ni/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # National Instruments network device configuration # config NET_VENDOR_NI bool "National Instruments Devices" default y help If you have a network (Ethernet) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about National Instruments devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_NI config NI_XGE_MANAGEMENT_ENET tristate "National Instruments XGE management enet support" depends on HAS_IOMEM && HAS_DMA select PHYLIB select OF_MDIO if OF help Simple LAN device for debug or management purposes. Can support either 10G or 1G PHYs via SFP+ ports. endif PK ! �T=)X X ni/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_NI_XGE_MANAGEMENT_ENET) += nixge.o PK ! r�}�, , litex/Kconfignu �[��� # # LiteX device configuration # config NET_VENDOR_LITEX bool "LiteX devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about LiteX devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_LITEX config LITEX_LITEETH tristate "LiteX Ethernet support" depends on OF && HAS_IOMEM help If you wish to compile a kernel for hardware with a LiteX LiteEth device then you should answer Y to this. LiteX is a soft system-on-chip that targets FPGAs. LiteETH is a basic network device that is commonly used in LiteX designs. endif # NET_VENDOR_LITEX PK ! Р �e e litex/Makefilenu �[��� # # Makefile for the LiteX network device drivers. # obj-$(CONFIG_LITEX_LITEETH) += litex_liteeth.o PK ! ��e� � silan/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Silan device configuration # config NET_VENDOR_SILAN bool "Silan devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Silan devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SILAN config SC92031 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver" depends on PCI select CRC32 help This is a driver for the Fast Ethernet PCI network cards based on the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you have one of these, say Y here. To compile this driver as a module, choose M here: the module will be called sc92031. This is recommended. endif # NET_VENDOR_SILAN PK ! t�|� � silan/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Silan network device drivers. # obj-$(CONFIG_SC92031) += sc92031.o PK ! �c�{� � natsemi/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # National Semiconductor device configuration # config NET_VENDOR_NATSEMI bool "National Semiconductor devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about National Semiconductor devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_NATSEMI config MACSONIC tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" depends on MAC help Support for NatSemi SONIC based Ethernet devices. This includes the onboard Ethernet in many Quadras as well as some LC-PDS, a few Nubus and all known Comm Slot Ethernet cards. If you have one of these say Y here. To compile this driver as a module, choose M here. This module will be called macsonic. config MIPS_JAZZ_SONIC tristate "MIPS JAZZ onboard SONIC Ethernet support" depends on MACH_JAZZ help This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. config NATSEMI tristate "National Semiconductor DP8381x series PCI Ethernet support" depends on PCI select CRC32 help This driver is for the National Semiconductor DP83810 series, which is used in cards from PureData, NetGear, Linksys and others, including the 83815 chip. More specific information and updates are available from <http://www.scyld.com/network/natsemi.html>. config NS83820 tristate "National Semiconductor DP83820 support" depends on PCI help This is a driver for the National Semiconductor DP83820 series of gigabit ethernet MACs. Cards using this chipset include the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of zero copy. config XTENSA_XT2000_SONIC tristate "Xtensa XT2000 onboard SONIC Ethernet support" depends on XTENSA_PLATFORM_XT2000 help This is the driver for the onboard card of the Xtensa XT2000 board. endif # NET_VENDOR_NATSEMI PK ! �,6�( ( natsemi/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the National Semiconductor Sonic devices. # obj-$(CONFIG_MACSONIC) += macsonic.o obj-$(CONFIG_MIPS_JAZZ_SONIC) += jazzsonic.o obj-$(CONFIG_NATSEMI) += natsemi.o obj-$(CONFIG_NS83820) += ns83820.o obj-$(CONFIG_XTENSA_XT2000_SONIC) += xtsonic.o PK ! �J�@ @ micrel/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Micrel device configuration # config NET_VENDOR_MICREL bool "Micrel devices" default y depends on (HAS_IOMEM && DMA_ENGINE) || SPI || PCI || HAS_IOMEM help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Micrel devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_MICREL config KS8842 tristate "Micrel KSZ8841/42 with generic bus interface" depends on HAS_IOMEM && DMA_ENGINE help This platform driver is for KSZ8841(1-port) / KS8842(2-port) ethernet switch chip (managed, VLAN, QoS) from Micrel or Timberdale(FPGA). config KS8851 tristate "Micrel KS8851 SPI" depends on SPI select MII select CRC32 select EEPROM_93CX6 select PHYLIB select MICREL_PHY help SPI driver for Micrel KS8851 SPI attached network chip. config KS8851_MLL tristate "Micrel KS8851 MLL" depends on HAS_IOMEM depends on PTP_1588_CLOCK_OPTIONAL select MII select CRC32 select EEPROM_93CX6 select PHYLIB select MICREL_PHY help This platform driver is for Micrel KS8851 Address/data bus multiplexed network chip. config KSZ884X_PCI tristate "Micrel KSZ8841/2 PCI" depends on PCI select MII select CRC32 help This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip. To compile this driver as a module, choose M here. The module will be called ksz884x. endif # NET_VENDOR_MICREL PK ! =�� micrel/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Micrel network device drivers. # obj-$(CONFIG_KS8842) += ks8842.o obj-$(CONFIG_KS8851) += ks8851_common.o ks8851_spi.o obj-$(CONFIG_KS8851_MLL) += ks8851_common.o ks8851_par.o obj-$(CONFIG_KSZ884X_PCI) += ksz884x.o PK ! ��,e� � sun/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 # # Sun network device configuration # config NET_VENDOR_SUN bool "Sun devices" default y depends on SUN3 || SBUS || PCI || SUN_LDOMS help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Sun network interfaces. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SUN config HAPPYMEAL tristate "Sun Happy Meal 10/100baseT support" depends on (SBUS || PCI) select CRC32 help This driver supports the "hme" interface present on most Ultra systems and as an option on older Sbus systems. This driver supports both PCI and Sbus devices. This driver also supports the "qfe" quad 100baseT device available in both PCI and Sbus configurations. To compile this driver as a module, choose M here: the module will be called sunhme. config SUNBMAC tristate "Sun BigMAC 10/100baseT support" depends on SBUS select CRC32 help This driver supports the "be" interface available as an Sbus option. This is Sun's older 100baseT Ethernet device. To compile this driver as a module, choose M here: the module will be called sunbmac. config SUNQE tristate "Sun QuadEthernet support" depends on SBUS select CRC32 help This driver supports the "qe" 10baseT Ethernet device, available as an Sbus option. Note that this is not the same as Quad FastEthernet "qfe" which is supported by the Happy Meal driver instead. To compile this driver as a module, choose M here: the module will be called sunqe. config SUNGEM tristate "Sun GEM support" depends on PCI select CRC32 select SUNGEM_PHY help Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also <http://docs.oracle.com/cd/E19455-01/806-3985-10/806-3985-10.pdf>. config CASSINI tristate "Sun Cassini support" depends on PCI select CRC32 help Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also <http://docs.oracle.com/cd/E19113-01/giga.ether.pci/817-4341-10/817-4341-10.pdf>. config SUNVNET_COMMON tristate "Common routines to support Sun Virtual Networking" depends on SUN_LDOMS depends on INET default m config SUNVNET tristate "Sun Virtual Network support" default m depends on SUN_LDOMS depends on SUNVNET_COMMON help Support for virtual network devices under Sun Logical Domains. config LDMVSW tristate "Sun4v LDoms Virtual Switch support" default m depends on SUN_LDOMS depends on SUNVNET_COMMON help Support for virtual switch devices under Sun4v Logical Domains. This driver adds a network interface for every vsw-port node found in the machine description of a service domain. Linux bridge/switch software can use these interfaces for guest domain network interconnectivity or guest domain connection to a physical network on a service domain. config NIU tristate "Sun Neptune 10Gbit Ethernet support" depends on PCI select CRC32 help This enables support for cards based upon Sun's Neptune chipset. endif # NET_VENDOR_SUN PK ! i#ϑ � sun/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Sun network device drivers. # obj-$(CONFIG_HAPPYMEAL) += sunhme.o obj-$(CONFIG_SUNQE) += sunqe.o obj-$(CONFIG_SUNBMAC) += sunbmac.o obj-$(CONFIG_SUNGEM) += sungem.o obj-$(CONFIG_CASSINI) += cassini.o obj-$(CONFIG_SUNVNET_COMMON) += sunvnet_common.o obj-$(CONFIG_SUNVNET) += sunvnet.o obj-$(CONFIG_LDMVSW) += ldmvsw.o obj-$(CONFIG_NIU) += niu.o PK ! �q�� � cisco/enic/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Cisco device configuration # config ENIC tristate "Cisco VIC Ethernet NIC Support" depends on PCI help This enables the support for the Cisco VIC Ethernet card. PK ! �� �� � cisco/enic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_ENIC) := enic.o enic-y := enic_main.o vnic_cq.o vnic_intr.o vnic_wq.o \ enic_res.o enic_dev.o enic_pp.o vnic_dev.o vnic_rq.o vnic_vic.o \ enic_ethtool.o enic_api.o enic_clsf.o PK ! �G�D D cisco/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Cisco device configuration # config NET_VENDOR_CISCO bool "Cisco devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Cisco cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_CISCO source "drivers/net/ethernet/cisco/enic/Kconfig" endif # NET_VENDOR_CISCO PK ! ԏ:�r r cisco/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Cisco device drivers. # obj-$(CONFIG_ENIC) += enic/ PK ! w,�2 2 moxa/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # MOXART device configuration # config NET_VENDOR_MOXART bool "MOXA ART devices" default y depends on (ARM && ARCH_MOXART) help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about MOXA ART devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_MOXART config ARM_MOXART_ETHER tristate "MOXART Ethernet support" depends on ARM && ARCH_MOXART select NET_CORE help If you wish to compile a kernel for a hardware with MOXA ART SoC and want to use the internal ethernet then you should answer Y to this. endif # NET_VENDOR_MOXART PK ! ��ڭ� � moxa/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the MOXART network device drivers. # obj-$(CONFIG_ARM_MOXART_ETHER) += moxart_ether.o PK ! ����D D intel/ice/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright (c) 2018, Intel Corporation. # # Makefile for the Intel(R) Ethernet Connection E800 Series Linux Driver # obj-$(CONFIG_ICE) += ice.o ice-y := ice_main.o \ ice_controlq.o \ ice_common.o \ ice_nvm.o \ ice_switch.o \ ice_sched.o \ ice_base.o \ ice_lib.o \ ice_txrx_lib.o \ ice_txrx.o \ ice_fltr.o \ ice_fdir.o \ ice_ethtool_fdir.o \ ice_flex_pipe.o \ ice_flow.o \ ice_idc.o \ ice_devlink.o \ ice_fw_update.o \ ice_lag.o \ ice_ethtool.o ice-$(CONFIG_PCI_IOV) += ice_virtchnl_allowlist.o ice-$(CONFIG_PCI_IOV) += ice_virtchnl_pf.o ice_sriov.o ice_virtchnl_fdir.o ice-$(CONFIG_PTP_1588_CLOCK) += ice_ptp.o ice_ptp_hw.o ice-$(CONFIG_DCB) += ice_dcb.o ice_dcb_nl.o ice_dcb_lib.o ice-$(CONFIG_RFS_ACCEL) += ice_arfs.o ice-$(CONFIG_XDP_SOCKETS) += ice_xsk.o PK ! '���� � intel/e1000/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 1999 - 2006 Intel Corporation. # # Makefile for the Intel(R) PRO/1000 ethernet driver # obj-$(CONFIG_E1000) += e1000.o e1000-objs := e1000_main.o e1000_hw.o e1000_ethtool.o e1000_param.o PK ! &��' intel/igbvf/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 2009 - 2018 Intel Corporation. # # Makefile for the Intel(R) 82576 VF ethernet driver # obj-$(CONFIG_IGBVF) += igbvf.o igbvf-objs := vf.o \ mbx.o \ ethtool.o \ netdev.o PK ! ���9# # intel/i40e/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 2013 - 2018 Intel Corporation. # # Makefile for the Intel(R) Ethernet Connection XL710 (i40e.ko) driver # ccflags-y += -I$(src) subdir-ccflags-y += -I$(src) obj-$(CONFIG_I40E) += i40e.o i40e-objs := i40e_main.o \ i40e_ethtool.o \ i40e_adminq.o \ i40e_common.o \ i40e_hmc.o \ i40e_lan_hmc.o \ i40e_nvm.o \ i40e_debugfs.o \ i40e_diag.o \ i40e_txrx.o \ i40e_ptp.o \ i40e_ddp.o \ i40e_client.o \ i40e_virtchnl_pf.o \ i40e_xsk.o i40e-$(CONFIG_I40E_DCB) += i40e_dcb.o i40e_dcb_nl.o PK ! ��$%/ / intel/igc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright (c) 2018 Intel Corporation # # Intel(R) I225-LM/I225-V 2.5G Ethernet Controller # obj-$(CONFIG_IGC) += igc.o igc-objs := igc_main.o igc_mac.o igc_i225.o igc_base.o igc_nvm.o igc_phy.o \ igc_diag.o igc_ethtool.o igc_ptp.o igc_dump.o igc_tsn.o igc_xdp.o PK ! �Iz� � intel/ixgb/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 1999 - 2008 Intel Corporation. # # Makefile for the Intel(R) PRO/10GbE ethernet driver # obj-$(CONFIG_IXGB) += ixgb.o ixgb-objs := ixgb_main.o ixgb_hw.o ixgb_ee.o ixgb_ethtool.o ixgb_param.o PK ! v7ta� � intel/iavf/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 2013 - 2018 Intel Corporation. # # Makefile for the Intel(R) Ethernet Adaptive Virtual Function (iavf) # driver # # ccflags-y += -I$(src) subdir-ccflags-y += -I$(src) obj-$(CONFIG_IAVF) += iavf.o iavf-objs := iavf_main.o iavf_ethtool.o iavf_virtchnl.o iavf_fdir.o \ iavf_adv_rss.o \ iavf_txrx.o iavf_common.o iavf_adminq.o iavf_client.o PK ! ( ��E E intel/ixgbevf/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 1999 - 2018 Intel Corporation. # # Makefile for the Intel(R) 82599 VF ethernet driver # obj-$(CONFIG_IXGBEVF) += ixgbevf.o ixgbevf-objs := vf.o \ mbx.o \ ethtool.o \ ixgbevf_main.o ixgbevf-$(CONFIG_IXGBEVF_IPSEC) += ipsec.o PK ! ���{D D intel/igb/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 1999 - 2018 Intel Corporation. # # Makefile for the Intel(R) 82575 PCI-Express ethernet driver # obj-$(CONFIG_IGB) += igb.o igb-objs := igb_main.o igb_ethtool.o e1000_82575.o \ e1000_mac.o e1000_nvm.o e1000_phy.o e1000_mbx.o \ e1000_i210.o igb_ptp.o igb_hwmon.o PK ! ��M. . intel/e1000e/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 1999 - 2018 Intel Corporation. # # Makefile for the Intel(R) PRO/1000 ethernet driver # obj-$(CONFIG_E1000E) += e1000e.o e1000e-objs := 82571.o ich8lan.o 80003es2lan.o \ mac.o manage.o nvm.o phy.o \ param.o ethtool.o netdev.o ptp.o PK ! 7�;6, 6, intel/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Intel network device configuration # config NET_VENDOR_INTEL bool "Intel devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Intel cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_INTEL config E100 tristate "Intel(R) PRO/100+ support" depends on PCI select MII help This driver supports Intel(R) PRO/100 family of adapters. To verify that your adapter is supported, find the board ID number on the adapter. Look for a label that has a barcode and a number in the format 123456-001 (six digits hyphen three digits). Use the above information and the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> to identify the adapter. More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/e100.rst>. To compile this driver as a module, choose M here. The module will be called e100. config E1000 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" depends on PCI help This driver supports Intel(R) PRO/1000 gigabit ethernet family of adapters. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/e1000.rst>. To compile this driver as a module, choose M here. The module will be called e1000. config E1000E tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" depends on PCI && (!SPARC32 || BROKEN) depends on PTP_1588_CLOCK_OPTIONAL select CRC32 help This driver supports the PCI-Express Intel(R) PRO/1000 gigabit ethernet family of adapters. For PCI or PCI-X e1000 adapters, use the regular e1000 driver For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/e1000e.rst>. To compile this driver as a module, choose M here. The module will be called e1000e. config E1000E_HWTS bool "Support HW cross-timestamp on PCH devices" default y depends on E1000E && X86 help Say Y to enable hardware supported cross-timestamping on PCH devices. The cross-timestamp is available through the PTP clock driver precise cross-timestamp ioctl (PTP_SYS_OFFSET_PRECISE). config IGB tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select I2C select I2C_ALGOBIT help This driver supports Intel(R) 82575/82576 gigabit ethernet family of adapters. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/igb.rst>. To compile this driver as a module, choose M here. The module will be called igb. config IGB_HWMON bool "Intel(R) PCI-Express Gigabit adapters HWMON support" default y depends on IGB && HWMON && !(IGB=y && HWMON=m) help Say Y if you want to expose thermal sensor data on Intel devices. Some of our devices contain thermal sensors, both external and internal. This data is available via the hwmon sysfs interface and exposes the onboard sensors. config IGB_DCA bool "Direct Cache Access (DCA) Support" default y depends on IGB && DCA && !(IGB=y && DCA=m) help Say Y here if you want to use Direct Cache Access (DCA) in the driver. DCA is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses. config IGBVF tristate "Intel(R) 82576 Virtual Function Ethernet support" depends on PCI help This driver supports Intel(R) 82576 virtual functions. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/igbvf.rst>. To compile this driver as a module, choose M here. The module will be called igbvf. config IXGB tristate "Intel(R) PRO/10GbE support" depends on PCI help This driver supports Intel(R) PRO/10GbE family of adapters for PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver instead. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/ixgb.rst>. To compile this driver as a module, choose M here. The module will be called ixgb. config IXGBE tristate "Intel(R) 10GbE PCI Express adapters support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select MDIO select PHYLIB help This driver supports Intel(R) 10GbE PCI Express family of adapters. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/ixgbe.rst>. To compile this driver as a module, choose M here. The module will be called ixgbe. config IXGBE_HWMON bool "Intel(R) 10GbE PCI Express adapters HWMON support" default y depends on IXGBE && HWMON && !(IXGBE=y && HWMON=m) help Say Y if you want to expose the thermal sensor data on some of our cards, via a hwmon sysfs interface. config IXGBE_DCA bool "Direct Cache Access (DCA) Support" default y depends on IXGBE && DCA && !(IXGBE=y && DCA=m) help Say Y here if you want to use Direct Cache Access (DCA) in the driver. DCA is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses. config IXGBE_DCB bool "Data Center Bridging (DCB) Support" default n depends on IXGBE && DCB help Say Y here if you want to use Data Center Bridging (DCB) in the driver. If unsure, say N. config IXGBE_IPSEC bool "IPSec XFRM cryptography-offload acceleration" depends on IXGBE depends on XFRM_OFFLOAD default y select XFRM_ALGO help Enable support for IPSec offload in ixgbe.ko config IXGBEVF tristate "Intel(R) 10GbE PCI Express Virtual Function Ethernet support" depends on PCI_MSI help This driver supports Intel(R) PCI Express virtual functions for the Intel(R) ixgbe driver. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/ixgbevf.rst>. To compile this driver as a module, choose M here. The module will be called ixgbevf. MSI-X interrupt support is required for this driver to work correctly. config IXGBEVF_IPSEC bool "IPSec XFRM cryptography-offload acceleration" depends on IXGBEVF depends on XFRM_OFFLOAD default y select XFRM_ALGO help Enable support for IPSec offload in ixgbevf.ko config I40E tristate "Intel(R) Ethernet Controller XL710 Family support" depends on PTP_1588_CLOCK_OPTIONAL depends on PCI select AUXILIARY_BUS help This driver supports Intel(R) Ethernet Controller XL710 Family of devices. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/i40e.rst>. To compile this driver as a module, choose M here. The module will be called i40e. config I40E_DCB bool "Data Center Bridging (DCB) Support" default n depends on I40E && DCB help Say Y here if you want to use Data Center Bridging (DCB) in the driver. If unsure, say N. # this is here to allow seamless migration from I40EVF --> IAVF name # so that CONFIG_IAVF symbol will always mirror the state of CONFIG_I40EVF config IAVF tristate config I40EVF tristate "Intel(R) Ethernet Adaptive Virtual Function support" select IAVF depends on PCI_MSI help This driver supports virtual functions for Intel XL710, X710, X722, XXV710, and all devices advertising support for Intel Ethernet Adaptive Virtual Function devices. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <https://support.intel.com> This driver was formerly named i40evf. More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/iavf.rst>. To compile this driver as a module, choose M here. The module will be called iavf. MSI-X interrupt support is required for this driver to work correctly. config ICE tristate "Intel(R) Ethernet Connection E800 Series Support" default n depends on PCI_MSI depends on PTP_1588_CLOCK_OPTIONAL select AUXILIARY_BUS select DIMLIB select NET_DEVLINK select PLDMFW help This driver supports Intel(R) Ethernet Connection E800 Series of devices. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/ice.rst>. To compile this driver as a module, choose M here. The module will be called ice. config FM10K tristate "Intel(R) FM10000 Ethernet Switch Host Interface Support" default n depends on PCI_MSI depends on PTP_1588_CLOCK_OPTIONAL help This driver supports Intel(R) FM10000 Ethernet Switch Host Interface. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/intel/fm10k.rst>. To compile this driver as a module, choose M here. The module will be called fm10k. MSI-X interrupt support is required config IGC tristate "Intel(R) Ethernet Controller I225-LM/I225-V support" default n depends on PCI depends on PTP_1588_CLOCK_OPTIONAL help This driver supports Intel(R) Ethernet Controller I225-LM/I225-V family of adapters. For more information on how to identify your adapter, go to the Adapter & Driver ID Guide that can be located at: <http://support.intel.com> To compile this driver as a module, choose M here. The module will be called igc. endif # NET_VENDOR_INTEL PK ! ��� � intel/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Intel network device drivers. # obj-$(CONFIG_E100) += e100.o obj-$(CONFIG_E1000) += e1000/ obj-$(CONFIG_E1000E) += e1000e/ obj-$(CONFIG_IGB) += igb/ obj-$(CONFIG_IGC) += igc/ obj-$(CONFIG_IGBVF) += igbvf/ obj-$(CONFIG_IXGBE) += ixgbe/ obj-$(CONFIG_IXGBEVF) += ixgbevf/ obj-$(CONFIG_I40E) += i40e/ obj-$(CONFIG_IXGB) += ixgb/ obj-$(CONFIG_IAVF) += iavf/ obj-$(CONFIG_FM10K) += fm10k/ obj-$(CONFIG_ICE) += ice/ PK ! ɭ w� � intel/fm10k/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 2013 - 2018 Intel Corporation. # # Makefile for the Intel(R) Ethernet Switch Host Interface Driver # obj-$(CONFIG_FM10K) += fm10k.o fm10k-y := fm10k_main.o \ fm10k_common.o \ fm10k_pci.o \ fm10k_netdev.o \ fm10k_ethtool.o \ fm10k_pf.o \ fm10k_vf.o \ fm10k_mbx.o \ fm10k_iov.o \ fm10k_tlv.o fm10k-$(CONFIG_DEBUG_FS) += fm10k_debugfs.o fm10k-$(CONFIG_DCB) += fm10k_dcbnl.o PK ! ��w� � intel/ixgbe/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 1999 - 2018 Intel Corporation. # # Makefile for the Intel(R) 10GbE PCI Express ethernet driver # obj-$(CONFIG_IXGBE) += ixgbe.o ixgbe-objs := ixgbe_main.o ixgbe_common.o ixgbe_ethtool.o \ ixgbe_82599.o ixgbe_82598.o ixgbe_phy.o ixgbe_sriov.o \ ixgbe_mbx.o ixgbe_x540.o ixgbe_x550.o ixgbe_lib.o ixgbe_ptp.o \ ixgbe_xsk.o ixgbe-$(CONFIG_IXGBE_DCB) += ixgbe_dcb.o ixgbe_dcb_82598.o \ ixgbe_dcb_82599.o ixgbe_dcb_nl.o ixgbe-$(CONFIG_IXGBE_HWMON) += ixgbe_sysfs.o ixgbe-$(CONFIG_DEBUG_FS) += ixgbe_debugfs.o ixgbe-$(CONFIG_FCOE:m=y) += ixgbe_fcoe.o ixgbe-$(CONFIG_IXGBE_IPSEC) += ixgbe_ipsec.o PK ! ��� � mediatek/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_VENDOR_MEDIATEK bool "MediaTek devices" depends on ARCH_MEDIATEK || SOC_MT7621 || SOC_MT7620 help If you have a Mediatek SoC with ethernet, say Y. if NET_VENDOR_MEDIATEK config NET_MEDIATEK_SOC tristate "MediaTek SoC Gigabit Ethernet support" depends on NET_DSA || !NET_DSA select PHYLINK select DIMLIB help This driver supports the gigabit ethernet MACs in the MediaTek SoC family. config NET_MEDIATEK_STAR_EMAC tristate "MediaTek STAR Ethernet MAC support" select PHYLIB select REGMAP_MMIO help This driver supports the ethernet MAC IP first used on MediaTek MT85** SoCs. endif #NET_VENDOR_MEDIATEK PK ! M�z+- - mediatek/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Mediatek SoCs built-in ethernet macs # obj-$(CONFIG_NET_MEDIATEK_SOC) += mtk_eth.o mtk_eth-y := mtk_eth_soc.o mtk_sgmii.o mtk_eth_path.o mtk_ppe.o mtk_ppe_debugfs.o mtk_ppe_offload.o obj-$(CONFIG_NET_MEDIATEK_STAR_EMAC) += mtk_star_emac.o PK ! �-<O� � hisilicon/hns/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the HISILICON network device drivers. # obj-$(CONFIG_HNS) += hnae.o obj-$(CONFIG_HNS_DSAF) += hns_dsaf.o hns_dsaf-objs = hns_ae_adapt.o hns_dsaf_gmac.o hns_dsaf_mac.o hns_dsaf_misc.o \ hns_dsaf_main.o hns_dsaf_ppe.o hns_dsaf_rcb.o hns_dsaf_xgmac.o obj-$(CONFIG_HNS_ENET) += hns_enet_drv.o hns_enet_drv-objs = hns_enet.o hns_ethtool.o PK ! ��:�� � hisilicon/hns3/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0+ # # Makefile for the HISILICON network device drivers. # ccflags-y += -I$(srctree)/$(src) ccflags-y += -I$(srctree)/drivers/net/ethernet/hisilicon/hns3/hns3pf ccflags-y += -I$(srctree)/drivers/net/ethernet/hisilicon/hns3/hns3vf ccflags-y += -I$(srctree)/drivers/net/ethernet/hisilicon/hns3/hns3_common obj-$(CONFIG_HNS3) += hnae3.o obj-$(CONFIG_HNS3_ENET) += hns3.o hns3-objs = hns3_enet.o hns3_ethtool.o hns3_debugfs.o hns3-$(CONFIG_HNS3_DCB) += hns3_dcbnl.o obj-$(CONFIG_HNS3_HCLGEVF) += hclgevf.o hclgevf-objs = hns3vf/hclgevf_main.o hns3vf/hclgevf_cmd.o hns3vf/hclgevf_mbx.o hns3vf/hclgevf_devlink.o \ hns3_common/hclge_comm_cmd.o obj-$(CONFIG_HNS3_HCLGE) += hclge.o hclge-objs = hns3pf/hclge_main.o hns3pf/hclge_cmd.o hns3pf/hclge_mdio.o hns3pf/hclge_tm.o \ hns3pf/hclge_mbx.o hns3pf/hclge_err.o hns3pf/hclge_debugfs.o hns3pf/hclge_ptp.o hns3pf/hclge_devlink.o \ hns3_common/hclge_comm_cmd.o hclge-$(CONFIG_HNS3_DCB) += hns3pf/hclge_dcb.o PK ! �B� � hisilicon/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # HISILICON device configuration # config NET_VENDOR_HISILICON bool "Hisilicon devices" default y depends on OF || ACPI depends on ARM || ARM64 || COMPILE_TEST help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Hisilicon devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_HISILICON config HIX5HD2_GMAC tristate "Hisilicon HIX5HD2 Family Network Device Support" select PHYLIB help This selects the hix5hd2 mac family network device. config HISI_FEMAC tristate "Hisilicon Fast Ethernet MAC device support" depends on HAS_IOMEM select PHYLIB select RESET_CONTROLLER help This selects the Hisilicon Fast Ethernet MAC device(FEMAC). The FEMAC receives and transmits data over Ethernet ports at 10/100 Mbps in full-duplex or half-duplex mode. The FEMAC exchanges data with the CPU, and supports the energy efficient Ethernet (EEE). config HIP04_ETH tristate "HISILICON P04 Ethernet support" depends on HAS_IOMEM # For MFD_SYSCON select MARVELL_PHY select MFD_SYSCON select HNS_MDIO help If you wish to compile a kernel for a hardware with hisilicon p04 SoC and want to use the internal ethernet then you should answer Y to this. config HI13X1_GMAC bool "Hisilicon HI13X1 Network Device Support" depends on HIP04_ETH help If you wish to compile a kernel for a hardware with hisilicon hi13x1_gamc then you should answer Y to this. This makes this driver suitable for use on certain boards such as the HI13X1. If you are unsure, say N. config HNS_MDIO tristate select PHYLIB help This selects the HNS MDIO support. It is needed by HNS_DSAF to access the PHY config HNS tristate help This selects the framework support for Hisilicon Network Subsystem. It is needed by any driver which provides HNS acceleration engine or make use of the engine config HNS_DSAF tristate "Hisilicon HNS DSAF device Support" select HNS select HNS_MDIO help This selects the DSAF (Distributed System Area Frabric) network acceleration engine support. The engine is used in Hisilicon hip05, Hi1610 and further ICT SoC config HNS_ENET tristate "Hisilicon HNS Ethernet Device Support" select PHYLIB select HNS help This selects the general ethernet driver for HNS. This module make use of any HNS AE driver, such as HNS_DSAF config HNS3 tristate "Hisilicon Network Subsystem Support HNS3 (Framework)" depends on PCI select NET_DEVLINK select PAGE_POOL help This selects the framework support for Hisilicon Network Subsystem 3. This layer facilitates clients like ENET, RoCE and user-space ethernet drivers(like ODP)to register with HNAE devices and their associated operations. if HNS3 config HNS3_HCLGE tristate "Hisilicon HNS3 HCLGE Acceleration Engine & Compatibility Layer Support" default m depends on PCI_MSI depends on PTP_1588_CLOCK_OPTIONAL help This selects the HNS3_HCLGE network acceleration engine & its hardware compatibility layer. The engine would be used in Hisilicon hip08 family of SoCs and further upcoming SoCs. config HNS3_DCB bool "Hisilicon HNS3 Data Center Bridge Support" default n depends on HNS3_HCLGE && DCB help Say Y here if you want to use Data Center Bridging (DCB) in the HNS3 driver. If unsure, say N. config HNS3_HCLGEVF tristate "Hisilicon HNS3VF Acceleration Engine & Compatibility Layer Support" depends on PCI_MSI depends on HNS3_HCLGE help This selects the HNS3 VF drivers network acceleration engine & its hardware compatibility layer. The engine would be used in Hisilicon hip08 family of SoCs and further upcoming SoCs. config HNS3_ENET tristate "Hisilicon HNS3 Ethernet Device Support" default m depends on 64BIT && PCI depends on INET select DIMLIB help This selects the Ethernet Driver for Hisilicon Network Subsystem 3 for hip08 family of SoCs. This module depends upon HNAE3 driver to access the HNAE3 devices and their associated operations. endif #HNS3 endif # NET_VENDOR_HISILICON PK ! ���5 5 hisilicon/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the HISILICON network device drivers. # obj-$(CONFIG_HIX5HD2_GMAC) += hix5hd2_gmac.o obj-$(CONFIG_HIP04_ETH) += hip04_eth.o obj-$(CONFIG_HNS_MDIO) += hns_mdio.o obj-$(CONFIG_HNS) += hns/ obj-$(CONFIG_HNS3) += hns3/ obj-$(CONFIG_HISI_FEMAC) += hisi_femac.o PK ! 9Y��� � neterion/vxge/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Exar Corp's X3100 Series 10 GbE PCIe I/O # Virtualized Server Adapter linux driver obj-$(CONFIG_VXGE) += vxge.o vxge-objs := vxge-config.o vxge-traffic.o vxge-ethtool.o vxge-main.o PK ! w' � � neterion/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Exar device configuration # config NET_VENDOR_NETERION bool "Neterion (Exar) devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Neterion/Exar cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_NETERION config S2IO tristate "Neterion (Exar) Xframe 10Gb Ethernet Adapter" depends on PCI help This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters. These were originally released from S2IO, which renamed itself Neterion. So, the adapters might be labeled as either one, depending on its age. More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/neterion/s2io.rst>. To compile this driver as a module, choose M here. The module will be called s2io. config VXGE tristate "Neterion (Exar) X3100 Series 10GbE PCIe Server Adapter" depends on PCI help This driver supports Exar Corp's X3100 Series 10 GbE PCIe I/O Virtualized Server Adapter. These were originally released from Neterion, which was later acquired by Exar. So, the adapters might be labeled as either one, depending on its age. More specific information on configuring the driver is in <file:Documentation/networking/device_drivers/ethernet/neterion/vxge.rst>. To compile this driver as a module, choose M here. The module will be called vxge. config VXGE_DEBUG_TRACE_ALL bool "Enabling All Debug trace statements in driver" default n depends on VXGE help Say Y here if you want to enabling all the debug trace statements in the vxge driver. By default only few debug trace statements are enabled. endif # NET_VENDOR_NETERION PK ! ���A� � neterion/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Exar network device drivers. # obj-$(CONFIG_S2IO) += s2io.o obj-$(CONFIG_VXGE) += vxge/ PK ! ���=X X emulex/benet/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config BE2NET tristate "ServerEngines' 10Gbps NIC - BladeEngine" depends on PCI help This driver implements the NIC functionality for ServerEngines' 10Gbps network adapter - BladeEngine. config BE2NET_HWMON bool "HWMON support for be2net driver" depends on BE2NET && HWMON depends on !(BE2NET=y && HWMON=m) default y help Say Y here if you want to expose thermal sensor data on be2net network adapter. config BE2NET_BE2 bool "Support for BE2 chipsets" depends on BE2NET default y help Say Y here if you want to use devices based on BE2 chipsets. (e.g. OneConnect OCe10xxx) config BE2NET_BE3 bool "Support for BE3 chipsets" depends on BE2NET default y help Say Y here if you want to use devices based on BE3 chipsets. (e.g. OneConnect OCe11xxx) config BE2NET_LANCER bool "Support for Lancer chipsets" depends on BE2NET default y help Say Y here if you want to use devices based on Lancer chipsets. (e.g LightPulse LPe12xxx) config BE2NET_SKYHAWK bool "Support for Skyhawk chipsets" depends on BE2NET default y help Say Y here if you want to use devices based on Skyhawk chipsets. (e.g. OneConnect OCe14xxx) comment "WARNING: be2net is useless without any enabled chip" depends on BE2NET_BE2=n && BE2NET_BE3=n && BE2NET_LANCER=n && \ BE2NET_SKYHAWK=n && BE2NET PK ! ��� � emulex/benet/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile to build the network driver for ServerEngine's BladeEngine. # obj-$(CONFIG_BE2NET) += be2net.o be2net-y := be_main.o be_cmds.o be_ethtool.o be_roce.o PK ! C��LL L emulex/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Emulex driver configuration # config NET_VENDOR_EMULEX bool "Emulex devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Emulex cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_EMULEX source "drivers/net/ethernet/emulex/benet/Kconfig" endif # NET_VENDOR_EMULEX PK ! 0���v v emulex/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Emulex device drivers. # obj-$(CONFIG_BE2NET) += benet/ PK ! �� *7 7 qualcomm/emac/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Qualcomm Technologies, Inc. EMAC Gigabit Ethernet driver # obj-$(CONFIG_QCOM_EMAC) += qcom-emac.o qcom-emac-objs := emac.o emac-mac.o emac-phy.o emac-sgmii.o emac-ethtool.o \ emac-sgmii-fsm9900.o emac-sgmii-qdf2432.o \ emac-sgmii-qdf2400.o PK ! � o�j j qualcomm/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Qualcomm network device configuration # config NET_VENDOR_QUALCOMM bool "Qualcomm devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Qualcomm cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_QUALCOMM config QCA7000 tristate help This enables support for the Qualcomm Atheros QCA7000. config QCA7000_SPI tristate "Qualcomm Atheros QCA7000 SPI support" select QCA7000 depends on SPI_MASTER && OF help This SPI protocol driver supports the Qualcomm Atheros QCA7000. To compile this driver as a module, choose M here. The module will be called qcaspi. config QCA7000_UART tristate "Qualcomm Atheros QCA7000 UART support" select QCA7000 depends on SERIAL_DEV_BUS && OF help This UART protocol driver supports the Qualcomm Atheros QCA7000. Currently the driver assumes these device UART settings: Data bits: 8 Parity: None Stop bits: 1 Flow control: None To compile this driver as a module, choose M here. The module will be called qcauart. config QCOM_EMAC tristate "Qualcomm Technologies, Inc. EMAC Gigabit Ethernet support" depends on HAS_DMA && HAS_IOMEM select CRC32 select PHYLIB help This driver supports the Qualcomm Technologies, Inc. Gigabit Ethernet Media Access Controller (EMAC). The controller supports IEEE 802.3-2002, half-duplex mode at 10/100 Mb/s, full-duplex mode at 10/100/1000Mb/s, Wake On LAN (WOL) for low power, Receive-Side Scaling (RSS), and IEEE 1588-2008 Precision Clock Synchronization Protocol. source "drivers/net/ethernet/qualcomm/rmnet/Kconfig" endif # NET_VENDOR_QUALCOMM PK ! 9�n� � qualcomm/rmnet/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # RMNET MAP driver # menuconfig RMNET tristate "RmNet MAP driver" default n select GRO_CELLS help If you select this, you will enable the RMNET module which is used for handling data in the multiplexing and aggregation protocol (MAP) format in the embedded data path. RMNET devices can be attached to any IP mode physical device. PK ! 4��� � qualcomm/rmnet/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the RMNET module # rmnet-y := rmnet_config.o rmnet-y += rmnet_vnd.o rmnet-y += rmnet_handlers.o rmnet-y += rmnet_map_data.o rmnet-y += rmnet_map_command.o obj-$(CONFIG_RMNET) += rmnet.o PK ! ���SK K qualcomm/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Qualcomm network device drivers. # obj-$(CONFIG_QCA7000) += qca_7k_common.o obj-$(CONFIG_QCA7000_SPI) += qcaspi.o qcaspi-objs := qca_7k.o qca_debug.o qca_spi.o obj-$(CONFIG_QCA7000_UART) += qcauart.o qcauart-objs := qca_uart.o obj-y += emac/ obj-$(CONFIG_RMNET) += rmnet/ PK ! r[�Kv v synopsys/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Synopsys network device configuration # config NET_VENDOR_SYNOPSYS bool "Synopsys devices" default y help If you have a network (Ethernet) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Synopsys devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_SYNOPSYS config DWC_XLGMAC tristate "Synopsys DWC Enterprise Ethernet (XLGMAC) driver support" depends on HAS_IOMEM && HAS_DMA select BITREVERSE select CRC32 help This driver supports the Synopsys DesignWare Cores Enterprise Ethernet (dwc-xlgmac). if DWC_XLGMAC config DWC_XLGMAC_PCI tristate "XLGMAC PCI bus support" depends on DWC_XLGMAC && PCI help This selects the pci bus support for the dwc-xlgmac driver. This driver was tested on Synopsys XLGMAC IP Prototyping Kit. If you have a controller with this interface, say Y or M here. If unsure, say N. endif # DWC_XLGMAC endif # NET_VENDOR_SYNOPSYS PK ! FI�; ; synopsys/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Synopsys network device drivers. # obj-$(CONFIG_DWC_XLGMAC) += dwc-xlgmac.o dwc-xlgmac-objs := dwc-xlgmac-net.o dwc-xlgmac-desc.o \ dwc-xlgmac-hw.o dwc-xlgmac-common.o \ dwc-xlgmac-ethtool.o dwc-xlgmac-$(CONFIG_DWC_XLGMAC_PCI) += dwc-xlgmac-pci.o PK ! f���J J alteon/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Alteon network device configuration # config NET_VENDOR_ALTEON bool "Alteon devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Alteon cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ALTEON config ACENIC tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" depends on PCI help Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet adapter. The driver allows for using the Jumbo Frame option (9000 bytes/frame) however it requires that your switches can handle this as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig line. To compile this driver as a module, choose M here: the module will be called acenic. config ACENIC_OMIT_TIGON_I bool "Omit support for old Tigon I based AceNICs" depends on ACENIC help Say Y here if you only have Tigon II based AceNICs and want to leave out support for the older Tigon I based cards which are no longer being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B version)). This will reduce the size of the driver object by app. 100KB. If you are not sure whether your card is a Tigon I or a Tigon II, say N here. The safe and default value for this is N. endif # NET_VENDOR_ALTEON PK ! �_{� � alteon/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Alteon network device drivers. # obj-$(CONFIG_ACENIC) += acenic.o PK ! :B�W W pensando/ionic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright(c) 2017 - 2019 Pensando Systems, Inc obj-$(CONFIG_IONIC) := ionic.o ionic-y := ionic_main.o ionic_bus_pci.o ionic_devlink.o ionic_dev.o \ ionic_debugfs.o ionic_lif.o ionic_rx_filter.o ionic_ethtool.o \ ionic_txrx.o ionic_stats.o ionic_fw.o ionic-$(CONFIG_PTP_1588_CLOCK) += ionic_phc.o PK ! Y �� pensando/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 # Copyright (c) 2019 Pensando Systems, Inc # # Pensando device configuration # config NET_VENDOR_PENSANDO bool "Pensando devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Pensando cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_PENSANDO config IONIC tristate "Pensando Ethernet IONIC Support" depends on 64BIT && PCI depends on PTP_1588_CLOCK_OPTIONAL select NET_DEVLINK select DIMLIB help This enables the support for the Pensando family of Ethernet adapters. More specific information on this driver can be found in <file:Documentation/networking/device_drivers/ethernet/pensando/ionic.rst>. To compile this driver as a module, choose M here. The module will be called ionic. endif # NET_VENDOR_PENSANDO PK ! ����z z pensando/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Pensando network device drivers. # obj-$(CONFIG_IONIC) += ionic/ PK ! q�$ $ calxeda/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_CALXEDA_XGMAC tristate "Calxeda 1G/10G XGMAC Ethernet driver" depends on HAS_IOMEM depends on ARCH_HIGHBANK || COMPILE_TEST select CRC32 help This is the driver for the XGMAC Ethernet IP block found on Calxeda Highbank platforms. PK ! a��S S calxeda/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_NET_CALXEDA_XGMAC) += xgmac.o PK ! q"�#c c microchip/sparx5/Kconfignu �[��� config SPARX5_SWITCH tristate "Sparx5 switch driver" depends on NET_SWITCHDEV depends on HAS_IOMEM depends on OF depends on ARCH_SPARX5 || COMPILE_TEST depends on PTP_1588_CLOCK_OPTIONAL depends on BRIDGE || BRIDGE=n select PHYLINK select PHY_SPARX5_SERDES select RESET_CONTROLLER help This driver supports the Sparx5 network switch device. PK ! ߅��g g microchip/sparx5/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Microchip Sparx5 network device drivers. # obj-$(CONFIG_SPARX5_SWITCH) += sparx5-switch.o sparx5-switch-objs := sparx5_main.o sparx5_packet.o \ sparx5_netdev.o sparx5_phylink.o sparx5_port.o sparx5_mactable.o sparx5_vlan.o \ sparx5_switchdev.o sparx5_calendar.o sparx5_ethtool.o sparx5_fdma.o PK ! ���� microchip/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Microchip network device configuration # config NET_VENDOR_MICROCHIP bool "Microchip devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Microchip cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_MICROCHIP config ENC28J60 tristate "ENC28J60 support" depends on SPI select CRC32 help Support for the Microchip EN28J60 ethernet chip. To compile this driver as a module, choose M here. The module will be called enc28j60. config ENC28J60_WRITEVERIFY bool "Enable write verify" depends on ENC28J60 help Enable the verify after the buffer write useful for debugging purpose. If unsure, say N. config ENCX24J600 tristate "ENCX24J600 support" depends on SPI help Support for the Microchip ENC424J600/624J600 ethernet chip. To compile this driver as a module, choose M here. The module will be called encx24j600. config LAN743X tristate "LAN743x support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select PHYLIB select CRC16 select CRC32 help Support for the Microchip LAN743x PCI Express Gigabit Ethernet chip To compile this driver as a module, choose M here. The module will be called lan743x. source "drivers/net/ethernet/microchip/sparx5/Kconfig" endif # NET_VENDOR_MICROCHIP PK ! ۲�O O microchip/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Microchip network device drivers. # obj-$(CONFIG_ENC28J60) += enc28j60.o obj-$(CONFIG_ENCX24J600) += encx24j600.o encx24j600-regmap.o obj-$(CONFIG_LAN743X) += lan743x.o lan743x-objs := lan743x_main.o lan743x_ethtool.o lan743x_ptp.o obj-$(CONFIG_SPARX5_SWITCH) += sparx5/ PK ! {��� � samsung/sxgbe/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_SXGBE_ETH) += samsung-sxgbe.o samsung-sxgbe-objs:= sxgbe_platform.o sxgbe_main.o sxgbe_desc.o \ sxgbe_dma.o sxgbe_core.o sxgbe_mtl.o sxgbe_mdio.o \ sxgbe_ethtool.o $(samsung-sxgbe-y) PK ! ��� � samsung/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Samsung Ethernet device configuration # config NET_VENDOR_SAMSUNG bool "Samsung Ethernet devices" default y help If you have a network (Ethernet) chipset belonging to this class, say Y. Note that the answer to this question does not directly affect the kernel: saying N will just cause the configurator to skip all the questions about Samsung chipsets. If you say Y, you will be asked for your specific chipset/driver in the following questions. if NET_VENDOR_SAMSUNG config SXGBE_ETH tristate "Samsung 10G/2.5G/1G SXGBE Ethernet driver" depends on HAS_IOMEM && HAS_DMA depends on PTP_1588_CLOCK_OPTIONAL select PHYLIB select CRC32 help This is the driver for the SXGBE 10G Ethernet IP block found on Samsung platforms. To compile this driver as a module, choose M here: the module will be called samsung-sxgbe. endif # NET_VENDOR_SAMSUNG PK ! �+��� � samsung/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Samsung Ethernet device drivers. # obj-$(CONFIG_SXGBE_ETH) += sxgbe/ PK ! �c4� � toshiba/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Toshiba network device configuration # config NET_VENDOR_TOSHIBA bool "Toshiba devices" default y depends on PCI && (PPC_IBM_CELL_BLADE || MIPS) || PPC_PS3 help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Toshiba cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_TOSHIBA config GELIC_NET tristate "PS3 Gigabit Ethernet driver" depends on PPC_PS3 select PS3_SYS_MANAGER help This driver supports the network device on the PS3 game console. This driver has built-in support for Ethernet. To compile this driver as a module, choose M here: the module will be called ps3_gelic. config GELIC_WIRELESS bool "PS3 Wireless support" depends on GELIC_NET && WLAN select WIRELESS_EXT help This option adds the support for the wireless feature of PS3. If you have the wireless-less model of PS3 or have no plan to use wireless feature, disabling this option saves memory. As the driver automatically distinguishes the models, you can safely enable this option even if you have a wireless-less model. config SPIDER_NET tristate "Spider Gigabit Ethernet driver" depends on PCI && PPC_IBM_CELL_BLADE select FW_LOADER select SUNGEM_PHY help This driver supports the Gigabit Ethernet chips present on the Cell Processor-Based Blades from IBM. config TC35815 tristate "TOSHIBA TC35815 Ethernet support" depends on PCI && MIPS select PHYLIB endif # NET_VENDOR_TOSHIBA PK ! �ˉLt t toshiba/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Toshiba network device drivers. # obj-$(CONFIG_GELIC_NET) += ps3_gelic.o gelic_wireless-$(CONFIG_GELIC_WIRELESS) += ps3_gelic_wireless.o ps3_gelic-objs += ps3_gelic_net.o $(gelic_wireless-y) spidernet-y += spider_net.o spider_net_ethtool.o obj-$(CONFIG_SPIDER_NET) += spidernet.o obj-$(CONFIG_TC35815) += tc35815.o PK ! }�n realtek/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Realtek device configuration # config NET_VENDOR_REALTEK bool "Realtek devices" default y depends on PCI || (PARPORT && X86) help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Realtek devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_REALTEK config ATP tristate "AT-LAN-TEC/RealTek pocket adapter support" depends on PARPORT && X86 select CRC32 help This is a network (Ethernet) device which attaches to your parallel port. Read the file <file:drivers/net/ethernet/realtek/atp.c> if you want to use this. If you intend to use this driver, you should have said N to the "Parallel printer support", because the two drivers don't like each other. To compile this driver as a module, choose M here: the module will be called atp. config 8139CP tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support" depends on PCI select CRC32 select MII help This is a driver for the Fast Ethernet PCI network cards based on the RTL8139C+ chips. If you have one of those, say Y here. To compile this driver as a module, choose M here: the module will be called 8139cp. This is recommended. config 8139TOO tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" depends on PCI select CRC32 select MII help This is a driver for the Fast Ethernet PCI network cards based on the RTL 8129/8130/8139 chips. If you have one of those, say Y here. To compile this driver as a module, choose M here: the module will be called 8139too. This is recommended. config 8139TOO_PIO bool "Use PIO instead of MMIO" default y depends on 8139TOO help This instructs the driver to use programmed I/O ports (PIO) instead of PCI shared memory (MMIO). This can possibly solve some problems in case your mainboard has memory consistency issues. If unsure, say N. config 8139TOO_TUNE_TWISTER bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" depends on 8139TOO help This implements a function which might come in handy in case you are using low quality on long cabling. It is required for RealTek RTL-8139 revision K boards, and totally unused otherwise. It tries to match the transceiver to the cable characteristics. This is experimental since hardly documented by the manufacturer. If unsure, say Y. config 8139TOO_8129 bool "Support for older RTL-8129/8130 boards" depends on 8139TOO help This enables support for the older and uncommon RTL-8129 and RTL-8130 chips, which support MII via an external transceiver, instead of an internal one. Disabling this option will save some memory by making the code size smaller. If unsure, say Y. config 8139_OLD_RX_RESET bool "Use older RX-reset method" depends on 8139TOO help The 8139too driver was recently updated to contain a more rapid reset sequence, in the face of severe receive errors. This "new" RX-reset method should be adequate for all boards. But if you experience problems, you can enable this option to restore the old RX-reset behavior. If unsure, say N. config R8169 tristate "Realtek 8169/8168/8101/8125 ethernet support" depends on PCI select FW_LOADER select CRC32 select PHYLIB select REALTEK_PHY help Say Y here if you have a Realtek Ethernet adapter belonging to the following families: RTL8169 Gigabit Ethernet RTL8168 Gigabit Ethernet RTL8101 Fast Ethernet RTL8125 2.5GBit Ethernet To compile this driver as a module, choose M here: the module will be called r8169. This is recommended. endif # NET_VENDOR_REALTEK PK ! �:�� realtek/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Realtek network device drivers. # obj-$(CONFIG_8139CP) += 8139cp.o obj-$(CONFIG_8139TOO) += 8139too.o obj-$(CONFIG_ATP) += atp.o r8169-objs += r8169_main.o r8169_firmware.o r8169_phy_config.o obj-$(CONFIG_R8169) += r8169.o PK ! �h�s� � mellanox/mlxsw/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Mellanox switch drivers configuration # config MLXSW_CORE tristate "Mellanox Technologies Switch ASICs support" select NET_DEVLINK select MLXFW help This driver supports Mellanox Technologies Switch ASICs family. To compile this driver as a module, choose M here: the module will be called mlxsw_core. config MLXSW_CORE_HWMON bool "HWMON support for Mellanox Technologies Switch ASICs" depends on MLXSW_CORE && HWMON depends on !(MLXSW_CORE=y && HWMON=m) default y help Say Y here if you want to expose HWMON interface on mlxsw devices. config MLXSW_CORE_THERMAL bool "Thermal zone support for Mellanox Technologies Switch ASICs" depends on MLXSW_CORE && THERMAL default y help Say Y here if you want to automatically control fans speed according ambient temperature reported by ASIC. config MLXSW_PCI tristate "PCI bus implementation for Mellanox Technologies Switch ASICs" depends on PCI && HAS_IOMEM && MLXSW_CORE default m help This is PCI bus implementation for Mellanox Technologies Switch ASICs. To compile this driver as a module, choose M here: the module will be called mlxsw_pci. config MLXSW_I2C tristate "I2C bus implementation for Mellanox Technologies Switch ASICs" depends on I2C && MLXSW_CORE default m help This is I2C bus implementation for Mellanox Technologies Switch ASICs. To compile this driver as a module, choose M here: the module will be called mlxsw_i2c. config MLXSW_SPECTRUM tristate "Mellanox Technologies Spectrum family support" depends on MLXSW_CORE && MLXSW_PCI && NET_SWITCHDEV && VLAN_8021Q depends on PSAMPLE || PSAMPLE=n depends on BRIDGE || BRIDGE=n depends on IPV6 || IPV6=n depends on NET_IPGRE || NET_IPGRE=n depends on IPV6_GRE || IPV6_GRE=n depends on VXLAN || VXLAN=n depends on PTP_1588_CLOCK_OPTIONAL select GENERIC_ALLOCATOR select PARMAN select OBJAGG select NET_PTP_CLASSIFY if PTP_1588_CLOCK default m help This driver supports Mellanox Technologies Spectrum/Spectrum-2/Spectrum-3 Ethernet Switch ASICs. To compile this driver as a module, choose M here: the module will be called mlxsw_spectrum. config MLXSW_SPECTRUM_DCB bool "Data Center Bridging (DCB) support" depends on MLXSW_SPECTRUM && DCB default y help Say Y here if you want to use Data Center Bridging (DCB) in the driver. config MLXSW_MINIMAL tristate "Mellanox Technologies minimal I2C support" depends on MLXSW_CORE && MLXSW_I2C default m help This driver supports I2C access for Mellanox Technologies Switch ASICs. To compile this driver as a module, choose M here: the module will be called mlxsw_minimal. PK ! %�� � mellanox/mlxsw/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_MLXSW_CORE) += mlxsw_core.o mlxsw_core-objs := core.o core_acl_flex_keys.o \ core_acl_flex_actions.o core_env.o mlxsw_core-$(CONFIG_MLXSW_CORE_HWMON) += core_hwmon.o mlxsw_core-$(CONFIG_MLXSW_CORE_THERMAL) += core_thermal.o obj-$(CONFIG_MLXSW_PCI) += mlxsw_pci.o mlxsw_pci-objs := pci.o obj-$(CONFIG_MLXSW_I2C) += mlxsw_i2c.o mlxsw_i2c-objs := i2c.o obj-$(CONFIG_MLXSW_SPECTRUM) += mlxsw_spectrum.o mlxsw_spectrum-objs := spectrum.o spectrum_buffers.o \ spectrum_switchdev.o spectrum_router.o \ spectrum_router_xm.o \ spectrum1_kvdl.o spectrum2_kvdl.o \ spectrum_kvdl.o \ spectrum_acl_tcam.o spectrum_acl_ctcam.o \ spectrum_acl_atcam.o spectrum_acl_erp.o \ spectrum1_acl_tcam.o spectrum2_acl_tcam.o \ spectrum_acl_bloom_filter.o spectrum_acl.o \ spectrum_flow.o spectrum_matchall.o \ spectrum_flower.o spectrum_cnt.o \ spectrum_fid.o spectrum_ipip.o \ spectrum_acl_flex_actions.o \ spectrum_acl_flex_keys.o \ spectrum1_mr_tcam.o spectrum2_mr_tcam.o \ spectrum_mr_tcam.o spectrum_mr.o \ spectrum_qdisc.o spectrum_span.o \ spectrum_nve.o spectrum_nve_vxlan.o \ spectrum_dpipe.o spectrum_trap.o \ spectrum_ethtool.o spectrum_policer.o mlxsw_spectrum-$(CONFIG_MLXSW_SPECTRUM_DCB) += spectrum_dcb.o mlxsw_spectrum-$(CONFIG_PTP_1588_CLOCK) += spectrum_ptp.o obj-$(CONFIG_MLXSW_MINIMAL) += mlxsw_minimal.o mlxsw_minimal-objs := minimal.o PK ! �Z_� � mellanox/mlxbf_gige/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause # # Mellanox GigE driver configuration # config MLXBF_GIGE tristate "Mellanox Technologies BlueField Gigabit Ethernet support" depends on (ARM64 && ACPI) || COMPILE_TEST select PHYLIB help The second generation BlueField SoC from Mellanox Technologies supports an out-of-band Gigabit Ethernet management port to the Arm subsystem. PK ! � �� � mellanox/mlxbf_gige/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause obj-$(CONFIG_MLXBF_GIGE) += mlxbf_gige.o mlxbf_gige-y := mlxbf_gige_ethtool.o \ mlxbf_gige_intr.o \ mlxbf_gige_main.o \ mlxbf_gige_mdio.o \ mlxbf_gige_rx.o \ mlxbf_gige_tx.o PK ! ��� mellanox/mlx4/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Mellanox driver configuration # config MLX4_EN tristate "Mellanox Technologies 1/10/40Gbit Ethernet support" depends on PCI && NETDEVICES && ETHERNET && INET depends on PTP_1588_CLOCK_OPTIONAL select MLX4_CORE help This driver supports Mellanox Technologies ConnectX Ethernet devices. config MLX4_EN_DCB bool "Data Center Bridging (DCB) Support" default y depends on MLX4_EN && DCB help Say Y here if you want to use Data Center Bridging (DCB) in the driver. If set to N, will not be able to configure QoS and ratelimit attributes. This flag is depended on the kernel's DCB support. If unsure, set to Y config MLX4_CORE tristate depends on PCI select NET_DEVLINK default n config MLX4_DEBUG bool "Verbose debugging output" if (MLX4_CORE && EXPERT) depends on MLX4_CORE default y help This option causes debugging code to be compiled into the mlx4_core driver. The output can be turned on via the debug_level module parameter (which can also be set after the driver is loaded through sysfs). config MLX4_CORE_GEN2 bool "Support for old gen2 Mellanox PCI IDs" if (MLX4_CORE) depends on MLX4_CORE default y help Say Y here if you want to use old gen2 Mellanox devices in the driver. PK ! �F<�� � mellanox/mlx4/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_MLX4_CORE) += mlx4_core.o mlx4_core-y := alloc.o catas.o cmd.o cq.o eq.o fw.o fw_qos.o icm.o intf.o \ main.o mcg.o mr.o pd.o port.o profile.o qp.o reset.o sense.o \ srq.o resource_tracker.o crdump.o obj-$(CONFIG_MLX4_EN) += mlx4_en.o mlx4_en-y := en_main.o en_tx.o en_rx.o en_ethtool.o en_port.o en_cq.o \ en_resources.o en_netdev.o en_selftest.o en_clock.o mlx4_en-$(CONFIG_MLX4_EN_DCB) += en_dcb_nl.o PK ! �?�w w mellanox/mlxfw/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Mellanox firmware flash library configuration # config MLXFW tristate "Mellanox Technologies firmware flash module" help This driver supports Mellanox Technologies Firmware flashing common logic. To compile this driver as a module, choose M here: the module will be called mlxfw. select XZ_DEC select NET_DEVLINK PK ! ��JL� � mellanox/mlxfw/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_MLXFW) += mlxfw.o mlxfw-objs := mlxfw_fsm.o mlxfw_mfa2_tlv_multi.o mlxfw_mfa2.o PK ! r1��J J mellanox/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Mellanox driver configuration # config NET_VENDOR_MELLANOX bool "Mellanox devices" default y depends on PCI || I2C help If you have a network (Ethernet or RDMA) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Mellanox cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_MELLANOX source "drivers/net/ethernet/mellanox/mlx4/Kconfig" source "drivers/net/ethernet/mellanox/mlx5/core/Kconfig" source "drivers/net/ethernet/mellanox/mlxsw/Kconfig" source "drivers/net/ethernet/mellanox/mlxfw/Kconfig" source "drivers/net/ethernet/mellanox/mlxbf_gige/Kconfig" endif # NET_VENDOR_MELLANOX PK ! 4Q:� mellanox/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Mellanox device drivers. # obj-$(CONFIG_MLX4_CORE) += mlx4/ obj-$(CONFIG_MLX5_CORE) += mlx5/core/ obj-$(CONFIG_MLXSW_CORE) += mlxsw/ obj-$(CONFIG_MLXFW) += mlxfw/ obj-$(CONFIG_MLXBF_GIGE) += mlxbf_gige/ PK ! �l�x x mellanox/mlx5/core/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Mellanox driver configuration # config MLX5_CORE tristate "Mellanox 5th generation network adapters (ConnectX series) core driver" depends on PCI select AUXILIARY_BUS select NET_DEVLINK depends on VXLAN || !VXLAN depends on MLXFW || !MLXFW depends on PTP_1588_CLOCK_OPTIONAL depends on PCI_HYPERV_INTERFACE || !PCI_HYPERV_INTERFACE help Core driver for low level functionality of the ConnectX-4 and Connect-IB cards by Mellanox Technologies. config MLX5_ACCEL bool config MLX5_FPGA bool "Mellanox Technologies Innova support" depends on MLX5_CORE select MLX5_ACCEL help Build support for the Innova family of network cards by Mellanox Technologies. Innova network cards are comprised of a ConnectX chip and an FPGA chip on one board. If you select this option, the mlx5_core driver will include the Innova FPGA core and allow building sandbox-specific client drivers. config MLX5_CORE_EN bool "Mellanox 5th generation network adapters (ConnectX series) Ethernet support" depends on NETDEVICES && ETHERNET && INET && PCI && MLX5_CORE select PAGE_POOL select DIMLIB help Ethernet support in Mellanox Technologies ConnectX-4 NIC. config MLX5_EN_ARFS bool "Mellanox MLX5 ethernet accelerated receive flow steering (ARFS) support" depends on MLX5_CORE_EN && RFS_ACCEL default y help Mellanox MLX5 ethernet hardware-accelerated receive flow steering support, Enables ethernet netdevice arfs support and ntuple filtering. config MLX5_EN_RXNFC bool "Mellanox MLX5 ethernet rx nfc flow steering support" depends on MLX5_CORE_EN default y help Mellanox MLX5 ethernet rx nfc flow steering support Enables ethtool receive network flow classification, which allows user defined flow rules to direct traffic into arbitrary rx queue via ethtool set/get_rxnfc API. config MLX5_MPFS bool "Mellanox Technologies MLX5 MPFS support" depends on MLX5_CORE_EN default y help Mellanox Technologies Ethernet Multi-Physical Function Switch (MPFS) support in ConnectX NIC. MPFs is required for when multi-PF configuration is enabled to allow passing user configured unicast MAC addresses to the requesting PF. config MLX5_ESWITCH bool "Mellanox Technologies MLX5 SRIOV E-Switch support" depends on MLX5_CORE_EN && NET_SWITCHDEV default y help Mellanox Technologies Ethernet SRIOV E-Switch support in ConnectX NIC. E-Switch provides internal SRIOV packet steering and switching for the enabled VFs and PF in two available modes: Legacy SRIOV mode (L2 mac vlan steering based). Switchdev mode (eswitch offloads). config MLX5_BRIDGE bool depends on MLX5_ESWITCH && BRIDGE default y help mlx5 ConnectX offloads support for Ethernet Bridging (BRIDGE). Enable adding representors of mlx5 uplink and VF ports to Bridge and offloading rules for traffic between such ports. Supports VLANs (trunk and access modes). config MLX5_CLS_ACT bool "MLX5 TC classifier action support" depends on MLX5_ESWITCH && NET_CLS_ACT default y help mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT), works in both native NIC mode and Switchdev SRIOV mode. Actions get attached to a Hardware offloaded classifiers and are invoked after a successful classification. Actions are used to overwrite the classification result, instantly drop or redirect and/or reformat packets in wire speeds without involving the host cpu. If set to N, TC offloads in both NIC and switchdev modes will be disabled. If unsure, set to Y config MLX5_TC_CT bool "MLX5 TC connection tracking offload support" depends on MLX5_CLS_ACT && NF_FLOW_TABLE && NET_ACT_CT && NET_TC_SKB_EXT default y help Say Y here if you want to support offloading connection tracking rules via tc ct action. If unsure, set to Y config MLX5_TC_SAMPLE bool "MLX5 TC sample offload support" depends on MLX5_CLS_ACT default y help Say Y here if you want to support offloading sample rules via tc sample action. If set to N, will not be able to configure tc rules with sample action. If unsure, set to Y config MLX5_CORE_EN_DCB bool "Data Center Bridging (DCB) Support" default y depends on MLX5_CORE_EN && DCB help Say Y here if you want to use Data Center Bridging (DCB) in the driver. If set to N, will not be able to configure QoS and ratelimit attributes. This flag is depended on the kernel's DCB support. If unsure, set to Y config MLX5_CORE_IPOIB bool "Mellanox 5th generation network adapters (connectX series) IPoIB offloads support" depends on MLX5_CORE_EN help MLX5 IPoIB offloads & acceleration support. config MLX5_FPGA_IPSEC bool "Mellanox Technologies IPsec Innova support" depends on MLX5_CORE depends on MLX5_FPGA help Build IPsec support for the Innova family of network cards by Mellanox Technologies. Innova network cards are comprised of a ConnectX chip and an FPGA chip on one board. If you select this option, the mlx5_core driver will include the Innova FPGA core and allow building sandbox-specific client drivers. config MLX5_IPSEC bool "Mellanox Technologies IPsec Connect-X support" depends on MLX5_CORE_EN depends on XFRM_OFFLOAD depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD select MLX5_ACCEL help Build IPsec support for the Connect-X family of network cards by Mellanox Technologies. Note: If you select this option, the mlx5_core driver will include IPsec support for the Connect-X family. config MLX5_EN_IPSEC bool "IPSec XFRM cryptography-offload acceleration" depends on MLX5_CORE_EN depends on XFRM_OFFLOAD depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD depends on MLX5_FPGA_IPSEC || MLX5_IPSEC help Build support for IPsec cryptography-offload acceleration in the NIC. Note: Support for hardware with this capability needs to be selected for this option to become available. config MLX5_FPGA_TLS bool "Mellanox Technologies TLS Innova support" depends on TLS_DEVICE depends on TLS=y || MLX5_CORE=m depends on MLX5_CORE_EN depends on MLX5_FPGA select MLX5_EN_TLS help Build TLS support for the Innova family of network cards by Mellanox Technologies. Innova network cards are comprised of a ConnectX chip and an FPGA chip on one board. If you select this option, the mlx5_core driver will include the Innova FPGA core and allow building sandbox-specific client drivers. config MLX5_TLS bool "Mellanox Technologies TLS Connect-X support" depends on TLS_DEVICE depends on TLS=y || MLX5_CORE=m depends on MLX5_CORE_EN select MLX5_ACCEL select MLX5_EN_TLS help Build TLS support for the Connect-X family of network cards by Mellanox Technologies. config MLX5_EN_TLS bool help Build support for TLS cryptography-offload acceleration in the NIC. Note: Support for hardware with this capability needs to be selected for this option to become available. config MLX5_SW_STEERING bool "Mellanox Technologies software-managed steering" depends on MLX5_CORE_EN && MLX5_ESWITCH select CRC32 default y help Build support for software-managed steering in the NIC. config MLX5_SF bool "Mellanox Technologies subfunction device support using auxiliary device" depends on MLX5_CORE && MLX5_CORE_EN help Build support for subfuction device in the NIC. A Mellanox subfunction device can support RDMA, netdevice and vdpa device. It is similar to a SRIOV VF but it doesn't require SRIOV support. config MLX5_SF_MANAGER bool depends on MLX5_SF && MLX5_ESWITCH default y help Build support for subfuction port in the NIC. A Mellanox subfunction port is managed through devlink. A subfunction supports RDMA, netdevice and vdpa device. It is similar to a SRIOV VF but it doesn't require SRIOV support. PK ! ߥȋ\ \ mellanox/mlx5/core/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Mellanox 5th generation network adapters # (ConnectX series) core & netdev driver # subdir-ccflags-y += -I$(src) obj-$(CONFIG_MLX5_CORE) += mlx5_core.o # # mlx5 core basic # mlx5_core-y := main.o cmd.o debugfs.o fw.o eq.o uar.o pagealloc.o \ health.o mcg.o cq.o alloc.o port.o mr.o pd.o \ transobj.o vport.o sriov.o fs_cmd.o fs_core.o pci_irq.o \ fs_counters.o fs_ft_pool.o rl.o lag.o dev.o events.o wq.o lib/gid.o \ lib/devcom.o lib/pci_vsc.o lib/dm.o lib/fs_ttc.o diag/fs_tracepoint.o \ diag/fw_tracer.o diag/crdump.o devlink.o diag/rsc_dump.o \ fw_reset.o qos.o # # Netdev basic # mlx5_core-$(CONFIG_MLX5_CORE_EN) += en/rqt.o en/tir.o en/rss.o en/rx_res.o \ en/channels.o en_main.o en_common.o en_fs.o en_ethtool.o \ en_tx.o en_rx.o en_dim.o en_txrx.o en/xdp.o en_stats.o \ en_selftest.o en/port.o en/monitor_stats.o en/health.o \ en/reporter_tx.o en/reporter_rx.o en/params.o en/xsk/pool.o \ en/xsk/setup.o en/xsk/rx.o en/xsk/tx.o en/devlink.o en/ptp.o \ en/qos.o en/trap.o en/fs_tt_redirect.o # # Netdev extra # mlx5_core-$(CONFIG_MLX5_EN_ARFS) += en_arfs.o mlx5_core-$(CONFIG_MLX5_EN_RXNFC) += en_fs_ethtool.o mlx5_core-$(CONFIG_MLX5_CORE_EN_DCB) += en_dcbnl.o en/port_buffer.o mlx5_core-$(CONFIG_PCI_HYPERV_INTERFACE) += en/hv_vhca_stats.o mlx5_core-$(CONFIG_MLX5_ESWITCH) += lag_mp.o lib/geneve.o lib/port_tun.o \ en_rep.o en/rep/bond.o en/mod_hdr.o \ en/mapping.o mlx5_core-$(CONFIG_MLX5_CLS_ACT) += en_tc.o en/rep/tc.o en/rep/neigh.o \ lib/fs_chains.o en/tc_tun.o \ esw/indir_table.o en/tc_tun_encap.o \ en/tc_tun_vxlan.o en/tc_tun_gre.o en/tc_tun_geneve.o \ en/tc_tun_mplsoudp.o diag/en_tc_tracepoint.o \ en/tc/post_act.o en/tc/int_port.o mlx5_core-$(CONFIG_MLX5_TC_CT) += en/tc_ct.o mlx5_core-$(CONFIG_MLX5_TC_SAMPLE) += en/tc/sample.o # # Core extra # mlx5_core-$(CONFIG_MLX5_ESWITCH) += eswitch.o eswitch_offloads.o eswitch_offloads_termtbl.o \ ecpf.o rdma.o esw/legacy.o \ esw/devlink_port.o esw/vporttbl.o esw/qos.o mlx5_core-$(CONFIG_MLX5_ESWITCH) += esw/acl/helper.o \ esw/acl/egress_lgcy.o esw/acl/egress_ofld.o \ esw/acl/ingress_lgcy.o esw/acl/ingress_ofld.o mlx5_core-$(CONFIG_MLX5_BRIDGE) += esw/bridge.o en/rep/bridge.o mlx5_core-$(CONFIG_MLX5_MPFS) += lib/mpfs.o mlx5_core-$(CONFIG_VXLAN) += lib/vxlan.o mlx5_core-$(CONFIG_PTP_1588_CLOCK) += lib/clock.o mlx5_core-$(CONFIG_PCI_HYPERV_INTERFACE) += lib/hv.o lib/hv_vhca.o # # Ipoib netdev # mlx5_core-$(CONFIG_MLX5_CORE_IPOIB) += ipoib/ipoib.o ipoib/ethtool.o ipoib/ipoib_vlan.o # # Accelerations & FPGA # mlx5_core-$(CONFIG_MLX5_IPSEC) += accel/ipsec_offload.o mlx5_core-$(CONFIG_MLX5_FPGA_IPSEC) += fpga/ipsec.o mlx5_core-$(CONFIG_MLX5_FPGA_TLS) += fpga/tls.o mlx5_core-$(CONFIG_MLX5_ACCEL) += lib/crypto.o accel/tls.o accel/ipsec.o mlx5_core-$(CONFIG_MLX5_FPGA) += fpga/cmd.o fpga/core.o fpga/conn.o fpga/sdk.o mlx5_core-$(CONFIG_MLX5_EN_IPSEC) += en_accel/ipsec.o en_accel/ipsec_rxtx.o \ en_accel/ipsec_stats.o en_accel/ipsec_fs.o mlx5_core-$(CONFIG_MLX5_EN_TLS) += en_accel/tls.o en_accel/tls_rxtx.o en_accel/tls_stats.o \ en_accel/fs_tcp.o en_accel/ktls.o en_accel/ktls_txrx.o \ en_accel/ktls_tx.o en_accel/ktls_rx.o mlx5_core-$(CONFIG_MLX5_SW_STEERING) += steering/dr_domain.o steering/dr_table.o \ steering/dr_matcher.o steering/dr_rule.o \ steering/dr_icm_pool.o steering/dr_buddy.o \ steering/dr_ste.o steering/dr_send.o \ steering/dr_ste_v0.o steering/dr_ste_v1.o \ steering/dr_ste_v2.o \ steering/dr_cmd.o steering/dr_fw.o \ steering/dr_action.o steering/fs_dr.o \ steering/dr_dbg.o # # SF device # mlx5_core-$(CONFIG_MLX5_SF) += sf/vhca_event.o sf/dev/dev.o sf/dev/driver.o # # SF manager # mlx5_core-$(CONFIG_MLX5_SF_MANAGER) += sf/cmd.o sf/hw_table.o sf/devlink.o PK ! ��l�H H mellanox/mlx5/core/esw/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only subdir-ccflags-y += -I$(src)/.. PK ! ��l�H H $ mellanox/mlx5/core/steering/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only subdir-ccflags-y += -I$(src)/.. PK ! �FX@ @ fujitsu/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Fujitsu Network device configuration # config NET_VENDOR_FUJITSU bool "Fujitsu devices" default y depends on PCMCIA help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the the questions about Fujitsu cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_FUJITSU config PCMCIA_FMVJ18X tristate "Fujitsu FMV-J18x PCMCIA support" depends on PCMCIA select CRC32 help Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible PCMCIA (PC-card) Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called fmvj18x_cs. If unsure, say N. endif # NET_VENDOR_FUJITSU PK ! [З;� � fujitsu/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Fujitsu network device drivers. # obj-$(CONFIG_PCMCIA_FMVJ18X) += fmvj18x_cs.o PK ! �w�þ � google/gve/Makefilenu �[��� # Makefile for the Google virtual Ethernet (gve) driver obj-$(CONFIG_GVE) += gve.o gve-objs := gve_main.o gve_tx.o gve_tx_dqo.o gve_rx.o gve_rx_dqo.o gve_ethtool.o gve_adminq.o gve_utils.o PK ! .��� � google/Kconfignu �[��� # # Google network device configuration # config NET_VENDOR_GOOGLE bool "Google Devices" default y help If you have a network (Ethernet) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Google devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_GOOGLE config GVE tristate "Google Virtual NIC (gVNIC) support" depends on (PCI_MSI && (X86 || CPU_LITTLE_ENDIAN)) help This driver supports Google Virtual NIC (gVNIC)" To compile this driver as a module, choose M here. The module will be called gve. endif #NET_VENDOR_GOOGLE PK ! NufQ Q google/Makefilenu �[��� # # Makefile for the Google network device drivers. # obj-$(CONFIG_GVE) += gve/ PK ! ����* * mscc/Kconfignu �[��� # SPDX-License-Identifier: (GPL-2.0 OR MIT) config NET_VENDOR_MICROSEMI bool "Microsemi devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Microsemi devices. if NET_VENDOR_MICROSEMI # Users should depend on NET_SWITCHDEV, HAS_IOMEM, BRIDGE config MSCC_OCELOT_SWITCH_LIB select NET_DEVLINK select REGMAP_MMIO select PACKING select PHYLINK tristate help This is a hardware support library for Ocelot network switches. It is used by switchdev as well as by DSA drivers. config MSCC_OCELOT_SWITCH tristate "Ocelot switch driver" depends on PTP_1588_CLOCK_OPTIONAL depends on BRIDGE || BRIDGE=n depends on NET_SWITCHDEV depends on HAS_IOMEM depends on OF select MSCC_OCELOT_SWITCH_LIB select GENERIC_PHY help This driver supports the Ocelot network switch device as present on the Ocelot SoCs (VSC7514). endif # NET_VENDOR_MICROSEMI PK ! �R�;� � mscc/Makefilenu �[��� # SPDX-License-Identifier: (GPL-2.0 OR MIT) obj-$(CONFIG_MSCC_OCELOT_SWITCH_LIB) += mscc_ocelot_switch_lib.o mscc_ocelot_switch_lib-y := \ ocelot.o \ ocelot_io.o \ ocelot_police.o \ ocelot_vcap.o \ ocelot_flower.o \ ocelot_ptp.o \ ocelot_devlink.o mscc_ocelot_switch_lib-$(CONFIG_BRIDGE_MRP) += ocelot_mrp.o obj-$(CONFIG_MSCC_OCELOT_SWITCH) += mscc_ocelot.o mscc_ocelot-y := \ ocelot_vsc7514.o \ ocelot_net.o PK ! ^��Y� � atheros/atl1e/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_ATL1E) += atl1e.o atl1e-objs += atl1e_main.o atl1e_hw.o atl1e_ethtool.o atl1e_param.o PK ! ��e e atheros/alx/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_ALX) += alx.o alx-objs := main.o ethtool.o hw.o PK ! l�} } atheros/atl1c/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_ATL1C) += atl1c.o atl1c-objs := atl1c_main.o atl1c_hw.o atl1c_ethtool.o PK ! �_E!3 3 atheros/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Atheros device configuration # config NET_VENDOR_ATHEROS bool "Atheros devices" default y depends on (PCI || ATH79) help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Atheros devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ATHEROS config AG71XX tristate "Atheros AR7XXX/AR9XXX built-in ethernet mac support" depends on ATH79 select PHYLINK imply NET_SELFTESTS help If you wish to compile a kernel for AR7XXX/91XXX and enable ethernet support, then you should always answer Y to this. config ATL2 tristate "Atheros L2 Fast Ethernet support" depends on PCI select CRC32 select MII help This driver supports the Atheros L2 fast ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl2. config ATL1 tristate "Atheros/Attansic L1 Gigabit Ethernet support" depends on PCI select CRC32 select MII help This driver supports the Atheros/Attansic L1 gigabit ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl1. config ATL1E tristate "Atheros L1E Gigabit Ethernet support" depends on PCI select CRC32 select MII help This driver supports the Atheros L1E gigabit ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl1e. config ATL1C tristate "Atheros L1C Gigabit Ethernet support" depends on PCI select CRC32 select MII help This driver supports the Atheros L1C gigabit ethernet adapter. To compile this driver as a module, choose M here. The module will be called atl1c. config ALX tristate "Qualcomm Atheros AR816x/AR817x support" depends on PCI select CRC32 select MDIO help This driver supports the Qualcomm Atheros L1F ethernet adapter, i.e. the following chipsets: 1969:1091 - AR8161 Gigabit Ethernet 1969:1090 - AR8162 Fast Ethernet 1969:10A1 - AR8171 Gigabit Ethernet 1969:10A0 - AR8172 Fast Ethernet To compile this driver as a module, choose M here. The module will be called alx. endif # NET_VENDOR_ATHEROS PK ! �7�� atheros/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Atheros network device drivers. # obj-$(CONFIG_AG71XX) += ag71xx.o obj-$(CONFIG_ATL1) += atlx/ obj-$(CONFIG_ATL2) += atlx/ obj-$(CONFIG_ATL1E) += atl1e/ obj-$(CONFIG_ATL1C) += atl1c/ obj-$(CONFIG_ALX) += alx/ PK ! ���c c atheros/atlx/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_ATL1) += atl1.o obj-$(CONFIG_ATL2) += atl2.o PK ! �+zD{ { amd/xgbe/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_AMD_XGBE) += amd-xgbe.o amd-xgbe-objs := xgbe-main.o xgbe-drv.o xgbe-dev.o \ xgbe-desc.o xgbe-ethtool.o xgbe-mdio.o \ xgbe-ptp.o \ xgbe-i2c.o xgbe-phy-v1.o xgbe-phy-v2.o \ xgbe-platform.o amd-xgbe-$(CONFIG_PCI) += xgbe-pci.o amd-xgbe-$(CONFIG_AMD_XGBE_DCB) += xgbe-dcb.o amd-xgbe-$(CONFIG_DEBUG_FS) += xgbe-debugfs.o PK ! �W�}! ! amd/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # AMD network device configuration # config NET_VENDOR_AMD bool "AMD devices" default y depends on DIO || MACH_DECSTATION || MVME147 || ATARI || SUN3 || \ SUN3X || SBUS || PCI || ZORRO || (ISA && ISA_DMA_API) || \ ISA || EISA || PCMCIA || ARM64 help If you have a network (Ethernet) chipset belonging to this class, say Y. Note that the answer to this question does not directly affect the kernel: saying N will just cause the configurator to skip all the questions regarding AMD chipsets. If you say Y, you will be asked for your specific chipset/driver in the following questions. if NET_VENDOR_AMD config A2065 tristate "A2065 support" depends on ZORRO select CRC32 help If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called a2065. config AMD8111_ETH tristate "AMD 8111 (new PCI LANCE) support" depends on PCI select CRC32 select MII help If you have an AMD 8111-based PCI LANCE ethernet card, answer Y here. To compile this driver as a module, choose M here. The module will be called amd8111e. config LANCE tristate "AMD LANCE and PCnet (AT1500 and NE2100) support" depends on ISA && ISA_DMA_API && !ARM && !PPC32 select NETDEV_LEGACY_INIT help If you have a network (Ethernet) card of this type, say Y here. Some LinkSys cards are of this type. To compile this driver as a module, choose M here: the module will be called lance. This is recommended. config PCNET32 tristate "AMD PCnet32 PCI support" depends on PCI select CRC32 select MII help If you have a PCnet32 or PCnetPCI based network (Ethernet) card, answer Y here. To compile this driver as a module, choose M here. The module will be called pcnet32. config ARIADNE tristate "Ariadne support" depends on ZORRO help If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called ariadne. config ATARILANCE tristate "Atari LANCE support" depends on ATARI help Say Y to include support for several Atari Ethernet adapters based on the AMD LANCE chipset: RieblCard (with or without battery), or PAMCard VME (also the version by Rhotron, with different addresses). config DECLANCE tristate "DEC LANCE ethernet controller support" depends on MACH_DECSTATION select CRC32 help This driver is for the series of Ethernet controllers produced by DEC (now Compaq) based on the AMD LANCE chipset, including the DEPCA series. (This chipset is better known via the NE2100 cards.) config HPLANCE tristate "HP on-board LANCE support" depends on DIO select CRC32 help If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here. config MIPS_AU1X00_ENET tristate "MIPS AU1000 Ethernet support" depends on MIPS_ALCHEMY select PHYLIB select CRC32 help If you have an Alchemy Semi AU1X00 based system say Y. Otherwise, say N. config MVME147_NET tristate "MVME147 (LANCE) Ethernet support" depends on MVME147 select CRC32 help Support for the on-board Ethernet interface on the Motorola MVME147 single-board computer. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config PCMCIA_NMCLAN tristate "New Media PCMCIA support" depends on PCMCIA help Say Y here if you intend to attach a New Media Ethernet or LiveWire PCMCIA (PC-card) Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called nmclan_cs. If unsure, say N. config NI65 tristate "NI6510 support" depends on ISA && ISA_DMA_API && !ARM && !PPC32 select NETDEV_LEGACY_INIT help If you have a network (Ethernet) card of this type, say Y here. To compile this driver as a module, choose M here. The module will be called ni65. config SUN3LANCE tristate "Sun3/Sun3x on-board LANCE support" depends on (SUN3 || SUN3X) help Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) featured an AMD LANCE 10Mbit Ethernet controller on board; say Y here to compile in the Linux driver for this and enable Ethernet. General Linux information on the Sun 3 and 3x series (now discontinued) is at <http://www.angelfire.com/ca2/tech68k/sun3.html>. If you're not building a kernel for a Sun 3, say N. config SUNLANCE tristate "Sun LANCE support" depends on SBUS select CRC32 help This driver supports the "le" interface present on all 32-bit Sparc systems, on some older Ultra systems and as an Sbus option. These cards are based on the AMD LANCE chipset, which is better known via the NE2100 cards. To compile this driver as a module, choose M here: the module will be called sunlance. config AMD_XGBE tristate "AMD 10GbE Ethernet driver" depends on (OF_ADDRESS || ACPI || PCI) && HAS_IOMEM depends on X86 || ARM64 || COMPILE_TEST depends on PTP_1588_CLOCK_OPTIONAL select BITREVERSE select CRC32 select PHYLIB select AMD_XGBE_HAVE_ECC if X86 help This driver supports the AMD 10GbE Ethernet device found on an AMD SoC. To compile this driver as a module, choose M here: the module will be called amd-xgbe. config AMD_XGBE_DCB bool "Data Center Bridging (DCB) support" default n depends on AMD_XGBE && DCB help Say Y here to enable Data Center Bridging (DCB) support in the driver. If unsure, say N. config AMD_XGBE_HAVE_ECC bool default n endif # NET_VENDOR_AMD PK ! ��lX� � amd/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the AMD network device drivers. # obj-$(CONFIG_A2065) += a2065.o obj-$(CONFIG_AMD8111_ETH) += amd8111e.o obj-$(CONFIG_ARIADNE) += ariadne.o obj-$(CONFIG_ATARILANCE) += atarilance.o obj-$(CONFIG_DECLANCE) += declance.o obj-$(CONFIG_HPLANCE) += hplance.o 7990.o obj-$(CONFIG_LANCE) += lance.o obj-$(CONFIG_MIPS_AU1X00_ENET) += au1000_eth.o obj-$(CONFIG_MVME147_NET) += mvme147.o 7990.o obj-$(CONFIG_PCMCIA_NMCLAN) += nmclan_cs.o obj-$(CONFIG_NI65) += ni65.o obj-$(CONFIG_PCNET32) += pcnet32.o obj-$(CONFIG_SUN3LANCE) += sun3lance.o obj-$(CONFIG_SUNLANCE) += sunlance.o obj-$(CONFIG_AMD_XGBE) += xgbe/ PK ! ��.� � netronome/nfp/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_NFP) += nfp.o nfp-objs := \ nfpcore/nfp6000_pcie.o \ nfpcore/nfp_cppcore.o \ nfpcore/nfp_cpplib.o \ nfpcore/nfp_hwinfo.o \ nfpcore/nfp_mip.o \ nfpcore/nfp_mutex.o \ nfpcore/nfp_nffw.o \ nfpcore/nfp_nsp.o \ nfpcore/nfp_nsp_cmds.o \ nfpcore/nfp_nsp_eth.o \ nfpcore/nfp_resource.o \ nfpcore/nfp_rtsym.o \ nfpcore/nfp_target.o \ ccm.o \ ccm_mbox.o \ devlink_param.o \ nfp_asm.o \ nfp_app.o \ nfp_app_nic.o \ nfp_devlink.o \ nfp_hwmon.o \ nfp_main.o \ nfp_net_common.o \ nfp_net_ctrl.o \ nfp_net_debugdump.o \ nfp_net_ethtool.o \ nfp_net_main.o \ nfp_net_repr.o \ nfp_net_sriov.o \ nfp_netvf_main.o \ nfp_port.o \ nfp_shared_buf.o \ nic/main.o ifeq ($(CONFIG_TLS_DEVICE),y) nfp-objs += \ crypto/tls.o endif ifeq ($(CONFIG_NFP_APP_FLOWER),y) nfp-objs += \ flower/action.o \ flower/cmsg.o \ flower/lag_conf.o \ flower/main.o \ flower/match.o \ flower/metadata.o \ flower/offload.o \ flower/tunnel_conf.o \ flower/qos_conf.o \ flower/conntrack.o endif ifeq ($(CONFIG_BPF_SYSCALL),y) nfp-objs += \ bpf/cmsg.o \ bpf/main.o \ bpf/offload.o \ bpf/verifier.o \ bpf/jit.o endif ifeq ($(CONFIG_NFP_APP_ABM_NIC),y) nfp-objs += \ abm/cls.o \ abm/ctrl.o \ abm/qdisc.o \ abm/main.o endif nfp-$(CONFIG_NFP_DEBUG) += nfp_net_debugfs.o PK ! S�nV netronome/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Netronome device configuration # config NET_VENDOR_NETRONOME bool "Netronome(R) devices" default y help If you have a Netronome(R) network (Ethernet) card or device, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Netronome(R) cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_NETRONOME config NFP tristate "Netronome(R) NFP4000/NFP6000 NIC driver" depends on PCI && PCI_MSI depends on VXLAN || VXLAN=n depends on TLS && TLS_DEVICE || TLS_DEVICE=n select NET_DEVLINK select CRC32 select DIMLIB help This driver supports the Netronome(R) NFP4000/NFP6000 based cards working as a advanced Ethernet NIC. It works with both SR-IOV physical and virtual functions. config NFP_APP_FLOWER bool "NFP4000/NFP6000 TC Flower offload support" depends on NFP depends on NET_SWITCHDEV depends on IPV6!=m || NFP=m default y help Enable driver support for TC Flower offload on NFP4000 and NFP6000. Say Y, if you are planning to make use of TC Flower offload either directly, with Open vSwitch, or any other way. Note that TC Flower offload requires specific FW to work. config NFP_APP_ABM_NIC bool "NFP4000/NFP6000 Advanced buffer management NIC support" depends on NFP depends on NET_SWITCHDEV default y help Enable driver support for Advanced buffer management NIC on NFP. ABM NIC allows advanced configuration of queuing and scheduling of packets, including ECN marking. Say Y, if you are planning to use one of the NFP4000 and NFP6000 platforms which support this functionality. Code will be built into the nfp.ko driver. config NFP_DEBUG bool "Debug support for Netronome(R) NFP4000/NFP6000 NIC drivers" depends on NFP help Enable extra sanity checks and debugfs support in Netronome(R) NFP4000/NFP6000 NIC drivers. Note: selecting this option may adversely impact performance. endif PK ! FN�{ { netronome/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Netronome network device drivers # obj-$(CONFIG_NFP) += nfp/ PK ! *�f[� � seeq/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # SEEQ device configuration # config NET_VENDOR_SEEQ bool "SEEQ devices" default y depends on HAS_IOMEM help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about SEEQ devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SEEQ config ARM_ETHER3 tristate "Acorn/ANT Ether3 support" depends on ARM && ARCH_ACORN help If you have an Acorn system with one of these network cards, you should say Y to this option if you wish to use it with Linux. config SGISEEQ tristate "SGI Seeq ethernet controller support" depends on SGI_HAS_SEEQ help Say Y here if you have an Seeq based Ethernet network card. This is used in many Silicon Graphics machines. endif # NET_VENDOR_SEEQ PK ! ��oS� � seeq/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the SEEQ network device drivers # obj-$(CONFIG_ARM_ETHER3) += ether3.o obj-$(CONFIG_SGISEEQ) += sgiseeq.o PK ! ,C�{ { microsoft/Kconfignu �[��� # # Microsoft Azure network device configuration # config NET_VENDOR_MICROSOFT bool "Microsoft Network Devices" default y help If you have a network (Ethernet) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip the question about Microsoft network devices. If you say Y, you will be asked for your specific device in the following question. if NET_VENDOR_MICROSOFT config MICROSOFT_MANA tristate "Microsoft Azure Network Adapter (MANA) support" depends on PCI_MSI && X86_64 depends on PCI_HYPERV select PAGE_POOL help This driver supports Microsoft Azure Network Adapter (MANA). So far, the driver is only supported on X86_64. To compile this driver as a module, choose M here. The module will be called mana. endif #NET_VENDOR_MICROSOFT PK ! n��Pe e microsoft/Makefilenu �[��� # # Makefile for the Microsoft Azure network device driver. # obj-$(CONFIG_MICROSOFT_MANA) += mana/ PK ! ����� � microsoft/mana/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause # # Makefile for the Microsoft Azure Network Adapter driver obj-$(CONFIG_MICROSOFT_MANA) += mana.o mana-objs := gdma_main.o shm_channel.o hw_channel.o mana_en.o mana_ethtool.o PK ! �p6 3com/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # 3Com Ethernet device configuration # config NET_VENDOR_3COM bool "3Com devices" default y depends on ISA || EISA || PCI || PCMCIA help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about 3Com cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_3COM config EL3 tristate "3c509/3c579 \"EtherLink III\" support" depends on (ISA || EISA) help If you have a network (Ethernet) card belonging to the 3Com EtherLinkIII series, say Y here. If your card is not working you may need to use the DOS setup disk to disable Plug & Play mode, and to select the default media type. To compile this driver as a module, choose M here. The module will be called 3c509. config 3C515 tristate "3c515 ISA \"Fast EtherLink\"" depends on ISA && ISA_DMA_API && !PPC32 select NETDEV_LEGACY_INIT help If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet network card, say Y here. To compile this driver as a module, choose M here. The module will be called 3c515. config PCMCIA_3C574 tristate "3Com 3c574 PCMCIA support" depends on PCMCIA help Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA (PC-card) Fast Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called 3c574_cs. If unsure, say N. config PCMCIA_3C589 tristate "3Com 3c589 PCMCIA support" depends on PCMCIA help Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA (PC-card) Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called 3c589_cs. If unsure, say N. config VORTEX tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support" depends on (PCI || EISA) && HAS_IOPORT_MAP select MII help This option enables driver support for a large number of 10Mbps and 10/100Mbps EISA, PCI and Cardbus 3Com network cards: "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI "Boomerang" (EtherLink XL 3c900 or 3c905) PCI "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus "Tornado" (3c905) PCI "Hurricane" (3c555/3cSOHO) PCI If you have such a card, say Y here. More specific information is in <file:Documentation/networking/device_drivers/ethernet/3com/vortex.rst> and in the comments at the beginning of <file:drivers/net/ethernet/3com/3c59x.c>. To compile this support as a module, choose M here. config TYPHOON tristate "3cr990 series \"Typhoon\" support" depends on PCI select CRC32 help This option enables driver support for the 3cr990 series of cards: 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97, 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server, 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR If you have a network (Ethernet) card of this type, say Y here. To compile this driver as a module, choose M here. The module will be called typhoon. endif # NET_VENDOR_3COM PK ! �6O) ) 3com/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the 3Com Ethernet device drivers # obj-$(CONFIG_EL3) += 3c509.o obj-$(CONFIG_3C515) += 3c515.o obj-$(CONFIG_PCMCIA_3C589) += 3c589_cs.o obj-$(CONFIG_PCMCIA_3C574) += 3c574_cs.o obj-$(CONFIG_VORTEX) += 3c59x.o obj-$(CONFIG_TYPHOON) += typhoon.o PK ! � �� � apple/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Apple device configuration # config NET_VENDOR_APPLE bool "Apple devices" default y depends on (PPC_PMAC && PPC32) || MAC help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Apple devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_APPLE config MACE tristate "MACE (Power Mac ethernet) support" depends on PPC_PMAC && PPC32 select CRC32 help Power Macintoshes and clones with Ethernet built-in on the motherboard will usually use a MACE (Medium Access Control for Ethernet) interface. Say Y to include support for the MACE chip. To compile this driver as a module, choose M here: the module will be called mace. config MACE_AAUI_PORT bool "Use AAUI port instead of TP by default" depends on MACE help Some Apple machines (notably the Apple Network Server) which use the MACE ethernet chip have an Apple AUI port (small 15-pin connector), instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say Y here if you have such a machine. If unsure, say N. The driver will default to AAUI on ANS anyway, and if you use it as a module, you can provide the port_aaui=0|1 to force the driver. config BMAC tristate "BMAC (G3 ethernet) support" depends on PPC_PMAC && PPC32 select CRC32 help Say Y for support of BMAC Ethernet interfaces. These are used on G3 computers. To compile this driver as a module, choose M here: the module will be called bmac. config MACMACE tristate "Macintosh (AV) onboard MACE ethernet" depends on MAC select CRC32 help Support for the onboard AMD 79C940 MACE Ethernet controller used in the 660AV and 840AV Macintosh. If you have one of these Macintoshes say Y here. endif # NET_VENDOR_APPLE PK ! t��(� � apple/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Apple network device drivers. # obj-$(CONFIG_MACE) += mace.o obj-$(CONFIG_BMAC) += bmac.o obj-$(CONFIG_MACMACE) += macmace.o PK ! �ڛ� rocker/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Rocker device configuration # config NET_VENDOR_ROCKER bool "Rocker devices" default y help If you have a network device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Rocker devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ROCKER config ROCKER tristate "Rocker switch driver (EXPERIMENTAL)" depends on PCI && NET_SWITCHDEV && BRIDGE select CRC32 help This driver supports Rocker switch device. To compile this driver as a module, choose M here: the module will be called rocker. endif # NET_VENDOR_ROCKER PK ! �y�j� � rocker/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Rocker network device drivers. # obj-$(CONFIG_ROCKER) += rocker.o rocker-y := rocker_main.o rocker_tlv.o rocker_ofdpa.o PK ! �,��; ; altera/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config ALTERA_TSE tristate "Altera Triple-Speed Ethernet MAC support" depends on HAS_DMA select PHYLIB help This driver supports the Altera Triple-Speed (TSE) Ethernet MAC. To compile this driver as a module, choose M here. The module will be called alteratse. PK ! d#a�� � altera/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Altera device drivers. # obj-$(CONFIG_ALTERA_TSE) += altera_tse.o altera_tse-objs := altera_tse_main.o altera_tse_ethtool.o \ altera_msgdma.o altera_sgdma.o altera_utils.o PK ! ��P�� � 8390/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # 8390 device configuration # config NET_VENDOR_8390 bool "National Semiconductor 8390 devices" default y depends on NET_VENDOR_NATSEMI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about National Semiconductor 8390 cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_8390 config PCMCIA_AXNET tristate "Asix AX88190 PCMCIA support" depends on PCMCIA help Say Y here if you intend to attach an Asix AX88190-based PCMCIA (PC-card) Fast Ethernet card to your computer. These cards are nearly NE2000 compatible but need a separate driver due to a few misfeatures. To compile this driver as a module, choose M here: the module will be called axnet_cs. If unsure, say N. config AX88796 tristate "ASIX AX88796 NE2000 clone support" if !ZORRO depends on (ARM || MIPS || SUPERH || ZORRO || COMPILE_TEST) select CRC32 select PHYLIB select MDIO_BITBANG help AX88796 driver, using platform bus to provide chip detection and resources config AX88796_93CX6 bool "ASIX AX88796 external 93CX6 eeprom support" depends on AX88796 select EEPROM_93CX6 help Select this if your platform comes with an external 93CX6 eeprom. config XSURF100 tristate "Amiga XSurf 100 AX88796/NE2000 clone support" depends on ZORRO select AX88796 select AX88796B_PHY help This driver is for the Individual Computers X-Surf 100 Ethernet card (based on the Asix AX88796 chip). If you have such a card, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called xsurf100. config HYDRA tristate "Hydra support" depends on ZORRO select CRC32 help If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called hydra. config ARM_ETHERH tristate "I-cubed EtherH/ANT EtherM support" depends on ARM && ARCH_ACORN select CRC32 help If you have an Acorn system with one of these network cards, you should say Y to this option if you wish to use it with Linux. config MAC8390 tristate "Macintosh NS 8390 based ethernet cards" depends on MAC select CRC32 help If you want to include a driver to support Nubus or LC-PDS Ethernet cards using an NS8390 chipset or its equivalent, say Y. config MCF8390 tristate "ColdFire NS8390 based Ethernet support" depends on COLDFIRE select CRC32 help This driver is for Ethernet devices using an NS8390-compatible chipset on many common ColdFire CPU based boards. Many of the older Freescale dev boards use this, and some other common boards like some SnapGear routers do as well. If you have one of these boards and want to use the network interface on them then choose Y. To compile this driver as a module, choose M here, the module will be called mcf8390. config NE2000 tristate "NE2000/NE1000 support" depends on (ISA || (Q40 && m) || MACH_TX49XX || ATARI_ETHERNEC) select NETDEV_LEGACY_INIT if ISA select CRC32 help If you have a network (Ethernet) card of this type, say Y here. Many Ethernet cards without a specific driver are compatible with the NE2000. If you have a PCI NE2000 card however, say N here and Y to "PCI NE2000 and clone support" below. To compile this driver as a module, choose M here. The module will be called ne. config NE2K_PCI tristate "PCI NE2000 and clones support (see help)" depends on PCI select CRC32 help This driver is for NE2000 compatible PCI cards. It will not work with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 support" below). If you have a PCI NE2000 network (Ethernet) card, say Y here. This driver also works for the following NE2000 clone cards: RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond Holtek HT80232 Holtek HT80229 To compile this driver as a module, choose M here. The module will be called ne2k-pci. config APNE tristate "PCMCIA NE2000 support" depends on AMIGA_PCMCIA select CRC32 help If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called apne. config PCMCIA_PCNET tristate "NE2000 compatible PCMCIA support" depends on PCMCIA select CRC32 help Say Y here if you intend to attach an NE2000 compatible PCMCIA (PC-card) Ethernet or Fast Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called pcnet_cs. If unsure, say N. config STNIC tristate "National DP83902AV support" depends on SUPERH select CRC32 help Support for cards based on the National Semiconductor DP83902AV ST-NIC Serial Network Interface Controller for Twisted Pair. This is a 10Mbit/sec Ethernet controller. Product overview and specs at <http://www.national.com/pf/DP/DP83902A.html>. If unsure, say N. config ULTRA tristate "SMC Ultra support" depends on ISA select NETDEV_LEGACY_INIT select CRC32 help If you have a network (Ethernet) card of this type, say Y here. Important: There have been many reports that, with some motherboards mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, such as some BusLogic models) causes corruption problems with many operating systems. The Linux smc-ultra driver has a work-around for this but keep it in mind if you have such a SCSI card and have problems. To compile this driver as a module, choose M here. The module will be called smc-ultra. config WD80x3 tristate "WD80*3 support" depends on ISA select NETDEV_LEGACY_INIT select CRC32 help If you have a network (Ethernet) card of this type, say Y here. To compile this driver as a module, choose M here. The module will be called wd. config ZORRO8390 tristate "Zorro NS8390-based Ethernet support" depends on ZORRO select CRC32 help This driver is for Zorro Ethernet cards using an NS8390-compatible chipset, like the Village Tronic Ariadne II and the Individual Computers X-Surf Ethernet cards. If you have such a card, say Y. Otherwise, say N. To compile this driver as a module, choose M here: the module will be called zorro8390. endif # NET_VENDOR_8390 PK ! #�� � 8390/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the 8390 network device drivers. # obj-$(CONFIG_MAC8390) += mac8390.o obj-$(CONFIG_APNE) += apne.o 8390.o obj-$(CONFIG_ARM_ETHERH) += etherh.o obj-$(CONFIG_AX88796) += ax88796.o obj-$(CONFIG_HYDRA) += hydra.o obj-$(CONFIG_MCF8390) += mcf8390.o obj-$(CONFIG_NE2000) += ne.o 8390p.o obj-$(CONFIG_NE2K_PCI) += ne2k-pci.o 8390.o obj-$(CONFIG_PCMCIA_AXNET) += axnet_cs.o 8390.o obj-$(CONFIG_PCMCIA_PCNET) += pcnet_cs.o 8390.o obj-$(CONFIG_STNIC) += stnic.o 8390.o obj-$(CONFIG_ULTRA) += smc-ultra.o 8390.o obj-$(CONFIG_WD80x3) += wd.o 8390.o obj-$(CONFIG_XSURF100) += xsurf100.o obj-$(CONFIG_ZORRO8390) += zorro8390.o PK ! ܳ��d d rdc/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # RDC network device configuration # config NET_VENDOR_RDC bool "RDC devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about RDC cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_RDC config R6040 tristate "RDC R6040 Fast Ethernet Adapter support" depends on PCI select CRC32 select MII select PHYLIB help This is a driver for the R6040 Fast Ethernet MACs found in the the RDC R-321x System-on-chips. To compile this driver as a module, choose M here: the module will be called r6040. This is recommended. endif # NET_VENDOR_RDC PK ! _C�{ { rdc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the RDC network device drivers. # obj-$(CONFIG_R6040) += r6040.o PK ! �0��� � actions/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_VENDOR_ACTIONS bool "Actions Semi devices" depends on ARCH_ACTIONS || COMPILE_TEST default ARCH_ACTIONS help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Actions Semi devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ACTIONS config OWL_EMAC tristate "Actions Semi Owl Ethernet MAC support" select PHYLIB help This driver supports the Actions Semi Ethernet Media Access Controller (EMAC) found on the S500 and S900 SoCs. The controller is compliant with the IEEE 802.3 CSMA/CD standard and supports both half-duplex and full-duplex operation modes at 10/100 Mb/s. endif # NET_VENDOR_ACTIONS PK ! �t$�� � actions/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Actions Semi Owl SoCs built-in ethernet macs # obj-$(CONFIG_OWL_EMAC) += owl-emac.o PK ! �w�f f via/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # VIA device configuration # config NET_VENDOR_VIA bool "VIA devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about VIA devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_VIA config VIA_RHINE tristate "VIA Rhine support" depends on PCI || (OF_IRQ && GENERIC_PCI_IOMAP) depends on PCI || ARCH_VT8500 || COMPILE_TEST depends on HAS_DMA select CRC32 select MII help If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type Ethernet functions can also be found integrated on South Bridges (e.g. VT8235). To compile this driver as a module, choose M here. The module will be called via-rhine. config VIA_RHINE_MMIO bool "Use MMIO instead of PIO" depends on VIA_RHINE help This instructs the driver to use PCI shared memory (MMIO) instead of programmed I/O ports (PIO). Enabling this gives an improvement in processing time in parts of the driver. If unsure, say Y. config VIA_VELOCITY tristate "VIA Velocity support" depends on (PCI || (OF_ADDRESS && OF_IRQ)) depends on HAS_DMA select CRC32 select CRC_CCITT select MII help If you have a VIA "Velocity" based network card say Y here. To compile this driver as a module, choose M here. The module will be called via-velocity. endif # NET_VENDOR_VIA PK ! Ũ � via/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the VIA device drivers. # obj-$(CONFIG_VIA_RHINE) += via-rhine.o obj-$(CONFIG_VIA_VELOCITY) += via-velocity.o PK ! ;�p p dec/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Digital Equipment Inc network device configuration # config NET_VENDOR_DEC bool "Digital Equipment devices" default y depends on PCI || EISA || CARDBUS help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about DEC cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_DEC source "drivers/net/ethernet/dec/tulip/Kconfig" endif # NET_VENDOR_DEC PK ! ˙�ڑ � dec/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Digital Equipment Inc. network device drivers. # obj-$(CONFIG_NET_TULIP) += tulip/ PK ! �5N_ _ dec/tulip/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Tulip family network device configuration # config NET_TULIP bool "DEC - Tulip devices" depends on (PCI || EISA || CARDBUS) help This selects the "Tulip" family of EISA/PCI network cards. if NET_TULIP config DE2104X tristate "Early DECchip Tulip (dc2104x) PCI support" depends on PCI select CRC32 help This driver is developed for the SMC EtherPower series Ethernet cards and also works with cards based on the DECchip 21040 (Tulip series) chips. Some LinkSys PCI cards are of this type. (If your card is NOT SMC EtherPower 10/100 PCI (smc9332dst), you can also try the driver for "Generic DECchip" cards, below. However, most people with a network card of this type will say Y here.) To compile this driver as a module, choose M here. The module will be called de2104x. config DE2104X_DSL int "Descriptor Skip Length in 32 bit longwords" depends on DE2104X range 0 31 default 0 help Setting this value allows to align ring buffer descriptors into their own cache lines. Value of 4 corresponds to the typical 32 byte line (the descriptor is 16 bytes). This is necessary on systems that lack cache coherence, an example is PowerMac 5500. Otherwise 0 is safe. Default is 0, and range is 0 to 31. config TULIP tristate "DECchip Tulip (dc2114x) PCI support" depends on PCI select CRC32 help This driver is developed for the SMC EtherPower series Ethernet cards and also works with cards based on the DECchip 21140 (Tulip series) chips. Some LinkSys PCI cards are of this type. (If your card is NOT SMC EtherPower 10/100 PCI (smc9332dst), you can also try the driver for "Generic DECchip" cards, above. However, most people with a network card of this type will say Y here.) To compile this driver as a module, choose M here. The module will be called tulip. config TULIP_MWI bool "New bus configuration" depends on TULIP help This configures your Tulip card specifically for the card and system cache line size type you are using. This is experimental code, not yet tested on many boards. If unsure, say N. config TULIP_MMIO bool "Use PCI shared mem for NIC registers" depends on TULIP help Use PCI shared memory for the NIC registers, rather than going through the Tulip's PIO (programmed I/O ports). Faster, but could produce obscure bugs if your mainboard has memory controller timing issues. If in doubt, say N. config TULIP_NAPI bool "Use RX polling (NAPI)" depends on TULIP help NAPI is a new driver API designed to reduce CPU and interrupt load when the driver is receiving lots of packets from the card. It is still somewhat experimental and thus not yet enabled by default. If your estimated Rx load is 10kpps or more, or if the card will be deployed on potentially unfriendly networks (e.g. in a firewall), then say Y here. If in doubt, say N. config TULIP_NAPI_HW_MITIGATION bool "Use Interrupt Mitigation" depends on TULIP_NAPI help Use HW to reduce RX interrupts. Not strictly necessary since NAPI reduces RX interrupts by itself. Interrupt mitigation reduces RX interrupts even at low levels of traffic at the cost of a small latency. If in doubt, say Y. config TULIP_DM910X def_bool y depends on TULIP && SPARC config DE4X5 tristate "Generic DECchip & DIGITAL EtherWORKS PCI/EISA" depends on (PCI || EISA) depends on VIRT_TO_BUS || ALPHA || PPC || SPARC select CRC32 help This is support for the DIGITAL series of PCI/EISA Ethernet cards. These include the DE425, DE434, DE435, DE450 and DE500 models. If you have a network card of this type, say Y. More specific information is contained in <file:Documentation/networking/device_drivers/ethernet/dec/de4x5.rst>. To compile this driver as a module, choose M here. The module will be called de4x5. config WINBOND_840 tristate "Winbond W89c840 Ethernet support" depends on PCI select CRC32 select MII help This driver is for the Winbond W89c840 chip. It also works with the TX9882 chip on the Compex RL100-ATX board. More specific information and updates are available from <http://www.scyld.com/network/drivers.html>. config DM9102 tristate "Davicom DM910x/DM980x support" depends on PCI select CRC32 help This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from Davicom (<http://www.davicom.com.tw/>). If you have such a network (Ethernet) card, say Y. Some information is contained in the file <file:Documentation/networking/device_drivers/ethernet/dec/dmfe.rst>. To compile this driver as a module, choose M here. The module will be called dmfe. config ULI526X tristate "ULi M526x controller support" depends on PCI select CRC32 help This driver is for ULi M5261/M5263 10/100M Ethernet Controller (<http://www.nvidia.com/page/uli_drivers.html>). To compile this driver as a module, choose M here. The module will be called uli526x. config PCMCIA_XIRCOM tristate "Xircom CardBus support" depends on CARDBUS help This driver is for the Digital "Tulip" Ethernet CardBus adapters. It should work with most DEC 21*4*-based chips/ethercards, as well as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and ASIX. To compile this driver as a module, choose M here. The module will be called xircom_cb. If unsure, say N. endif # NET_TULIP PK ! ��� dec/tulip/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux "Tulip" family network device drivers. # ccflags-$(CONFIG_NET_TULIP) := -DDEBUG obj-$(CONFIG_PCMCIA_XIRCOM) += xircom_cb.o obj-$(CONFIG_DM9102) += dmfe.o obj-$(CONFIG_WINBOND_840) += winbond-840.o obj-$(CONFIG_DE2104X) += de2104x.o obj-$(CONFIG_TULIP) += tulip.o obj-$(CONFIG_DE4X5) += de4x5.o obj-$(CONFIG_ULI526X) += uli526x.o # Declare multi-part drivers. tulip-objs := eeprom.o interrupt.o media.o \ timer.o tulip_core.o \ 21142.o pnic.o pnic2.o PK ! ���N: : arc/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # ARC EMAC network device configuration # config NET_VENDOR_ARC bool "ARC devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about ARC cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ARC config ARC_EMAC_CORE tristate depends on ARC || ARCH_ROCKCHIP || COMPILE_TEST select MII select PHYLIB select CRC32 config ARC_EMAC tristate "ARC EMAC support" select ARC_EMAC_CORE depends on OF_IRQ depends on ARC || COMPILE_TEST help On some legacy ARC (Synopsys) FPGA boards such as ARCAngel4/ML50x non-standard on-chip ethernet device ARC EMAC 10/100 is used. Say Y here if you have such a board. If unsure, say N. config EMAC_ROCKCHIP tristate "Rockchip EMAC support" select ARC_EMAC_CORE depends on OF_IRQ && REGULATOR depends on ARCH_ROCKCHIP || COMPILE_TEST help Support for Rockchip RK3036/RK3066/RK3188 EMAC ethernet controllers. This selects Rockchip SoC glue layer support for the emac device driver. This driver is used for RK3036/RK3066/RK3188 EMAC ethernet controller. endif # NET_VENDOR_ARC PK ! �:o arc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the ARC network device drivers. # arc_emac-objs := emac_main.o emac_mdio.o obj-$(CONFIG_ARC_EMAC_CORE) += arc_emac.o obj-$(CONFIG_ARC_EMAC) += emac_arc.o obj-$(CONFIG_EMAC_ROCKCHIP) += emac_rockchip.o PK ! "iZ� � ibm/ehea/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the eHEA ethernet device driver for IBM eServer System p # ehea-y = ehea_main.o ehea_phyp.o ehea_qmr.o ehea_ethtool.o obj-$(CONFIG_EHEA) += ehea.o PK ! ��)�� � ibm/emac/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config IBM_EMAC tristate "IBM EMAC Ethernet support" depends on PPC_DCR select CRC32 select PHYLIB help This driver supports the IBM EMAC family of Ethernet controllers typically found on 4xx embedded PowerPC chips, but also on the Axon southbridge for Cell. config IBM_EMAC_RXB int "Number of receive buffers" depends on IBM_EMAC default "128" config IBM_EMAC_TXB int "Number of transmit buffers" depends on IBM_EMAC default "64" config IBM_EMAC_POLL_WEIGHT int "MAL NAPI polling weight" depends on IBM_EMAC default "32" config IBM_EMAC_RX_COPY_THRESHOLD int "RX skb copy threshold (bytes)" depends on IBM_EMAC default "256" config IBM_EMAC_DEBUG bool "Debugging" depends on IBM_EMAC default n # The options below has to be select'ed by the respective # processor types or platforms config IBM_EMAC_ZMII bool default n config IBM_EMAC_RGMII bool default n config IBM_EMAC_TAH bool default n config IBM_EMAC_EMAC4 bool default n config IBM_EMAC_NO_FLOW_CTRL bool default n config IBM_EMAC_MAL_CLR_ICINTSTAT bool default n config IBM_EMAC_MAL_COMMON_ERR bool default n PK ! ��:�' ' ibm/emac/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the PowerPC 4xx on-chip ethernet driver # obj-$(CONFIG_IBM_EMAC) += ibm_emac.o ibm_emac-y := mal.o core.o phy.o ibm_emac-$(CONFIG_IBM_EMAC_ZMII) += zmii.o ibm_emac-$(CONFIG_IBM_EMAC_RGMII) += rgmii.o ibm_emac-$(CONFIG_IBM_EMAC_TAH) += tah.o PK ! ^�m m ibm/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # IBM device configuration. # config NET_VENDOR_IBM bool "IBM devices" default y depends on PPC_PSERIES || PPC_DCR || (IBMEBUS && SPARSEMEM) help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about IBM devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_IBM config IBMVETH tristate "IBM LAN Virtual Ethernet support" depends on PPC_PSERIES help This driver supports virtual ethernet adapters on newer IBM iSeries and pSeries systems. To compile this driver as a module, choose M here. The module will be called ibmveth. source "drivers/net/ethernet/ibm/emac/Kconfig" config EHEA tristate "eHEA Ethernet support" depends on IBMEBUS && SPARSEMEM help This driver supports the IBM pSeries eHEA ethernet adapter. To compile the driver as a module, choose M here. The module will be called ehea. config IBMVNIC tristate "IBM Virtual NIC support" depends on PPC_PSERIES help This driver supports Virtual NIC adapters on IBM i and IBM System p systems. To compile this driver as a module, choose M here. The module will be called ibmvnic. endif # NET_VENDOR_IBM PK ! �.�� � ibm/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for th IBM network device drivers. # obj-$(CONFIG_IBMVETH) += ibmveth.o obj-$(CONFIG_IBMVNIC) += ibmvnic.o obj-$(CONFIG_IBM_EMAC) += emac/ obj-$(CONFIG_EHEA) += ehea/ PK ! Pl� ezchip/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # EZchip network device configuration # config NET_VENDOR_EZCHIP bool "EZchip devices" default y help If you have a network (Ethernet) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about EZchip devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_EZCHIP config EZCHIP_NPS_MANAGEMENT_ENET tristate "EZchip NPS management enet support" depends on OF_IRQ depends on HAS_IOMEM help Simple LAN device for debug or management purposes. Device supports interrupts for RX and TX(completion). Device does not have DMA ability. endif PK ! �Y#_ _ ezchip/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_EZCHIP_NPS_MANAGEMENT_ENET) += nps_enet.o PK ! ^��{ { broadcom/genet/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_BCMGENET) += genet.o genet-objs := bcmgenet.o bcmmii.o bcmgenet_wol.o PK ! ���F F broadcom/bnxt/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_BNXT) += bnxt_en.o bnxt_en-y := bnxt.o bnxt_hwrm.o bnxt_sriov.o bnxt_ethtool.o bnxt_dcb.o bnxt_ulp.o bnxt_xdp.o bnxt_ptp.o bnxt_vfr.o bnxt_devlink.o bnxt_dim.o bnxt_coredump.o bnxt_en-$(CONFIG_BNXT_FLOWER_OFFLOAD) += bnxt_tc.o bnxt_en-$(CONFIG_DEBUG_FS) += bnxt_debugfs.o PK ! �д) broadcom/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Broadcom device configuration # config NET_VENDOR_BROADCOM bool "Broadcom devices" default y depends on (SSB_POSSIBLE && HAS_DMA) || PCI || BCM63XX || \ SIBYTE_SB1xxx_SOC help If you have a network (Ethernet) chipset belonging to this class, say Y. Note that the answer to this question does not directly affect the kernel: saying N will just cause the configurator to skip all the questions regarding Broadcom chipsets. If you say Y, you will be asked for your specific chipset/driver in the following questions. if NET_VENDOR_BROADCOM config B44 tristate "Broadcom 440x/47xx ethernet support" depends on SSB_POSSIBLE && HAS_DMA select SSB select MII select PHYLIB help If you have a network (Ethernet) controller of this type, say Y or M here. To compile this driver as a module, choose M here. The module will be called b44. # Auto-select SSB PCI-HOST support, if possible config B44_PCI_AUTOSELECT bool depends on B44 && SSB_PCIHOST_POSSIBLE select SSB_PCIHOST default y # Auto-select SSB PCICORE driver, if possible config B44_PCICORE_AUTOSELECT bool depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE select SSB_DRIVER_PCICORE default y config B44_PCI bool depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT default y config BCM4908_ENET tristate "Broadcom BCM4908 internal mac support" depends on ARCH_BCM4908 || COMPILE_TEST default y if ARCH_BCM4908 help This driver supports Ethernet controller integrated into Broadcom BCM4908 family SoCs. config BCM63XX_ENET tristate "Broadcom 63xx internal mac support" depends on BCM63XX select MII select PHYLIB help This driver supports the ethernet MACs in the Broadcom 63xx MIPS chipset family (BCM63XX). config BCMGENET tristate "Broadcom GENET internal MAC support" depends on HAS_IOMEM depends on PTP_1588_CLOCK_OPTIONAL || !ARCH_BCM2835 select MII select PHYLIB select FIXED_PHY select BCM7XXX_PHY select MDIO_BCM_UNIMAC select DIMLIB select BROADCOM_PHY if ARCH_BCM2835 help This driver supports the built-in Ethernet MACs found in the Broadcom BCM7xxx Set Top Box family chipset. config BNX2 tristate "QLogic bnx2 support" depends on PCI select CRC32 select FW_LOADER help This driver supports QLogic bnx2 gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called bnx2. This is recommended. config CNIC tristate "QLogic CNIC support" depends on PCI && (IPV6 || IPV6=n) depends on MMU select BNX2 select UIO help This driver supports offload features of QLogic bnx2 gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called cnic. This is recommended. config SB1250_MAC tristate "SB1250 Gigabit Ethernet support" depends on SIBYTE_SB1xxx_SOC select PHYLIB help This driver supports Gigabit Ethernet interfaces based on the Broadcom SiByte family of System-On-a-Chip parts. They include the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 and BCM1480 chips. To compile this driver as a module, choose M here: the module will be called sb1250-mac. config TIGON3 tristate "Broadcom Tigon3 support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select PHYLIB help This driver supports Broadcom Tigon3 based gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called tg3. This is recommended. config TIGON3_HWMON bool "Broadcom Tigon3 HWMON support" default y depends on TIGON3 && HWMON && !(TIGON3=y && HWMON=m) help Say Y if you want to expose the thermal sensor on Tigon3 devices. config BNX2X tristate "Broadcom NetXtremeII 10Gb support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select FW_LOADER select ZLIB_INFLATE select LIBCRC32C select MDIO help This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called bnx2x. This is recommended. config BNX2X_SRIOV bool "Broadcom 578xx and 57712 SR-IOV support" depends on BNX2X && PCI_IOV default y help This configuration parameter enables Single Root Input Output Virtualization support in the 578xx and 57712 products. This allows for virtual function acceleration in virtual environments. config BGMAC tristate help This enables the integrated ethernet controller support for many Broadcom (mostly iProc) SoCs. An appropriate bus interface driver needs to be enabled to select this. config BGMAC_BCMA tristate "Broadcom iProc GBit BCMA support" depends on BCMA && BCMA_HOST_SOC depends on BCM47XX || ARCH_BCM_5301X || COMPILE_TEST select BGMAC select PHYLIB select FIXED_PHY help This driver supports GBit MAC and BCM4706 GBit MAC cores on BCMA bus. They can be found on BCM47xx SoCs and provide gigabit ethernet. In case of using this driver on BCM4706 it's also requires to enable BCMA_DRIVER_GMAC_CMN to make it work. config BGMAC_PLATFORM tristate "Broadcom iProc GBit platform support" depends on ARCH_BCM_IPROC || COMPILE_TEST select BGMAC select PHYLIB select FIXED_PHY default ARCH_BCM_IPROC help Say Y here if you want to use the Broadcom iProc Gigabit Ethernet controller through the generic platform interface config SYSTEMPORT tristate "Broadcom SYSTEMPORT internal MAC support" depends on HAS_IOMEM depends on NET_DSA || !NET_DSA select MII select PHYLIB select FIXED_PHY select DIMLIB help This driver supports the built-in Ethernet MACs found in the Broadcom BCM7xxx Set Top Box family chipset using an internal Ethernet switch. config BNXT tristate "Broadcom NetXtreme-C/E support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select FW_LOADER select LIBCRC32C select NET_DEVLINK select PAGE_POOL select DIMLIB help This driver supports Broadcom NetXtreme-C/E 10/25/40/50 gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called bnxt_en. This is recommended. config BNXT_SRIOV bool "Broadcom NetXtreme-C/E SR-IOV support" depends on BNXT && PCI_IOV default y help This configuration parameter enables Single Root Input Output Virtualization support in the NetXtreme-C/E products. This allows for virtual function acceleration in virtual environments. config BNXT_FLOWER_OFFLOAD bool "TC Flower offload support for NetXtreme-C/E" depends on BNXT default y help This configuration parameter enables TC Flower packet classifier offload for eswitch. This option enables SR-IOV switchdev eswitch offload. config BNXT_DCB bool "Data Center Bridging (DCB) Support" default n depends on BNXT && DCB help Say Y here if you want to use Data Center Bridging (DCB) in the driver. If unsure, say N. config BNXT_HWMON bool "Broadcom NetXtreme-C/E HWMON support" default y depends on BNXT && HWMON && !(BNXT=y && HWMON=m) help Say Y if you want to expose the thermal sensor data on NetXtreme-C/E devices, via the hwmon sysfs interface. endif # NET_VENDOR_BROADCOM PK ! �7� � broadcom/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Broadcom network device drivers. # obj-$(CONFIG_B44) += b44.o obj-$(CONFIG_BCM4908_ENET) += bcm4908_enet.o obj-$(CONFIG_BCM63XX_ENET) += bcm63xx_enet.o obj-$(CONFIG_BCMGENET) += genet/ obj-$(CONFIG_BNX2) += bnx2.o obj-$(CONFIG_CNIC) += cnic.o obj-$(CONFIG_BNX2X) += bnx2x/ obj-$(CONFIG_SB1250_MAC) += sb1250-mac.o obj-$(CONFIG_TIGON3) += tg3.o obj-$(CONFIG_BGMAC) += bgmac.o obj-$(CONFIG_BGMAC_BCMA) += bgmac-bcma.o bgmac-bcma-mdio.o obj-$(CONFIG_BGMAC_PLATFORM) += bgmac-platform.o obj-$(CONFIG_SYSTEMPORT) += bcmsysport.o obj-$(CONFIG_BNXT) += bnxt/ # FIXME: temporarily silence -Warray-bounds on non W=1+ builds ifndef KBUILD_EXTRA_WARN CFLAGS_tg3.o += -Wno-array-bounds endif PK ! J:��2 2 broadcom/bnx2x/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Broadcom 10-Gigabit ethernet driver # obj-$(CONFIG_BNX2X) += bnx2x.o bnx2x-y := bnx2x_main.o bnx2x_link.o bnx2x_cmn.o bnx2x_ethtool.o bnx2x_stats.o bnx2x_dcb.o bnx2x_sp.o bnx2x_self_test.o bnx2x-$(CONFIG_BNX2X_SRIOV) += bnx2x_vfpf.o bnx2x_sriov.o PK ! �5K� � ti/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # TI device configuration # config NET_VENDOR_TI bool "Texas Instruments (TI) devices" default y depends on PCI || EISA || AR7 || ARCH_DAVINCI || ARCH_OMAP2PLUS || ARCH_KEYSTONE || ARCH_K3 help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about TI devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_TI config TI_DAVINCI_EMAC tristate "TI DaVinci EMAC Support" depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 ) || COMPILE_TEST select TI_DAVINCI_MDIO select PHYLIB select GENERIC_ALLOCATOR help This driver supports TI's DaVinci Ethernet . To compile this driver as a module, choose M here: the module will be called davinci_emac_driver. This is recommended. config TI_DAVINCI_MDIO tristate "TI DaVinci MDIO Support" depends on ARCH_DAVINCI || ARCH_OMAP2PLUS || ARCH_KEYSTONE || ARCH_K3 || COMPILE_TEST select PHYLIB select MDIO_BITBANG help This driver supports TI's DaVinci MDIO module. To compile this driver as a module, choose M here: the module will be called davinci_mdio. This is recommended. config TI_CPSW_PHY_SEL bool "TI CPSW Phy mode Selection (DEPRECATED)" default n help This driver supports configuring of the phy mode connected to the CPSW. DEPRECATED: use PHY_TI_GMII_SEL. config TI_CPSW tristate "TI CPSW Switch Support" depends on ARCH_DAVINCI || ARCH_OMAP2PLUS || COMPILE_TEST depends on TI_CPTS || !TI_CPTS select TI_DAVINCI_MDIO select MFD_SYSCON select PAGE_POOL select REGMAP imply PHY_TI_GMII_SEL help This driver supports TI's CPSW Ethernet Switch. To compile this driver as a module, choose M here: the module will be called cpsw. config TI_CPSW_SWITCHDEV tristate "TI CPSW Switch Support with switchdev" depends on ARCH_DAVINCI || ARCH_OMAP2PLUS || COMPILE_TEST depends on NET_SWITCHDEV depends on TI_CPTS || !TI_CPTS select PAGE_POOL select TI_DAVINCI_MDIO select MFD_SYSCON select REGMAP select NET_DEVLINK imply PHY_TI_GMII_SEL help This driver supports TI's CPSW Ethernet Switch. To compile this driver as a module, choose M here: the module will be called cpsw_new. config TI_CPTS tristate "TI Common Platform Time Sync (CPTS) Support" depends on ARCH_OMAP2PLUS || ARCH_KEYSTONE || COMPILE_TEST depends on COMMON_CLK depends on PTP_1588_CLOCK help This driver supports the Common Platform Time Sync unit of the CPSW Ethernet Switch and Keystone 2 1g/10g Switch Subsystem. The unit can time stamp PTP UDP/IPv4 and Layer 2 packets, and the driver offers a PTP Hardware Clock. config TI_K3_AM65_CPSW_NUSS tristate "TI K3 AM654x/J721E CPSW Ethernet driver" depends on ARCH_K3 && OF && TI_K3_UDMA_GLUE_LAYER select NET_DEVLINK select TI_DAVINCI_MDIO imply PHY_TI_GMII_SEL depends on TI_K3_AM65_CPTS || !TI_K3_AM65_CPTS help This driver supports TI K3 AM654/J721E CPSW2G Ethernet SubSystem. The two-port Gigabit Ethernet MAC (MCU_CPSW0) subsystem provides Ethernet packet communication for the device: One Ethernet port (port 1) with selectable RGMII and RMII interfaces and an internal Communications Port Programming Interface (CPPI) port (port 0). To compile this driver as a module, choose M here: the module will be called ti-am65-cpsw-nuss. config TI_K3_AM65_CPSW_SWITCHDEV bool "TI K3 AM654x/J721E CPSW Switch mode support" depends on TI_K3_AM65_CPSW_NUSS depends on NET_SWITCHDEV help This enables switchdev support for TI K3 CPSWxG Ethernet Switch. Enable this driver to support hardware switch support for AM65 CPSW NUSS driver. config TI_K3_AM65_CPTS tristate "TI K3 AM65x CPTS" depends on ARCH_K3 && OF depends on PTP_1588_CLOCK help Say y here to support the TI K3 AM65x CPTS with 1588 features such as PTP hardware clock for each CPTS device and network packets timestamping where applicable. Depending on integration CPTS blocks enable compliance with the IEEE 1588-2008 standard for a precision clock synchronization protocol, Ethernet Enhanced Scheduled Traffic Operations (CPTS_ESTFn) and PCIe Subsystem Precision Time Measurement (PTM). config TI_AM65_CPSW_TAS bool "Enable TAS offload in AM65 CPSW" depends on TI_K3_AM65_CPSW_NUSS && NET_SCH_TAPRIO && TI_K3_AM65_CPTS help Say y here to support Time Aware Shaper(TAS) offload in AM65 CPSW. AM65 CPSW hardware supports Enhanced Scheduled Traffic (EST) defined in IEEE 802.1Q 2018. The EST scheduler runs on CPTS and the TAS/EST schedule is updated in the Fetch RAM memory of the CPSW. config TI_KEYSTONE_NETCP tristate "TI Keystone NETCP Core Support" select TI_DAVINCI_MDIO depends on OF depends on KEYSTONE_NAVIGATOR_DMA && KEYSTONE_NAVIGATOR_QMSS depends on TI_CPTS || !TI_CPTS help This driver supports TI's Keystone NETCP Core. To compile this driver as a module, choose M here: the module will be called keystone_netcp. config TI_KEYSTONE_NETCP_ETHSS depends on TI_KEYSTONE_NETCP tristate "TI Keystone NETCP Ethernet subsystem Support" help To compile this driver as a module, choose M here: the module will be called keystone_netcp_ethss. config TLAN tristate "TI ThunderLAN support" depends on (PCI || EISA) help If you have a PCI Ethernet network card based on the ThunderLAN chip which is supported by this driver, say Y here. Devices currently supported by this driver are Compaq Netelligent, Compaq NetFlex and Olicom cards. Please read the file <file:Documentation/networking/device_drivers/ethernet/ti/tlan.rst> for more details. To compile this driver as a module, choose M here. The module will be called tlan. Please email feedback to <torben.mathiasen@compaq.com>. config CPMAC tristate "TI AR7 CPMAC Ethernet support" depends on AR7 select PHYLIB help TI AR7 CPMAC Ethernet support endif # NET_VENDOR_TI PK ! ��5 5 ti/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the TI network device drivers. # obj-$(CONFIG_TI_CPSW) += cpsw-common.o obj-$(CONFIG_TI_DAVINCI_EMAC) += cpsw-common.o obj-$(CONFIG_TI_CPSW_SWITCHDEV) += cpsw-common.o obj-$(CONFIG_TLAN) += tlan.o obj-$(CONFIG_CPMAC) += cpmac.o obj-$(CONFIG_TI_DAVINCI_EMAC) += ti_davinci_emac.o ti_davinci_emac-y := davinci_emac.o davinci_cpdma.o obj-$(CONFIG_TI_DAVINCI_MDIO) += davinci_mdio.o obj-$(CONFIG_TI_CPSW_PHY_SEL) += cpsw-phy-sel.o obj-$(CONFIG_TI_CPTS) += cpts.o obj-$(CONFIG_TI_CPSW) += ti_cpsw.o ti_cpsw-y := cpsw.o davinci_cpdma.o cpsw_ale.o cpsw_priv.o cpsw_sl.o cpsw_ethtool.o obj-$(CONFIG_TI_CPSW_SWITCHDEV) += ti_cpsw_new.o ti_cpsw_new-y := cpsw_switchdev.o cpsw_new.o davinci_cpdma.o cpsw_ale.o cpsw_sl.o cpsw_priv.o cpsw_ethtool.o obj-$(CONFIG_TI_KEYSTONE_NETCP) += keystone_netcp.o keystone_netcp-y := netcp_core.o cpsw_ale.o obj-$(CONFIG_TI_KEYSTONE_NETCP_ETHSS) += keystone_netcp_ethss.o keystone_netcp_ethss-y := netcp_ethss.o netcp_sgmii.o netcp_xgbepcsr.o cpsw_ale.o obj-$(CONFIG_TI_K3_AM65_CPSW_NUSS) += ti-am65-cpsw-nuss.o ti-am65-cpsw-nuss-y := am65-cpsw-nuss.o cpsw_sl.o am65-cpsw-ethtool.o cpsw_ale.o k3-cppi-desc-pool.o am65-cpsw-qos.o ti-am65-cpsw-nuss-$(CONFIG_TI_K3_AM65_CPSW_SWITCHDEV) += am65-cpsw-switchdev.o obj-$(CONFIG_TI_K3_AM65_CPTS) += am65-cpts.o PK ! �=�2h h wiznet/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # WIZnet devices configuration # config NET_VENDOR_WIZNET bool "WIZnet devices" depends on HAS_IOMEM default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about WIZnet devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_WIZNET config WIZNET_W5100 tristate "WIZnet W5100 Ethernet support" depends on HAS_IOMEM help Support for WIZnet W5100 chips. W5100 is a single chip with integrated 10/100 Ethernet MAC, PHY and hardware TCP/IP stack, but this driver is limited to the MAC and PHY functions only, onchip TCP/IP is unused. To compile this driver as a module, choose M here: the module will be called w5100. config WIZNET_W5300 tristate "WIZnet W5300 Ethernet support" depends on HAS_IOMEM help Support for WIZnet W5300 chips. W5300 is a single chip with integrated 10/100 Ethernet MAC, PHY and hardware TCP/IP stack, but this driver is limited to the MAC and PHY functions only, onchip TCP/IP is unused. To compile this driver as a module, choose M here: the module will be called w5300. choice prompt "WIZnet interface mode" depends on WIZNET_W5100 || WIZNET_W5300 default WIZNET_BUS_ANY config WIZNET_BUS_DIRECT bool "Direct address bus mode" help In direct address mode host system can directly access all registers after mapping to Memory-Mapped I/O space. config WIZNET_BUS_INDIRECT bool "Indirect address bus mode" help In indirect address mode host system indirectly accesses registers using Indirect Mode Address Register and Indirect Mode Data Register, which are directly mapped to Memory-Mapped I/O space. config WIZNET_BUS_ANY bool "Select interface mode in runtime" help If interface mode is unknown in compile time, it can be selected in runtime from board/platform resources configuration. Performance may decrease compared to explicitly selected bus mode. endchoice config WIZNET_W5100_SPI tristate "WIZnet W5100/W5200/W5500 Ethernet support for SPI mode" depends on WIZNET_BUS_ANY && WIZNET_W5100 depends on SPI help In SPI mode host system accesses registers using SPI protocol (mode 0) on the SPI bus. Performance decreases compared to other bus interface mode. In W5100 SPI mode, burst READ/WRITE processing are not provided. To compile this driver as a module, choose M here: the module will be called w5100-spi. endif # NET_VENDOR_WIZNET PK ! �(� � wiznet/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_WIZNET_W5100) += w5100.o obj-$(CONFIG_WIZNET_W5100_SPI) += w5100-spi.o obj-$(CONFIG_WIZNET_W5300) += w5300.o PK ! gB�V` ` myricom/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Myricom device configuration # config NET_VENDOR_MYRI bool "Myricom devices" default y depends on PCI && INET help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Myricom cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_MYRI config MYRI10GE tristate "Myricom Myri-10G Ethernet support" depends on PCI && INET select FW_LOADER select CRC32 help This driver supports Myricom Myri-10G Dual Protocol interface in Ethernet mode. If the eeprom on your board is not recent enough, you will need a newer firmware image. You may get this image or more information, at: <http://www.myri.com/scs/download-Myri10GE.html> To compile this driver as a module, choose M here. The module will be called myri10ge. config MYRI10GE_DCA bool "Direct Cache Access (DCA) Support" default y depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) help Say Y here if you want to use Direct Cache Access (DCA) in the driver. DCA is a method for warming the CPU cache before data is used, with the intent of lessening the impact of cache misses. endif # NET_VENDOR_MYRI PK ! w�fȄ � myricom/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Myricom network device drivers. # obj-$(CONFIG_MYRI10GE) += myri10ge/ PK ! ��[�� � myricom/myri10ge/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Myricom Myri-10G ethernet driver # obj-$(CONFIG_MYRI10GE) += myri10ge.o PK ! |U]�� � huawei/hinic/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Huawei driver configuration # config HINIC tristate "Huawei Intelligent PCIE Network Interface Card" depends on (PCI_MSI && (X86 || ARM64)) select NET_DEVLINK help This driver supports HiNIC PCIE Ethernet cards. To compile this driver as part of the kernel, choose Y here. If unsure, choose N. The default is compiled as module. PK ! �斁 � huawei/hinic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_HINIC) += hinic.o hinic-y := hinic_main.o hinic_tx.o hinic_rx.o hinic_port.o hinic_hw_dev.o \ hinic_hw_io.o hinic_hw_qp.o hinic_hw_cmdq.o hinic_hw_wq.o \ hinic_hw_mgmt.o hinic_hw_api_cmd.o hinic_hw_eqs.o hinic_hw_if.o \ hinic_common.o hinic_ethtool.o hinic_devlink.o hinic_hw_mbox.o \ hinic_sriov.o hinic_debugfs.o PK ! �; a; ; huawei/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Huawei driver configuration # config NET_VENDOR_HUAWEI bool "Huawei devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Huawei cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_HUAWEI source "drivers/net/ethernet/huawei/hinic/Kconfig" endif # NET_VENDOR_HUAWEI PK ! E��Tu u huawei/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Huawei device drivers. # obj-$(CONFIG_HINIC) += hinic/ PK ! ��_&s s allwinner/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Allwinner device configuration # config NET_VENDOR_ALLWINNER bool "Allwinner devices" default y depends on ARCH_SUNXI help If you have a network (Ethernet) card belonging to this class, say Y here. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Allwinner cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ALLWINNER config SUN4I_EMAC tristate "Allwinner A10 EMAC support" depends on ARCH_SUNXI depends on OF select CRC32 select MII select PHYLIB select MDIO_SUN4I help Support for Allwinner A10 EMAC ethernet driver. To compile this driver as a module, choose M here. The module will be called sun4i-emac. endif # NET_VENDOR_ALLWINNER PK ! �K�"� � allwinner/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Allwinner device drivers. # obj-$(CONFIG_SUN4I_EMAC) += sun4i-emac.o PK ! �[t� � apm/xgene/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_XGENE tristate "APM X-Gene SoC Ethernet Driver" depends on ARCH_XGENE || COMPILE_TEST select PHYLIB select MDIO_XGENE select GPIOLIB help This is the Ethernet driver for the on-chip ethernet interface on the APM X-Gene SoC. To compile this driver as a module, choose M here. This module will be called xgene_enet. PK ! �QՏ" " apm/xgene/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for APM X-Gene Ethernet Driver. # xgene-enet-objs := xgene_enet_hw.o xgene_enet_sgmac.o xgene_enet_xgmac.o \ xgene_enet_main.o xgene_enet_ring2.o xgene_enet_ethtool.o \ xgene_enet_cle.o obj-$(CONFIG_NET_XGENE) += xgene-enet.o PK ! �=�� � apm/xgene-v2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_XGENE_V2 tristate "APM X-Gene SoC Ethernet-v2 Driver" depends on ARCH_XGENE || COMPILE_TEST help This is the Ethernet driver for the on-chip ethernet interface which uses a linked list of DMA descriptor architecture (v2) for APM X-Gene SoCs. To compile this driver as a module, choose M here. This module will be called xgene-enet-v2. PK ! ����� � apm/xgene-v2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for APM X-Gene Ethernet v2 driver # xgene-enet-v2-objs := main.o mac.o enet.o ring.o mdio.o ethtool.o obj-$(CONFIG_NET_XGENE_V2) += xgene-enet-v2.o PK ! ;t�G� � apm/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only source "drivers/net/ethernet/apm/xgene/Kconfig" source "drivers/net/ethernet/apm/xgene-v2/Kconfig" PK ! G�FJ� � apm/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for APM X-GENE Ethernet driver. # obj-$(CONFIG_NET_XGENE) += xgene/ obj-$(CONFIG_NET_XGENE_V2) += xgene-v2/ PK ! (; � � socionext/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_VENDOR_SOCIONEXT bool "Socionext ethernet drivers" default y help Option to select ethernet drivers for Socionext platforms. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Socionext devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SOCIONEXT config SNI_AVE tristate "Socionext AVE ethernet support" depends on (ARCH_UNIPHIER || COMPILE_TEST) && OF depends on HAS_IOMEM select MFD_SYSCON select PHYLIB help Driver for gigabit ethernet MACs, called AVE, in the Socionext UniPhier family. config SNI_NETSEC tristate "Socionext NETSEC ethernet support" depends on (ARCH_SYNQUACER || COMPILE_TEST) && OF select PHYLIB select PAGE_POOL select MII help Enable to add support for the SocioNext NetSec Gigabit Ethernet controller + PHY, as found on the Synquacer SC2A11 SoC To compile this driver as a module, choose M here: the module will be called netsec. If unsure, say N. endif #NET_VENDOR_SOCIONEXT PK ! �q� � socionext/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for all ethernet ip drivers on Socionext platforms # obj-$(CONFIG_SNI_AVE) += sni_ave.o obj-$(CONFIG_SNI_NETSEC) += netsec.o PK ! ��b b nxp/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config LPC_ENET tristate "NXP ethernet MAC on LPC devices" depends on ARCH_LPC32XX || COMPILE_TEST select PHYLIB select CRC32 help Say Y or M here if you want to use the NXP ethernet MAC included on some NXP LPC devices. You can safely enable this option for LPC32xx SoC. Also available as a module. PK ! �(H�L L nxp/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_LPC_ENET) += lpc_eth.o PK ! 9�� � renesas/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 # # Renesas device configuration # config NET_VENDOR_RENESAS bool "Renesas devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Renesas devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_RENESAS config SH_ETH tristate "Renesas SuperH Ethernet support" depends on ARCH_RENESAS || SUPERH || COMPILE_TEST select CRC32 select MII select MDIO_BITBANG select PHYLIB help Renesas SuperH Ethernet device driver. This driver supporting CPUs are: - SH7619, SH7710, SH7712, SH7724, SH7734, SH7763, SH7757, R8A7740, R8A774x, R8A777x and R8A779x. config RAVB tristate "Renesas Ethernet AVB support" depends on ARCH_RENESAS || COMPILE_TEST depends on PTP_1588_CLOCK_OPTIONAL select CRC32 select MII select MDIO_BITBANG select PHYLIB help Renesas Ethernet AVB device driver. This driver supports the following SoCs: - R8A779x. endif # NET_VENDOR_RENESAS PK ! b@ L� � renesas/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Renesas device drivers. # obj-$(CONFIG_SH_ETH) += sh_eth.o ravb-objs := ravb_main.o ravb_ptp.o obj-$(CONFIG_RAVB) += ravb.o PK ! ��>� � xilinx/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Xilink device configuration # config NET_VENDOR_XILINX bool "Xilinx devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Xilinx devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_XILINX config XILINX_EMACLITE tristate "Xilinx 10/100 Ethernet Lite support" depends on HAS_IOMEM select PHYLIB help This driver supports the 10/100 Ethernet Lite from Xilinx. config XILINX_AXI_EMAC tristate "Xilinx 10/100/1000 AXI Ethernet support" depends on HAS_IOMEM select PHYLINK help This driver supports the 10/100/1000 Ethernet from Xilinx for the AXI bus interface used in Xilinx Virtex FPGAs and Soc's. config XILINX_LL_TEMAC tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" depends on HAS_IOMEM select PHYLIB help This driver supports the Xilinx 10/100/1000 LocalLink TEMAC core used in Xilinx Spartan and Virtex FPGAs endif # NET_VENDOR_XILINX PK ! ��Y Y xilinx/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Xilink network device drivers. # ll_temac-objs := ll_temac_main.o ll_temac_mdio.o obj-$(CONFIG_XILINX_LL_TEMAC) += ll_temac.o obj-$(CONFIG_XILINX_EMACLITE) += xilinx_emaclite.o xilinx_emac-objs := xilinx_axienet_main.o xilinx_axienet_mdio.o obj-$(CONFIG_XILINX_AXI_EMAC) += xilinx_emac.o PK ! ͗l l brocade/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # QLogic BR-series device configuration # config NET_VENDOR_BROCADE bool "QLogic BR-series devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about QLogic BR-series cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_BROCADE source "drivers/net/ethernet/brocade/bna/Kconfig" endif # NET_VENDOR_BROCADE PK ! & �{ { brocade/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the QLogic BR-series device drivers. # obj-$(CONFIG_BNA) += bna/ PK ! %}62� � brocade/bna/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # QLogic BR-series network device configuration # config BNA tristate "QLogic BR-series 1010/1020/1860 10Gb Ethernet Driver support" depends on PCI help This driver supports QLogic BR-series 1010/1020/1860 10Gb CEE capable Ethernet cards. To compile this driver as a module, choose M here: the module will be called bna. For general information and support, go to the QLogic support website at: <http://support.qlogic.com> PK ! ֳ�e e brocade/bna/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Copyright (c) 2005-2014 Brocade Communications Systems, Inc. # Copyright (c) 2014-2015 QLogic Corporation. # All rights reserved. # obj-$(CONFIG_BNA) += bna.o bna-objs := bnad.o bnad_ethtool.o bnad_debugfs.o bna_enet.o bna_tx_rx.o bna-objs += bfa_msgq.o bfa_ioc.o bfa_ioc_ct.o bfa_cee.o bna-objs += cna_fwimg.o PK ! m�W3 nvidia/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # NVIDIA network device configuration # config NET_VENDOR_NVIDIA bool "NVIDIA devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about NVIDIA cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_NVIDIA config FORCEDETH tristate "nForce Ethernet support" depends on PCI help If you have a network (Ethernet) controller of this type, say Y here. To compile this driver as a module, choose M here. The module will be called forcedeth. endif # NET_VENDOR_NVIDIA PK ! 0�R�� � nvidia/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the NVIDIA network device drivers. # obj-$(CONFIG_FORCEDETH) += forcedeth.o PK ! ��t2 2 qlogic/netxen/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-or-later # Copyright (C) 2003 - 2009 NetXen, Inc. # Copyright (C) 2009 - QLogic Corporation. # All rights reserved. # obj-$(CONFIG_NETXEN_NIC) := netxen_nic.o netxen_nic-y := netxen_nic_hw.o netxen_nic_main.o netxen_nic_init.o \ netxen_nic_ethtool.o netxen_nic_ctx.o PK ! %�� qlogic/qede/Makefilenu �[��� # SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) # Copyright (c) 2019-2020 Marvell International Ltd. obj-$(CONFIG_QEDE) := qede.o qede-y := qede_main.o qede_fp.o qede_filter.o qede_ethtool.o qede_ptp.o qede-$(CONFIG_DCB) += qede_dcbnl.o qede-$(CONFIG_QED_RDMA) += qede_rdma.o PK ! ���� qlogic/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # QLogic network device configuration # config NET_VENDOR_QLOGIC bool "QLogic devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about QLogic cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_QLOGIC config QLA3XXX tristate "QLogic QLA3XXX Network Driver Support" depends on PCI help This driver supports QLogic ISP3XXX gigabit Ethernet cards. To compile this driver as a module, choose M here: the module will be called qla3xxx. config QLCNIC tristate "QLOGIC QLCNIC 1/10Gb Converged Ethernet NIC Support" depends on PCI select FW_LOADER help This driver supports QLogic QLE8240 and QLE8242 Converged Ethernet devices. config QLCNIC_SRIOV bool "QLOGIC QLCNIC 83XX family SR-IOV Support" depends on QLCNIC && PCI_IOV default y help This configuration parameter enables Single Root Input Output Virtualization support for QLE83XX Converged Ethernet devices. This allows for virtual function acceleration in virtualized environments. config QLCNIC_DCB bool "QLOGIC QLCNIC 82XX and 83XX family DCB Support" depends on QLCNIC && DCB default y help This configuration parameter enables DCB support in QLE83XX and QLE82XX Converged Ethernet devices. This allows for DCB get operations support through rtNetlink interface. Only CEE mode of DCB is supported. PG and PFC values are related only to Tx. config QLCNIC_HWMON bool "QLOGIC QLCNIC 82XX and 83XX family HWMON support" depends on QLCNIC && HWMON && !(QLCNIC=y && HWMON=m) default y help This configuration parameter can be used to read the board temperature in Converged Ethernet devices supported by qlcnic. This data is available via the hwmon sysfs interface. config NETXEN_NIC tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" depends on PCI select FW_LOADER help This enables the support for NetXen's Gigabit Ethernet card. config QED tristate "QLogic QED 25/40/100Gb core driver" depends on PCI select ZLIB_INFLATE select CRC8 select CRC32 select NET_DEVLINK help This enables the support for Marvell FastLinQ adapters family. config QED_LL2 bool config QED_SRIOV bool "QLogic QED 25/40/100Gb SR-IOV support" depends on QED && PCI_IOV default y help This configuration parameter enables Single Root Input Output Virtualization support for QED devices. This allows for virtual function acceleration in virtualized environments. config QEDE tristate "QLogic QED 25/40/100Gb Ethernet NIC" depends on QED depends on PTP_1588_CLOCK_OPTIONAL help This enables the support for Marvell FastLinQ adapters family, ethernet driver. config QED_RDMA bool config QED_ISCSI bool config QED_NVMETCP bool config QED_FCOE bool config QED_OOO bool endif # NET_VENDOR_QLOGIC PK ! ���� � qlogic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the QLogic network device drivers. # obj-$(CONFIG_QLA3XXX) += qla3xxx.o obj-$(CONFIG_QLCNIC) += qlcnic/ obj-$(CONFIG_NETXEN_NIC) += netxen/ obj-$(CONFIG_QED) += qed/ obj-$(CONFIG_QEDE)+= qede/ PK ! T��~� � qlogic/qlcnic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Qlogic 1G/10G Ethernet Driver for CNA devices # obj-$(CONFIG_QLCNIC) := qlcnic.o qlcnic-y := qlcnic_hw.o qlcnic_main.o qlcnic_init.o \ qlcnic_ethtool.o qlcnic_ctx.o qlcnic_io.o \ qlcnic_sysfs.o qlcnic_minidump.o qlcnic_83xx_hw.o \ qlcnic_83xx_init.o qlcnic_83xx_vnic.o \ qlcnic_sriov_common.o qlcnic-$(CONFIG_QLCNIC_SRIOV) += qlcnic_sriov_pf.o qlcnic-$(CONFIG_QLCNIC_DCB) += qlcnic_dcb.o PK ! �12 2 qlogic/qed/Makefilenu �[��� # SPDX-License-Identifier: (GPL-2.0-only OR BSD-3-Clause) # Copyright (c) 2019-2020 Marvell International Ltd. obj-$(CONFIG_QED) := qed.o qed-y := \ qed_chain.o \ qed_cxt.o \ qed_dcbx.o \ qed_debug.o \ qed_dev.o \ qed_devlink.o \ qed_hw.o \ qed_init_fw_funcs.o \ qed_init_ops.o \ qed_int.o \ qed_l2.o \ qed_main.o \ qed_mcp.o \ qed_mng_tlv.o \ qed_ptp.o \ qed_selftest.o \ qed_sp_commands.o \ qed_spq.o qed-$(CONFIG_QED_FCOE) += qed_fcoe.o qed-$(CONFIG_QED_ISCSI) += qed_iscsi.o qed-$(CONFIG_QED_LL2) += qed_ll2.o qed-$(CONFIG_QED_OOO) += qed_ooo.o qed-$(CONFIG_QED_NVMETCP) += \ qed_nvmetcp.o \ qed_nvmetcp_fw_funcs.o \ qed_nvmetcp_ip_services.o qed-$(CONFIG_QED_RDMA) += \ qed_iwarp.o \ qed_rdma.o \ qed_roce.o qed-$(CONFIG_QED_SRIOV) += \ qed_sriov.o \ qed_vf.o PK ! x�j�n n aquantia/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # aQuantia device configuration # config NET_VENDOR_AQUANTIA bool "aQuantia devices" default y help Set this to y if you have an Ethernet network cards that uses the aQuantia AQC107/AQC108 chipset. This option does not build any drivers; it causes the aQuantia drivers that can be built to appear in the list of Ethernet drivers. if NET_VENDOR_AQUANTIA config AQTION tristate "aQuantia AQtion(tm) Support" depends on PCI depends on MACSEC || MACSEC=n help This enables the support for the aQuantia AQtion(tm) Ethernet card. endif # NET_VENDOR_AQUANTIA PK ! �(�{ { aquantia/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the aQuantia device drivers. # obj-$(CONFIG_AQTION) += atlantic/ PK ! 7ӕ�f f aquantia/atlantic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only ################################################################################ # # aQuantia Ethernet Controller AQtion Linux Driver # Copyright(c) 2014-2017 aQuantia Corporation. # ################################################################################ obj-$(CONFIG_AQTION) += atlantic.o ccflags-y += -I$(srctree)/$(src) atlantic-objs := aq_main.o \ aq_nic.o \ aq_pci_func.o \ aq_vec.o \ aq_ring.o \ aq_hw_utils.o \ aq_ethtool.o \ aq_drvinfo.o \ aq_filters.o \ aq_phy.o \ hw_atl/hw_atl_a0.o \ hw_atl/hw_atl_b0.o \ hw_atl/hw_atl_utils.o \ hw_atl/hw_atl_utils_fw2x.o \ hw_atl/hw_atl_llh.o \ hw_atl2/hw_atl2.o \ hw_atl2/hw_atl2_utils.o \ hw_atl2/hw_atl2_utils_fw.o \ hw_atl2/hw_atl2_llh.o \ macsec/macsec_api.o atlantic-$(CONFIG_MACSEC) += aq_macsec.o atlantic-$(CONFIG_PTP_1588_CLOCK) += aq_ptp.o PK ! �3�� � amazon/ena/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Elastic Network Adapter (ENA) device drivers. # obj-$(CONFIG_ENA_ETHERNET) += ena.o ena-y := ena_netdev.o ena_com.o ena_eth_com.o ena_ethtool.o PK ! �0��( ( amazon/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Amazon network device configuration # config NET_VENDOR_AMAZON bool "Amazon Devices" default y help If you have a network (Ethernet) device belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Amazon devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_AMAZON config ENA_ETHERNET tristate "Elastic Network Adapter (ENA) support" depends on PCI_MSI && !CPU_BIG_ENDIAN select DIMLIB help This driver supports Elastic Network Adapter (ENA)" To compile this driver as a module, choose M here. The module will be called ena. endif #NET_VENDOR_AMAZON PK ! �Ö�� � amazon/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Amazon network device drivers. # obj-$(CONFIG_ENA_ETHERNET) += ena/ PK ! �8�_ _ cavium/thunder/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Cavium's Thunder ethernet device # obj-$(CONFIG_THUNDER_NIC_RGX) += thunder_xcv.o obj-$(CONFIG_THUNDER_NIC_BGX) += thunder_bgx.o obj-$(CONFIG_THUNDER_NIC_PF) += nicpf.o obj-$(CONFIG_THUNDER_NIC_VF) += nicvf.o nicpf-y := nic_main.o nicvf-y := nicvf_main.o nicvf_queues.o nicvf-y += nicvf_ethtool.o PK ! �+� - - cavium/liquidio/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Cavium Liquidio ethernet device driver # common-objs := lio_ethtool.o \ lio_core.o \ request_manager.o \ response_manager.o \ octeon_device.o \ cn66xx_device.o \ cn68xx_device.o \ cn23xx_pf_device.o \ cn23xx_vf_device.o \ octeon_mailbox.o \ octeon_mem_ops.o \ octeon_droq.o \ octeon_nic.o obj-$(CONFIG_LIQUIDIO) += liquidio.o liquidio-y := lio_main.o octeon_console.o lio_vf_rep.o $(common-objs) obj-$(CONFIG_LIQUIDIO_VF) += liquidio_vf.o liquidio_vf-y := lio_vf_main.o $(common-objs) PK ! s�~�Q Q cavium/common/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_CAVIUM_PTP) += cavium_ptp.o PK ! �O � cavium/octeon/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Cavium network device drivers. # obj-$(CONFIG_OCTEON_MGMT_ETHERNET) += octeon_mgmt.o PK ! <'�� � cavium/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Cavium ethernet device configuration # config NET_VENDOR_CAVIUM bool "Cavium ethernet drivers" default y help Select this option if you want enable Cavium network support. If you have a Cavium SoC or network adapter, say Y. if NET_VENDOR_CAVIUM config THUNDER_NIC_PF tristate "Thunder Physical function driver" depends on 64BIT && PCI select THUNDER_NIC_BGX help This driver supports Thunder's NIC physical function. The NIC provides the controller and DMA engines to move network traffic to/from the memory. The NIC works closely with TNS, BGX and SerDes to implement the functions replacing and virtualizing those of a typical standalone PCIe NIC chip. config THUNDER_NIC_VF tristate "Thunder Virtual function driver" imply CAVIUM_PTP depends on 64BIT && PCI help This driver supports Thunder's NIC virtual function config THUNDER_NIC_BGX tristate "Thunder MAC interface driver (BGX)" depends on 64BIT && PCI select PHYLIB select MDIO_THUNDER if PCI select THUNDER_NIC_RGX help This driver supports programming and controlling of MAC interface from NIC physical function driver. config THUNDER_NIC_RGX tristate "Thunder MAC interface driver (RGX)" depends on 64BIT && PCI select PHYLIB select MDIO_THUNDER if PCI help This driver supports configuring XCV block of RGX interface present on CN81XX chip. config CAVIUM_PTP tristate "Cavium PTP coprocessor as PTP clock" depends on 64BIT && PCI depends on PTP_1588_CLOCK help This driver adds support for the Precision Time Protocol Clocks and Timestamping coprocessor (PTP) found on Cavium processors. PTP provides timestamping mechanism that is suitable for use in IEEE 1588 Precision Time Protocol or other purposes. Timestamps can be used in BGX, TNS, GTI, and NIC blocks. config LIQUIDIO tristate "Cavium LiquidIO support" depends on 64BIT && PCI depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select FW_LOADER select LIBCRC32C select NET_DEVLINK help This driver supports Cavium LiquidIO Intelligent Server Adapters based on CN66XX, CN68XX and CN23XX chips. To compile this driver as a module, choose M here: the module will be called liquidio. This is recommended. config OCTEON_MGMT_ETHERNET tristate "Octeon Management port ethernet driver (CN5XXX, CN6XXX)" depends on CAVIUM_OCTEON_SOC select PHYLIB select MDIO_OCTEON default y help Enable the ethernet driver for the management port on Cavium Networks' Octeon CN57XX, CN56XX, CN55XX, CN54XX, CN52XX, and CN6XXX chips. config LIQUIDIO_VF tristate "Cavium LiquidIO VF support" depends on 64BIT && PCI_MSI depends on PTP_1588_CLOCK_OPTIONAL help This driver supports Cavium LiquidIO Intelligent Server Adapter based on CN23XX chips. To compile this driver as a module, choose M here: The module will be called liquidio_vf. MSI-X interrupt support is required for this driver to work correctly endif # NET_VENDOR_CAVIUM PK ! ӊ�� cavium/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Cavium ethernet device drivers. # obj-$(CONFIG_NET_VENDOR_CAVIUM) += common/ obj-$(CONFIG_NET_VENDOR_CAVIUM) += thunder/ obj-$(CONFIG_NET_VENDOR_CAVIUM) += liquidio/ obj-$(CONFIG_NET_VENDOR_CAVIUM) += octeon/ PK ! �2qH H Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Ethernet LAN device configuration # menuconfig ETHERNET bool "Ethernet driver support" depends on NET default y help This section contains all the Ethernet device drivers. if ETHERNET config MDIO tristate config SUNGEM_PHY tristate source "drivers/net/ethernet/3com/Kconfig" source "drivers/net/ethernet/actions/Kconfig" source "drivers/net/ethernet/adaptec/Kconfig" source "drivers/net/ethernet/aeroflex/Kconfig" source "drivers/net/ethernet/agere/Kconfig" source "drivers/net/ethernet/alacritech/Kconfig" source "drivers/net/ethernet/allwinner/Kconfig" source "drivers/net/ethernet/alteon/Kconfig" source "drivers/net/ethernet/altera/Kconfig" source "drivers/net/ethernet/amazon/Kconfig" source "drivers/net/ethernet/amd/Kconfig" source "drivers/net/ethernet/apm/Kconfig" source "drivers/net/ethernet/apple/Kconfig" source "drivers/net/ethernet/aquantia/Kconfig" source "drivers/net/ethernet/arc/Kconfig" source "drivers/net/ethernet/atheros/Kconfig" config CX_ECAT tristate "Beckhoff CX5020 EtherCAT master support" depends on PCI depends on X86 || COMPILE_TEST help Driver for EtherCAT master module located on CCAT FPGA that can be found on Beckhoff CX5020, and possibly other of CX Beckhoff CX series industrial PCs. To compile this driver as a module, choose M here. The module will be called ec_bhf. source "drivers/net/ethernet/broadcom/Kconfig" source "drivers/net/ethernet/cadence/Kconfig" source "drivers/net/ethernet/calxeda/Kconfig" source "drivers/net/ethernet/cavium/Kconfig" source "drivers/net/ethernet/chelsio/Kconfig" source "drivers/net/ethernet/cirrus/Kconfig" source "drivers/net/ethernet/cisco/Kconfig" source "drivers/net/ethernet/cortina/Kconfig" source "drivers/net/ethernet/davicom/Kconfig" config DNET tristate "Dave ethernet support (DNET)" depends on HAS_IOMEM select PHYLIB help The Dave ethernet interface (DNET) is found on Qong Board FPGA. Say Y to include support for the DNET chip. To compile this driver as a module, choose M here: the module will be called dnet. source "drivers/net/ethernet/dec/Kconfig" source "drivers/net/ethernet/dlink/Kconfig" source "drivers/net/ethernet/emulex/Kconfig" source "drivers/net/ethernet/ezchip/Kconfig" source "drivers/net/ethernet/faraday/Kconfig" source "drivers/net/ethernet/freescale/Kconfig" source "drivers/net/ethernet/fujitsu/Kconfig" source "drivers/net/ethernet/google/Kconfig" source "drivers/net/ethernet/hisilicon/Kconfig" source "drivers/net/ethernet/huawei/Kconfig" source "drivers/net/ethernet/i825xx/Kconfig" source "drivers/net/ethernet/ibm/Kconfig" source "drivers/net/ethernet/intel/Kconfig" source "drivers/net/ethernet/xscale/Kconfig" config JME tristate "JMicron(R) PCI-Express Gigabit Ethernet support" depends on PCI select CRC32 select MII help This driver supports the PCI-Express gigabit ethernet adapters based on JMicron JMC250 chipset. To compile this driver as a module, choose M here. The module will be called jme. config KORINA tristate "Korina (IDT RC32434) Ethernet support" depends on MIKROTIK_RB532 || COMPILE_TEST select CRC32 select MII help If you have a Mikrotik RouterBoard 500 or IDT RC32434 based system say Y. Otherwise say N. config LANTIQ_ETOP tristate "Lantiq SoC ETOP driver" depends on SOC_TYPE_XWAY help Support for the MII0 inside the Lantiq SoC config LANTIQ_XRX200 tristate "Lantiq / Intel xRX200 PMAC network driver" depends on SOC_TYPE_XWAY help Support for the PMAC of the Gigabit switch (GSWIP) inside the Lantiq / Intel VRX200 VDSL SoC source "drivers/net/ethernet/litex/Kconfig" source "drivers/net/ethernet/marvell/Kconfig" source "drivers/net/ethernet/mediatek/Kconfig" source "drivers/net/ethernet/mellanox/Kconfig" source "drivers/net/ethernet/micrel/Kconfig" source "drivers/net/ethernet/microchip/Kconfig" source "drivers/net/ethernet/mscc/Kconfig" source "drivers/net/ethernet/microsoft/Kconfig" source "drivers/net/ethernet/moxa/Kconfig" source "drivers/net/ethernet/myricom/Kconfig" config FEALNX tristate "Myson MTD-8xx PCI Ethernet support" depends on PCI select CRC32 select MII help Say Y here to support the Myson MTD-800 family of PCI-based Ethernet cards. <http://www.myson.com.tw/> source "drivers/net/ethernet/ni/Kconfig" source "drivers/net/ethernet/natsemi/Kconfig" source "drivers/net/ethernet/neterion/Kconfig" source "drivers/net/ethernet/netronome/Kconfig" source "drivers/net/ethernet/8390/Kconfig" source "drivers/net/ethernet/nvidia/Kconfig" source "drivers/net/ethernet/nxp/Kconfig" source "drivers/net/ethernet/oki-semi/Kconfig" config ETHOC tristate "OpenCores 10/100 Mbps Ethernet MAC support" depends on HAS_IOMEM && HAS_DMA select MII select PHYLIB select CRC32 select BITREVERSE help Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. source "drivers/net/ethernet/packetengines/Kconfig" source "drivers/net/ethernet/pasemi/Kconfig" source "drivers/net/ethernet/pensando/Kconfig" source "drivers/net/ethernet/qlogic/Kconfig" source "drivers/net/ethernet/brocade/Kconfig" source "drivers/net/ethernet/qualcomm/Kconfig" source "drivers/net/ethernet/rdc/Kconfig" source "drivers/net/ethernet/realtek/Kconfig" source "drivers/net/ethernet/renesas/Kconfig" source "drivers/net/ethernet/rocker/Kconfig" source "drivers/net/ethernet/samsung/Kconfig" source "drivers/net/ethernet/seeq/Kconfig" source "drivers/net/ethernet/sgi/Kconfig" source "drivers/net/ethernet/silan/Kconfig" source "drivers/net/ethernet/sis/Kconfig" source "drivers/net/ethernet/sfc/Kconfig" source "drivers/net/ethernet/smsc/Kconfig" source "drivers/net/ethernet/socionext/Kconfig" source "drivers/net/ethernet/stmicro/Kconfig" source "drivers/net/ethernet/sun/Kconfig" source "drivers/net/ethernet/synopsys/Kconfig" source "drivers/net/ethernet/tehuti/Kconfig" source "drivers/net/ethernet/ti/Kconfig" source "drivers/net/ethernet/toshiba/Kconfig" source "drivers/net/ethernet/tundra/Kconfig" source "drivers/net/ethernet/via/Kconfig" source "drivers/net/ethernet/wiznet/Kconfig" source "drivers/net/ethernet/xilinx/Kconfig" source "drivers/net/ethernet/xircom/Kconfig" endif # ETHERNET PK ! ���� � Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Linux network Ethernet device drivers. # obj-$(CONFIG_NET_VENDOR_3COM) += 3com/ obj-$(CONFIG_NET_VENDOR_8390) += 8390/ obj-$(CONFIG_NET_VENDOR_ACTIONS) += actions/ obj-$(CONFIG_NET_VENDOR_ADAPTEC) += adaptec/ obj-$(CONFIG_GRETH) += aeroflex/ obj-$(CONFIG_NET_VENDOR_AGERE) += agere/ obj-$(CONFIG_NET_VENDOR_ALACRITECH) += alacritech/ obj-$(CONFIG_NET_VENDOR_ALLWINNER) += allwinner/ obj-$(CONFIG_NET_VENDOR_ALTEON) += alteon/ obj-$(CONFIG_ALTERA_TSE) += altera/ obj-$(CONFIG_NET_VENDOR_AMAZON) += amazon/ obj-$(CONFIG_NET_VENDOR_AMD) += amd/ obj-$(CONFIG_NET_XGENE) += apm/ obj-$(CONFIG_NET_VENDOR_APPLE) += apple/ obj-$(CONFIG_NET_VENDOR_AQUANTIA) += aquantia/ obj-$(CONFIG_NET_VENDOR_ARC) += arc/ obj-$(CONFIG_NET_VENDOR_ATHEROS) += atheros/ obj-$(CONFIG_NET_VENDOR_CADENCE) += cadence/ obj-$(CONFIG_NET_VENDOR_BROADCOM) += broadcom/ obj-$(CONFIG_NET_VENDOR_BROCADE) += brocade/ obj-$(CONFIG_NET_CALXEDA_XGMAC) += calxeda/ obj-$(CONFIG_NET_VENDOR_CAVIUM) += cavium/ obj-$(CONFIG_NET_VENDOR_CHELSIO) += chelsio/ obj-$(CONFIG_NET_VENDOR_CIRRUS) += cirrus/ obj-$(CONFIG_NET_VENDOR_CISCO) += cisco/ obj-$(CONFIG_NET_VENDOR_CORTINA) += cortina/ obj-$(CONFIG_CX_ECAT) += ec_bhf.o obj-$(CONFIG_DM9000) += davicom/ obj-$(CONFIG_DNET) += dnet.o obj-$(CONFIG_NET_VENDOR_DEC) += dec/ obj-$(CONFIG_NET_VENDOR_DLINK) += dlink/ obj-$(CONFIG_NET_VENDOR_EMULEX) += emulex/ obj-$(CONFIG_NET_VENDOR_EZCHIP) += ezchip/ obj-$(CONFIG_NET_VENDOR_FARADAY) += faraday/ obj-$(CONFIG_NET_VENDOR_FREESCALE) += freescale/ obj-$(CONFIG_NET_VENDOR_FUJITSU) += fujitsu/ obj-$(CONFIG_NET_VENDOR_GOOGLE) += google/ obj-$(CONFIG_NET_VENDOR_HISILICON) += hisilicon/ obj-$(CONFIG_NET_VENDOR_HUAWEI) += huawei/ obj-$(CONFIG_NET_VENDOR_IBM) += ibm/ obj-$(CONFIG_NET_VENDOR_INTEL) += intel/ obj-$(CONFIG_NET_VENDOR_I825XX) += i825xx/ obj-$(CONFIG_NET_VENDOR_MICROSOFT) += microsoft/ obj-$(CONFIG_NET_VENDOR_XSCALE) += xscale/ obj-$(CONFIG_JME) += jme.o obj-$(CONFIG_KORINA) += korina.o obj-$(CONFIG_LANTIQ_ETOP) += lantiq_etop.o obj-$(CONFIG_LANTIQ_XRX200) += lantiq_xrx200.o obj-$(CONFIG_NET_VENDOR_LITEX) += litex/ obj-$(CONFIG_NET_VENDOR_MARVELL) += marvell/ obj-$(CONFIG_NET_VENDOR_MEDIATEK) += mediatek/ obj-$(CONFIG_NET_VENDOR_MELLANOX) += mellanox/ obj-$(CONFIG_NET_VENDOR_MICREL) += micrel/ obj-$(CONFIG_NET_VENDOR_MICROCHIP) += microchip/ obj-$(CONFIG_NET_VENDOR_MICROSEMI) += mscc/ obj-$(CONFIG_NET_VENDOR_MOXART) += moxa/ obj-$(CONFIG_NET_VENDOR_MYRI) += myricom/ obj-$(CONFIG_FEALNX) += fealnx.o obj-$(CONFIG_NET_VENDOR_NATSEMI) += natsemi/ obj-$(CONFIG_NET_VENDOR_NETERION) += neterion/ obj-$(CONFIG_NET_VENDOR_NETRONOME) += netronome/ obj-$(CONFIG_NET_VENDOR_NI) += ni/ obj-$(CONFIG_NET_VENDOR_NVIDIA) += nvidia/ obj-$(CONFIG_LPC_ENET) += nxp/ obj-$(CONFIG_NET_VENDOR_OKI) += oki-semi/ obj-$(CONFIG_ETHOC) += ethoc.o obj-$(CONFIG_NET_VENDOR_PACKET_ENGINES) += packetengines/ obj-$(CONFIG_NET_VENDOR_PASEMI) += pasemi/ obj-$(CONFIG_NET_VENDOR_QLOGIC) += qlogic/ obj-$(CONFIG_NET_VENDOR_QUALCOMM) += qualcomm/ obj-$(CONFIG_NET_VENDOR_REALTEK) += realtek/ obj-$(CONFIG_NET_VENDOR_RENESAS) += renesas/ obj-$(CONFIG_NET_VENDOR_RDC) += rdc/ obj-$(CONFIG_NET_VENDOR_ROCKER) += rocker/ obj-$(CONFIG_NET_VENDOR_SAMSUNG) += samsung/ obj-$(CONFIG_NET_VENDOR_SEEQ) += seeq/ obj-$(CONFIG_NET_VENDOR_SILAN) += silan/ obj-$(CONFIG_NET_VENDOR_SIS) += sis/ obj-$(CONFIG_NET_VENDOR_SOLARFLARE) += sfc/ obj-$(CONFIG_NET_VENDOR_SGI) += sgi/ obj-$(CONFIG_NET_VENDOR_SMSC) += smsc/ obj-$(CONFIG_NET_VENDOR_SOCIONEXT) += socionext/ obj-$(CONFIG_NET_VENDOR_STMICRO) += stmicro/ obj-$(CONFIG_NET_VENDOR_SUN) += sun/ obj-$(CONFIG_NET_VENDOR_TEHUTI) += tehuti/ obj-$(CONFIG_NET_VENDOR_TI) += ti/ obj-$(CONFIG_NET_VENDOR_TOSHIBA) += toshiba/ obj-$(CONFIG_NET_VENDOR_TUNDRA) += tundra/ obj-$(CONFIG_NET_VENDOR_VIA) += via/ obj-$(CONFIG_NET_VENDOR_WIZNET) += wiznet/ obj-$(CONFIG_NET_VENDOR_XILINX) += xilinx/ obj-$(CONFIG_NET_VENDOR_XIRCOM) += xircom/ obj-$(CONFIG_NET_VENDOR_SYNOPSYS) += synopsys/ obj-$(CONFIG_NET_VENDOR_PENSANDO) += pensando/ PK ! Z��~ ~ smsc/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Western Digital/SMC network device configuration # config NET_VENDOR_SMSC bool "SMC (SMSC)/Western Digital devices" default y depends on ARM || ARM64 || ATARI_ETHERNAT || COLDFIRE || \ ISA || MAC || MIPS || NIOS2 || PCI || \ PCMCIA || SUPERH || XTENSA || H8300 || COMPILE_TEST help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about SMC/Western Digital cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SMSC config SMC9194 tristate "SMC 9194 support" depends on ISA select CRC32 select NETDEV_LEGACY_INIT help This is support for the SMC9xxx based Ethernet cards. Choose this option if you have a DELL laptop with the docking station, or another SMC9192/9194 based chipset. Say Y if you want it compiled into the kernel, and read the file <file:Documentation/networking/device_drivers/ethernet/smsc/smc9.rst>. To compile this driver as a module, choose M here. The module will be called smc9194. config SMC91X tristate "SMC 91C9x/91C1xxx support" select CRC32 select MII depends on !OF || GPIOLIB depends on ARM || ARM64 || ATARI_ETHERNAT || COLDFIRE || \ MIPS || NIOS2 || SUPERH || XTENSA || H8300 || COMPILE_TEST help This is a driver for SMC's 91x series of Ethernet chipsets, including the SMC91C94 and the SMC91C111. Say Y if you want it compiled into the kernel, and read the file <file:Documentation/networking/device_drivers/ethernet/smsc/smc9.rst>. This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called smc91x. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.rst>. config PCMCIA_SMC91C92 tristate "SMC 91Cxx PCMCIA support" depends on PCMCIA select CRC32 select MII help Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA (PC-card) Ethernet or Fast Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called smc91c92_cs. If unsure, say N. config EPIC100 tristate "SMC EtherPower II" depends on PCI select CRC32 select MII help This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, which is based on the SMC83c17x (EPIC/100). More specific information and updates are available from <http://www.scyld.com/network/epic100.html>. config SMC911X tristate "SMSC LAN911[5678] support" select CRC32 select MII depends on (ARM || SUPERH || COMPILE_TEST) help This is a driver for SMSC's LAN911x series of Ethernet chipsets including the new LAN9115, LAN9116, LAN9117, and LAN9118. Say Y here if you want it compiled into the kernel. This driver is also available as a module. The module will be called smc911x. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.rst> config SMSC911X tristate "SMSC LAN911x/LAN921x families embedded ethernet support" depends on HAS_IOMEM select CRC32 select MII select PHYLIB help Say Y here if you want support for SMSC LAN911x and LAN921x families of ethernet controllers. To compile this driver as a module, choose M here. The module will be called smsc911x. config SMSC911X_ARCH_HOOKS def_bool n depends on SMSC911X help If the arch enables this, it allows the arch to implement various hooks for more comprehensive interrupt control and also to override the source of the MAC address. config SMSC9420 tristate "SMSC LAN9420 PCI ethernet adapter support" depends on PCI select CRC32 select PHYLIB select SMSC_PHY help This is a driver for SMSC's LAN9420 PCI ethernet adapter. Say Y here if you want it compiled into the kernel. This driver is also available as a module. The module will be called smsc9420. If you want to compile it as a module, say M here and read <file:Documentation/kbuild/modules.rst> endif # NET_VENDOR_SMSC PK ! m��6[ [ smsc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the SMSC network device drivers. # obj-$(CONFIG_SMC9194) += smc9194.o obj-$(CONFIG_SMC91X) += smc91x.o obj-$(CONFIG_PCMCIA_SMC91C92) += smc91c92_cs.o obj-$(CONFIG_EPIC100) += epic100.o obj-$(CONFIG_SMSC9420) += smsc9420.o obj-$(CONFIG_SMC911X) += smc911x.o obj-$(CONFIG_SMSC911X) += smsc911x.o PK ! �S� � cadence/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Cadence device configuration # config NET_VENDOR_CADENCE bool "Cadence devices" depends on HAS_IOMEM default y help If you have a network (Ethernet) card belonging to this class, say Y. If unsure, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the remaining Cadence network card questions. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_CADENCE config MACB tristate "Cadence MACB/GEM support" depends on HAS_DMA && COMMON_CLK depends on PTP_1588_CLOCK_OPTIONAL select PHYLINK select CRC32 help The Cadence MACB ethernet interface is found on many Atmel AT32 and AT91 parts. This driver also supports the Cadence GEM (Gigabit Ethernet MAC found in some ARM SoC devices). Say Y to include support for the MACB/GEM chip. To compile this driver as a module, choose M here: the module will be macb. config MACB_USE_HWSTAMP bool "Use IEEE 1588 hwstamp" depends on MACB depends on PTP_1588_CLOCK default y help Enable IEEE 1588 Precision Time Protocol (PTP) support for MACB. config MACB_PCI tristate "Cadence PCI MACB/GEM support" depends on MACB && PCI help This is PCI wrapper for MACB driver. To compile this driver as a module, choose M here: the module will be called macb_pci. endif # NET_VENDOR_CADENCE PK ! ��P�� � cadence/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Atmel network device drivers. # macb-y := macb_main.o ifeq ($(CONFIG_MACB_USE_HWSTAMP),y) macb-y += macb_ptp.o endif obj-$(CONFIG_MACB) += macb.o obj-$(CONFIG_MACB_PCI) += macb_pci.o PK ! ���ӡ � davicom/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Davicom device configuration # config DM9000 tristate "DM9000 support" depends on ARM || MIPS || COLDFIRE || NIOS2 || COMPILE_TEST select CRC32 select MII help Support for DM9000 chipset. To compile this driver as a module, choose M here. The module will be called dm9000. config DM9000_FORCE_SIMPLE_PHY_POLL bool "Force simple NSR based PHY polling" depends on DM9000 help This configuration forces the DM9000 to use the NSR's LinkStatus bit to determine if the link is up or down instead of the more costly MII PHY reads. Note, this will not work if the chip is operating with an external PHY. PK ! �߳>y y davicom/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Davicom device drivers. # obj-$(CONFIG_DM9000) += dm9000.o PK ! i%��� � adaptec/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Adaptec network device configuration # config NET_VENDOR_ADAPTEC bool "Adaptec devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Adaptec cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_ADAPTEC config ADAPTEC_STARFIRE tristate "Adaptec Starfire/DuraLAN support" depends on PCI select CRC32 select MII help Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network adapter. The DuraLAN chip is used on the 64 bit PCI boards from Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip driver. To compile this driver as a module, choose M here: the module will be called starfire. This is recommended. endif # NET_VENDOR_ADAPTEC PK ! A��� � adaptec/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Adaptec network device drivers. # obj-$(CONFIG_ADAPTEC_STARFIRE) += starfire.o PK ! �%� � packetengines/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Packet Engines device configuration # config NET_VENDOR_PACKET_ENGINES bool "Packet Engines devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Packet Engines devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_PACKET_ENGINES config HAMACHI tristate "Packet Engines Hamachi GNIC-II support" depends on PCI select MII help If you have a Gigabit Ethernet card of this type, say Y here. To compile this driver as a module, choose M here. The module will be called hamachi. config YELLOWFIN tristate "Packet Engines Yellowfin Gigabit-NIC support" depends on PCI select CRC32 help Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is used by the Beowulf Linux cluster project. See <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more information about this driver in particular and Beowulf in general. To compile this driver as a module, choose M here: the module will be called yellowfin. This is recommended. endif # NET_VENDOR_PACKET_ENGINES PK ! |�N]� � packetengines/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Packet Engines network device drivers. # obj-$(CONFIG_HAMACHI) += hamachi.o obj-$(CONFIG_YELLOWFIN) += yellowfin.o PK ! ��V5 pasemi/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # PA Semi network device configuration # config NET_VENDOR_PASEMI bool "PA Semi devices" default y depends on PPC_PASEMI && PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about PA Semi cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_PASEMI config PASEMI_MAC tristate "PA Semi 1/10Gbit MAC" depends on PPC_PASEMI && PCI select PHYLIB help This driver supports the on-chip 1/10Gbit Ethernet controller on PA Semi's PWRficient line of chips. endif # NET_VENDOR_PASEMI PK ! �)�� � pasemi/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the A Semi network device drivers. # obj-$(CONFIG_PASEMI_MAC) += pasemi_mac_driver.o pasemi_mac_driver-objs := pasemi_mac.o pasemi_mac_ethtool.o PK ! O]��C C sgi/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # SGI device configuration # config NET_VENDOR_SGI bool "SGI devices" default y depends on (PCI && SGI_MFD_IOC3) || SGI_IP32 help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about SGI devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SGI config SGI_IOC3_ETH bool "SGI IOC3 Ethernet" depends on PCI && SGI_MFD_IOC3 select CRC16 select CRC32 select MII help If you have a network (Ethernet) card of this type, say Y here. config SGI_O2MACE_ETH tristate "SGI O2 MACE Fast Ethernet support" depends on SGI_IP32=y endif # NET_VENDOR_SGI PK ! �W�a� � sgi/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the SGI device drivers. # obj-$(CONFIG_SGI_O2MACE_ETH) += meth.o obj-$(CONFIG_SGI_IOC3_ETH) += ioc3-eth.o PK ! �䴢 sis/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Silicon Integrated Systems (SiS) device configuration # config NET_VENDOR_SIS bool "Silicon Integrated Systems (SiS) devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about SiS devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SIS config SIS900 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" depends on PCI select CRC32 select MII help This is a driver for the Fast Ethernet PCI network cards based on the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in SiS 630 and SiS 540 chipsets. This driver also supports AMD 79C901 HomePNA so that you can use your phone line as a network cable. To compile this driver as a module, choose M here: the module will be called sis900. This is recommended. config SIS190 tristate "SiS190/SiS191 gigabit ethernet support" depends on PCI select CRC32 select MII help Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to appear in lan on motherboard designs which are based on SiS 965 and SiS 966 south bridge. To compile this driver as a module, choose M here: the module will be called sis190. This is recommended. endif # NET_VENDOR_SIS PK ! c�7B� � sis/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for Silicon Integrated Systems (SiS) network device drivers. # obj-$(CONFIG_SIS190) += sis190.o obj-$(CONFIG_SIS900) += sis900.o PK ! ��1� � faraday/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Faraday device configuration # config NET_VENDOR_FARADAY bool "Faraday devices" default y depends on ARM || NDS32 || COMPILE_TEST help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Faraday cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_FARADAY config FTMAC100 tristate "Faraday FTMAC100 10/100 Ethernet support" depends on ARM || NDS32 || COMPILE_TEST depends on !64BIT || BROKEN select MII help This driver supports the FTMAC100 10/100 Ethernet controller from Faraday. It is used on Faraday A320, Andes AG101 and some other ARM/NDS32 SoC's. config FTGMAC100 tristate "Faraday FTGMAC100 Gigabit Ethernet support" depends on ARM || NDS32 || COMPILE_TEST depends on !64BIT || BROKEN select PHYLIB select MDIO_ASPEED if MACH_ASPEED_G6 select CRC32 help This driver supports the FTGMAC100 Gigabit Ethernet controller from Faraday. It is used on Faraday A369, Andes AG102 and some other ARM/NDS32 SoC's. endif # NET_VENDOR_FARADAY PK ! �@� � faraday/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Faraday device drivers. # obj-$(CONFIG_FTGMAC100) += ftgmac100.o obj-$(CONFIG_FTMAC100) += ftmac100.o PK ! �R.a a xscale/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Intel XScale IXP device configuration # config NET_VENDOR_XSCALE bool "Intel XScale IXP devices" default y depends on NET_VENDOR_INTEL && (ARM && ARCH_IXP4XX && \ IXP4XX_NPE && IXP4XX_QMGR) help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question does not directly affect the kernel: saying N will just cause the configurator to skip all the questions about XScale IXP devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_XSCALE config IXP4XX_ETH tristate "Intel IXP4xx Ethernet support" depends on ARM && ARCH_IXP4XX && IXP4XX_NPE && IXP4XX_QMGR select PHYLIB select OF_MDIO if OF select NET_PTP_CLASSIFY help Say Y here if you want to use built-in Ethernet ports on IXP4xx processor. config PTP_1588_CLOCK_IXP46X bool "Intel IXP46x as PTP clock" depends on IXP4XX_ETH depends on PTP_1588_CLOCK=y || PTP_1588_CLOCK=IXP4XX_ETH default y help This driver adds support for using the IXP46X as a PTP clock. This clock is only useful if your PTP programs are getting hardware time stamps on the PTP Ethernet packets using the SO_TIMESTAMPING API. To compile this driver as a module, choose M here: the module will be called ptp_ixp46x. endif # NET_VENDOR_XSCALE PK ! `�� xscale/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Intel XScale IXP device drivers. # # Keep this link order to avoid deferred probing ifdef CONFIG_PTP_1588_CLOCK_IXP46X obj-$(CONFIG_IXP4XX_ETH) += ptp_ixp46x.o endif obj-$(CONFIG_IXP4XX_ETH) += ixp4xx_eth.o PK ! ��0� � marvell/octeontx2/nic/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Marvell's RVU Ethernet device drivers # obj-$(CONFIG_OCTEONTX2_PF) += rvu_nicpf.o obj-$(CONFIG_OCTEONTX2_VF) += rvu_nicvf.o rvu_nicpf-y := otx2_pf.o otx2_common.o otx2_txrx.o otx2_ethtool.o \ otx2_ptp.o otx2_flows.o otx2_tc.o cn10k.o otx2_dmac_flt.o \ otx2_devlink.o rvu_nicvf-y := otx2_vf.o otx2_devlink.o ccflags-y += -I$(srctree)/drivers/net/ethernet/marvell/octeontx2/af PK ! �J*� � marvell/octeontx2/af/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Marvell's RVU Admin Function driver # ccflags-y += -I$(src) obj-$(CONFIG_OCTEONTX2_MBOX) += rvu_mbox.o obj-$(CONFIG_OCTEONTX2_AF) += rvu_af.o rvu_mbox-y := mbox.o rvu_trace.o rvu_af-y := cgx.o rvu.o rvu_cgx.o rvu_npa.o rvu_nix.o \ rvu_reg.o rvu_npc.o rvu_debugfs.o ptp.o rvu_npc_fs.o \ rvu_cpt.o rvu_devlink.o rpm.o rvu_cn10k.o rvu_switch.o \ rvu_sdp.o PK ! �s^�R R marvell/octeontx2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Marvell RVU Network drivers configuration # config OCTEONTX2_MBOX tristate config OCTEONTX2_AF tristate "Marvell OcteonTX2 RVU Admin Function driver" select OCTEONTX2_MBOX select NET_DEVLINK depends on (64BIT && COMPILE_TEST) || ARM64 depends on PCI depends on PTP_1588_CLOCK_OPTIONAL help This driver supports Marvell's OcteonTX2 Resource Virtualization Unit's admin function manager which manages all RVU HW resources and provides a medium to other PF/VFs to configure HW. Should be enabled for other RVU device drivers to work. config NDC_DIS_DYNAMIC_CACHING bool "Disable caching of dynamic entries in NDC" depends on OCTEONTX2_AF default n help This config option disables caching of dynamic entries such as NIX SQEs , NPA stack pages etc in NDC. Also locks down NIX SQ/CQ/RQ/RSS and NPA Aura/Pool contexts. config OCTEONTX2_PF tristate "Marvell OcteonTX2 NIC Physical Function driver" select OCTEONTX2_MBOX select NET_DEVLINK depends on (64BIT && COMPILE_TEST) || ARM64 depends on PCI depends on PTP_1588_CLOCK_OPTIONAL help This driver supports Marvell's OcteonTX2 NIC physical function. config OCTEONTX2_VF tristate "Marvell OcteonTX2 NIC Virtual Function driver" depends on OCTEONTX2_PF help This driver supports Marvell's OcteonTX2 NIC virtual function. PK ! �.��� � marvell/octeontx2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for Marvell OcteonTX2 device drivers. # obj-$(CONFIG_OCTEONTX2_MBOX) += af/ obj-$(CONFIG_OCTEONTX2_AF) += af/ obj-$(CONFIG_OCTEONTX2_PF) += nic/ PK ! ���d d marvell/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Marvell device configuration # config NET_VENDOR_MARVELL bool "Marvell devices" default y depends on PCI || CPU_PXA168 || PPC32 || PLAT_ORION || INET || COMPILE_TEST help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Marvell devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_MARVELL config MV643XX_ETH tristate "Marvell Discovery (643XX) and Orion ethernet support" depends on PPC32 || PLAT_ORION || COMPILE_TEST depends on INET select PHYLIB select MVMDIO help This driver supports the gigabit ethernet MACs in the Marvell Discovery PPC/MIPS chipset family (MV643XX) and in the Marvell Orion ARM SoC family. Some boards that use the Discovery chipset are the Momenco Ocelot C and Jaguar ATX and Pegasos II. config MVMDIO tristate "Marvell MDIO interface support" depends on HAS_IOMEM select PHYLIB help This driver supports the MDIO interface found in the network interface units of the Marvell EBU SoCs (Kirkwood, Orion5x, Dove, Armada 370 and Armada XP). This driver is used by the MV643XX_ETH and MVNETA drivers. config MVNETA_BM_ENABLE tristate "Marvell Armada 38x/XP network interface BM support" depends on MVNETA depends on !64BIT help This driver supports auxiliary block of the network interface units in the Marvell ARMADA XP and ARMADA 38x SoC family, which is called buffer manager. This driver, when enabled, strictly cooperates with mvneta driver and is common for all network ports of the devices, even for Armada 370 SoC, which doesn't support hardware buffer management. config MVNETA tristate "Marvell Armada 370/38x/XP/37xx network interface support" depends on ARCH_MVEBU || COMPILE_TEST select MVMDIO select PHYLINK select PAGE_POOL help This driver supports the network interface units in the Marvell ARMADA XP, ARMADA 370, ARMADA 38x and ARMADA 37xx SoC family. Note that this driver is distinct from the mv643xx_eth driver, which should be used for the older Marvell SoCs (Dove, Orion, Discovery, Kirkwood). config MVNETA_BM tristate depends on !64BIT default y if MVNETA=y && MVNETA_BM_ENABLE!=n default MVNETA_BM_ENABLE select HWBM select GENERIC_ALLOCATOR help MVNETA_BM must not be 'm' if MVNETA=y, so this symbol ensures that all dependencies are met. config MVPP2 tristate "Marvell Armada 375/7K/8K network interface support" depends on ARCH_MVEBU || COMPILE_TEST select MVMDIO select PHYLINK select PAGE_POOL help This driver supports the network interface units in the Marvell ARMADA 375, 7K and 8K SoCs. config MVPP2_PTP bool "Marvell Armada 8K Enable PTP support" depends on (PTP_1588_CLOCK = y && MVPP2 = y) || \ (PTP_1588_CLOCK && MVPP2 = m) config PXA168_ETH tristate "Marvell pxa168 ethernet support" depends on HAS_IOMEM depends on CPU_PXA168 || ARCH_BERLIN || COMPILE_TEST select PHYLIB help This driver supports the pxa168 Ethernet ports. To compile this driver as a module, choose M here. The module will be called pxa168_eth. config SKGE tristate "Marvell Yukon Gigabit Ethernet support" depends on PCI select CRC32 help This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx and related Gigabit Ethernet adapters. It is a new smaller driver with better performance and more complete ethtool support. It does not support the link failover and network management features that "portable" vendor supplied sk98lin driver does. This driver supports adapters based on the original Yukon chipset: Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. It does not support the newer Yukon2 chipset: a separate driver, sky2, is provided for these adapters. To compile this driver as a module, choose M here: the module will be called skge. This is recommended. config SKGE_DEBUG bool "Debugging interface" depends on SKGE && DEBUG_FS help This option adds the ability to dump driver state for debugging. The file /sys/kernel/debug/skge/ethX displays the state of the internal transmit and receive rings. If unsure, say N. config SKGE_GENESIS bool "Support for older SysKonnect Genesis boards" depends on SKGE help This enables support for the older and uncommon SysKonnect Genesis chips, which support MII via an external transceiver, instead of an internal one. Disabling this option will save some memory by making code smaller. If unsure say Y. config SKY2 tristate "Marvell Yukon 2 support" depends on PCI select CRC32 help This driver supports Gigabit Ethernet adapters based on the Marvell Yukon 2 chipset: Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 There is companion driver for the older Marvell Yukon and SysKonnect Genesis based adapters: skge. To compile this driver as a module, choose M here: the module will be called sky2. This is recommended. config SKY2_DEBUG bool "Debugging interface" depends on SKY2 && DEBUG_FS help This option adds the ability to dump driver state for debugging. The file /sys/kernel/debug/sky2/ethX displays the state of the internal transmit and receive rings. If unsure, say N. source "drivers/net/ethernet/marvell/octeontx2/Kconfig" source "drivers/net/ethernet/marvell/prestera/Kconfig" endif # NET_VENDOR_MARVELL PK ! &� � marvell/mvpp2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Marvell PPv2 driver. # obj-$(CONFIG_MVPP2) := mvpp2.o mvpp2-y := mvpp2_main.o mvpp2_prs.o mvpp2_cls.o mvpp2_debugfs.o mvpp2-$(CONFIG_MVPP2_PTP) += mvpp2_tai.o PK ! nx'x� � marvell/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Marvell device drivers. # obj-$(CONFIG_MVMDIO) += mvmdio.o obj-$(CONFIG_MV643XX_ETH) += mv643xx_eth.o obj-$(CONFIG_MVNETA_BM) += mvneta_bm.o obj-$(CONFIG_MVNETA) += mvneta.o obj-$(CONFIG_MVPP2) += mvpp2/ obj-$(CONFIG_PXA168_ETH) += pxa168_eth.o obj-$(CONFIG_SKGE) += skge.o obj-$(CONFIG_SKY2) += sky2.o obj-y += octeontx2/ obj-y += prestera/ PK ! ���� � marvell/prestera/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Marvell Prestera drivers configuration # config PRESTERA tristate "Marvell Prestera Switch ASICs support" depends on NET_SWITCHDEV && VLAN_8021Q depends on BRIDGE || BRIDGE=n select NET_DEVLINK help This driver supports Marvell Prestera Switch ASICs family. To compile this driver as a module, choose M here: the module will be called prestera. config PRESTERA_PCI tristate "PCI interface driver for Marvell Prestera Switch ASICs family" depends on PCI && HAS_IOMEM && PRESTERA default PRESTERA help This is implementation of PCI interface support for Marvell Prestera Switch ASICs family. To compile this driver as a module, choose M here: the module will be called prestera_pci. PK ! v�|(Y Y marvell/prestera/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_PRESTERA) += prestera.o prestera-objs := prestera_main.o prestera_hw.o prestera_dsa.o \ prestera_rxtx.o prestera_devlink.o prestera_ethtool.o \ prestera_switchdev.o prestera_acl.o prestera_flow.o \ prestera_flower.o prestera_span.o obj-$(CONFIG_PRESTERA_PCI) += prestera_pci.o PK ! �|>� � alacritech/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config NET_VENDOR_ALACRITECH bool "Alacritech devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Alacritech devices. If you say Y, you will be asked for your specific device in the following questions. if NET_VENDOR_ALACRITECH config SLICOSS tristate "Alacritech Slicoss support" depends on PCI select CRC32 help This driver supports Gigabit Ethernet adapters based on the Session Layer Interface (SLIC) technology by Alacritech. Supported are Mojave (1 port) and Oasis (1, 2 and 4 port) cards, both copper and fiber. To compile this driver as a module, choose M here: the module will be called slicoss. This is recommended. endif # NET_VENDOR_ALACRITECH PK ! �1`| | alacritech/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Alacritech Slicoss driver # obj-$(CONFIG_SLICOSS) += slicoss.o PK ! ɨQy� � chelsio/libcxgb/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only ccflags-y := -I $(srctree)/$(src)/../cxgb4 obj-$(CONFIG_CHELSIO_LIB) += libcxgb.o libcxgb-y := libcxgb_ppm.o libcxgb_cm.o PK ! ���� � ' chelsio/inline_crypto/ch_ipsec/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only ccflags-y := -I $(srctree)/drivers/net/ethernet/chelsio/cxgb4 \ -I $(srctree)/drivers/crypto/chelsio obj-$(CONFIG_CHELSIO_IPSEC_INLINE) += ch_ipsec.o ch_ipsec-objs := chcr_ipsec.o PK ! ���]U U chelsio/inline_crypto/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Chelsio inline crypto configuration # config CHELSIO_INLINE_CRYPTO bool "Chelsio Inline Crypto support" depends on CHELSIO_T4 default y help Enable support for inline crypto. Allows enable/disable from list of inline crypto drivers. if CHELSIO_INLINE_CRYPTO config CRYPTO_DEV_CHELSIO_TLS tristate "Chelsio Crypto Inline TLS Driver" depends on CHELSIO_T4 depends on TLS depends on TLS_TOE help Support Chelsio Inline TLS with Chelsio crypto accelerator. Enable inline TLS support for Tx and Rx. To compile this driver as a module, choose M here: the module will be called chtls. config CHELSIO_IPSEC_INLINE tristate "Chelsio IPSec XFRM Tx crypto offload" depends on CHELSIO_T4 depends on XFRM_OFFLOAD depends on INET_ESP_OFFLOAD || INET6_ESP_OFFLOAD help Support Chelsio Inline IPsec with Chelsio crypto accelerator. Enable inline IPsec support for Tx. To compile this driver as a module, choose M here: the module will be called ch_ipsec. config CHELSIO_TLS_DEVICE tristate "Chelsio Inline KTLS Offload" depends on CHELSIO_T4 depends on TLS depends on TLS_DEVICE select CRYPTO_LIB_AES help This flag enables support for kernel tls offload over Chelsio T6 crypto accelerator. CONFIG_CHELSIO_TLS_DEVICE flag can be enabled only if CONFIG_TLS and CONFIG_TLS_DEVICE flags are enabled. To compile this driver as a module, choose M here: the module will be called ch_ktls. endif # CHELSIO_INLINE_CRYPTO PK ! �� $ chelsio/inline_crypto/chtls/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only ccflags-y := -I $(srctree)/drivers/net/ethernet/chelsio/cxgb4 \ -I $(srctree)/drivers/crypto/chelsio obj-$(CONFIG_CRYPTO_DEV_CHELSIO_TLS) += chtls.o chtls-objs := chtls_main.o chtls_cm.o chtls_io.o chtls_hw.o PK ! � �ߴ � chelsio/inline_crypto/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_CRYPTO_DEV_CHELSIO_TLS) += chtls/ obj-$(CONFIG_CHELSIO_IPSEC_INLINE) += ch_ipsec/ obj-$(CONFIG_CHELSIO_TLS_DEVICE) += ch_ktls/ PK ! ��g� � & chelsio/inline_crypto/ch_ktls/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only ccflags-y := -I $(srctree)/drivers/net/ethernet/chelsio/cxgb4 obj-$(CONFIG_CHELSIO_TLS_DEVICE) += ch_ktls.o ch_ktls-objs := chcr_ktls.o PK ! Q�O� � chelsio/cxgb/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Chelsio T1 driver # obj-$(CONFIG_CHELSIO_T1) += cxgb.o cxgb-$(CONFIG_CHELSIO_T1_1G) += mv88e1xxx.o vsc7326.o cxgb-objs := cxgb2.o espi.o tp.o pm3393.o sge.o subr.o \ mv88x201x.o my3126.o $(cxgb-y) PK ! [ %�y y chelsio/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Chelsio device configuration # config NET_VENDOR_CHELSIO bool "Chelsio devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Chelsio devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_CHELSIO config CHELSIO_T1 tristate "Chelsio 10Gb Ethernet support" depends on PCI select CRC32 select MDIO help This driver supports Chelsio gigabit and 10-gigabit Ethernet cards. More information about adapter features and performance tuning is in <file:Documentation/networking/device_drivers/ethernet/chelsio/cxgb.rst>. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module, choose M here: the module will be called cxgb. config CHELSIO_T1_1G bool "Chelsio gigabit Ethernet support" depends on CHELSIO_T1 help Enables support for Chelsio's gigabit Ethernet PCI cards. If you are using only 10G cards say 'N' here. config CHELSIO_T3 tristate "Chelsio Communications T3 10Gb Ethernet support" depends on PCI && INET select FW_LOADER select MDIO help This driver supports Chelsio T3-based gigabit and 10Gb Ethernet adapters. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module, choose M here: the module will be called cxgb3. config CHELSIO_T4 tristate "Chelsio Communications T4/T5/T6 Ethernet support" depends on PCI && (IPV6 || IPV6=n) && (TLS || TLS=n) depends on PTP_1588_CLOCK_OPTIONAL select FW_LOADER select MDIO select ZLIB_DEFLATE help This driver supports Chelsio T4, T5 & T6 based gigabit, 10Gb Ethernet adapter and T5/T6 based 40Gb and T6 based 25Gb, 50Gb and 100Gb Ethernet adapters. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module choose M here; the module will be called cxgb4. config CHELSIO_T4_DCB bool "Data Center Bridging (DCB) Support for Chelsio T4/T5/T6 cards" default n depends on CHELSIO_T4 && DCB help Enable DCB support through rtNetlink interface. Say Y here if you want to enable Data Center Bridging (DCB) support in the driver. If unsure, say N. config CHELSIO_T4_FCOE bool "Fibre Channel over Ethernet (FCoE) Support for Chelsio T5 cards" default n depends on CHELSIO_T4 && CHELSIO_T4_DCB && FCOE help Enable FCoE offload features. Say Y here if you want to enable Fibre Channel over Ethernet (FCoE) support in the driver. If unsure, say N. config CHELSIO_T4VF tristate "Chelsio Communications T4/T5/T6 Virtual Function Ethernet support" depends on PCI help This driver supports Chelsio T4, T5 & T6 based gigabit, 10Gb Ethernet adapters and T5/T6 based 40Gb and T6 based 25Gb, 50Gb and 100Gb Ethernet adapters with PCI-E SR-IOV Virtual Functions. For general information about Chelsio and our products, visit our website at <http://www.chelsio.com>. For customer support, please visit our customer support page at <http://www.chelsio.com/support.html>. Please send feedback to <linux-bugs@chelsio.com>. To compile this driver as a module choose M here; the module will be called cxgb4vf. config CHELSIO_LIB tristate help Common library for Chelsio drivers. source "drivers/net/ethernet/chelsio/inline_crypto/Kconfig" endif # NET_VENDOR_CHELSIO PK ! ��� F F chelsio/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Chelsio network device drivers. # obj-$(CONFIG_CHELSIO_T1) += cxgb/ obj-$(CONFIG_CHELSIO_T3) += cxgb3/ obj-$(CONFIG_CHELSIO_T4) += cxgb4/ obj-$(CONFIG_CHELSIO_T4VF) += cxgb4vf/ obj-$(CONFIG_CHELSIO_LIB) += libcxgb/ obj-$(CONFIG_CHELSIO_INLINE_CRYPTO) += inline_crypto/ PK ! ���� � chelsio/cxgb3/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Chelsio T3 driver # obj-$(CONFIG_CHELSIO_T3) += cxgb3.o cxgb3-objs := cxgb3_main.o ael1002.o vsc8211.o t3_hw.o mc5.o \ xgmac.o sge.o l2t.o cxgb3_offload.o aq100x.o PK ! ���� � chelsio/cxgb4vf/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Chelsio T4 SR-IOV Virtual Function Driver # obj-$(CONFIG_CHELSIO_T4VF) += cxgb4vf.o cxgb4vf-objs := cxgb4vf_main.o t4vf_hw.o sge.o PK ! �f�UJ J chelsio/cxgb4/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Chelsio T4 driver # obj-$(CONFIG_CHELSIO_T4) += cxgb4.o cxgb4-objs := cxgb4_main.o l2t.o smt.o t4_hw.o sge.o clip_tbl.o cxgb4_ethtool.o \ cxgb4_uld.o srq.o sched.o cxgb4_filter.o cxgb4_tc_u32.o \ cxgb4_ptp.o cxgb4_tc_flower.o cxgb4_cudbg.o cxgb4_mps.o \ cudbg_common.o cudbg_lib.o cudbg_zlib.o cxgb4_tc_mqprio.o \ cxgb4_tc_matchall.o cxgb4-$(CONFIG_CHELSIO_T4_DCB) += cxgb4_dcb.o cxgb4-$(CONFIG_CHELSIO_T4_FCOE) += cxgb4_fcoe.o cxgb4-$(CONFIG_DEBUG_FS) += cxgb4_debugfs.o cxgb4-$(CONFIG_THERMAL) += cxgb4_thermal.o PK ! ���h h oki-semi/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # OKI Semiconductor device configuration # config NET_VENDOR_OKI bool "OKI Semiconductor devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about OKI Semiconductor cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_OKI source "drivers/net/ethernet/oki-semi/pch_gbe/Kconfig" endif # NET_VENDOR_OKI PK ! _�;�� � oki-semi/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the OKI Semiconductor device drivers. # obj-$(CONFIG_PCH_GBE) += pch_gbe/ PK ! sK�� � oki-semi/pch_gbe/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # OKI Semiconductor device configuration # config PCH_GBE tristate "OKI SEMICONDUCTOR IOH(ML7223/ML7831) GbE" depends on PCI && (X86_32 || COMPILE_TEST) depends on PTP_1588_CLOCK select MII select PTP_1588_CLOCK_PCH select NET_PTP_CLASSIFY help This is a gigabit ethernet driver for EG20T PCH. EG20T PCH is the platform controller hub that is used in Intel's general embedded platform. EG20T PCH has Gigabit Ethernet interface. Using this interface, it is able to access system devices connected to Gigabit Ethernet. This driver enables Gigabit Ethernet function. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/ Output Hub), ML7223/ML7831. ML7223 IOH is for MP(Media Phone) use. ML7831 IOH is for general purpose use. ML7223/ML7831 is companion chip for Intel Atom E6xx series. ML7223/ML7831 is completely compatible for Intel EG20T PCH. PK ! 4��� � oki-semi/pch_gbe/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only obj-$(CONFIG_PCH_GBE) += pch_gbe.o pch_gbe-y := pch_gbe_phy.o pch_gbe_ethtool.o pch_gbe_param.o pch_gbe-y += pch_gbe_main.o PK ! ����2 2 cortina/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 # Cortina ethernet devices config NET_VENDOR_CORTINA bool "Cortina Gemini devices" default y help If you have a network (Ethernet) card belonging to this class, say Y and read the Ethernet-HOWTO, available from <https://www.tldp.org/docs.html#howto>. if NET_VENDOR_CORTINA config GEMINI_ETHERNET tristate "Gemini Gigabit Ethernet support" depends on OF depends on HAS_IOMEM select PHYLIB select CRC32 help This driver supports StorLink SL351x (Gemini) dual Gigabit Ethernet. endif # NET_VENDOR_CORTINA PK ! �D�� � cortina/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # Makefile for the Cortina Gemini network device drivers. obj-$(CONFIG_GEMINI_ETHERNET) += gemini.o PK ! " ��� � cirrus/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Cirrus network device configuration # config NET_VENDOR_CIRRUS bool "Cirrus devices" default y depends on ISA || EISA || ARM || MAC || COMPILE_TEST help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Cirrus cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_CIRRUS config CS89x0 tristate config CS89x0_ISA tristate "CS89x0 ISA driver support" depends on HAS_IOPORT_MAP depends on ISA depends on !PPC32 depends on CS89x0_PLATFORM=n select NETDEV_LEGACY_INIT select CS89x0 help Support for CS89x0 chipset based Ethernet cards. If you have a network (Ethernet) card of this type, say Y and read the file <file:Documentation/networking/device_drivers/ethernet/cirrus/cs89x0.rst>. To compile this driver as a module, choose M here. The module will be called cs89x0. config CS89x0_PLATFORM tristate "CS89x0 platform driver support" depends on ARM || (COMPILE_TEST && !PPC) select CS89x0 help Say Y to compile the cs89x0 platform driver. This makes this driver suitable for use on certain evaluation boards such as the iMX21ADS. To compile this driver as a module, choose M here. The module will be called cs89x0. config EP93XX_ETH tristate "EP93xx Ethernet support" depends on (ARM && ARCH_EP93XX) || COMPILE_TEST select MII help This is a driver for the ethernet hardware included in EP93xx CPUs. Say Y if you are building a kernel for EP93xx based devices. config MAC89x0 tristate "Macintosh CS89x0 based ethernet cards" depends on MAC help Support for CS89x0 chipset based Ethernet cards. If you have a Nubus or LC-PDS network (Ethernet) card of this type, say Y here. To compile this driver as a module, choose M here. This module will be called mac89x0. endif # NET_VENDOR_CIRRUS PK ! �R�� � cirrus/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Cirrus network device drivers. # obj-$(CONFIG_CS89x0) += cs89x0.o obj-$(CONFIG_EP93XX_ETH) += ep93xx_eth.o obj-$(CONFIG_MAC89x0) += mac89x0.o PK ! x�* dlink/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # D-Link device configuration # config NET_VENDOR_DLINK bool "D-Link devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about D-Link devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_DLINK config DL2K tristate "DL2000/TC902x/IP1000A-based Gigabit Ethernet support" depends on PCI select CRC32 help This driver supports DL2000/TC902x/IP1000A-based Gigabit ethernet cards, which includes D-Link DGE-550T Gigabit Ethernet Adapter. D-Link DL2000-based Gigabit Ethernet Adapter. Sundance/Tamarack TC902x Gigabit Ethernet Adapter. ICPlus IP1000A-based cards To compile this driver as a module, choose M here: the module will be called dl2k. config SUNDANCE tristate "Sundance Alta support" depends on PCI select CRC32 select MII help This driver is for the Sundance "Alta" chip. More specific information and updates are available from <http://www.scyld.com/network/sundance.html>. config SUNDANCE_MMIO bool "Use MMIO instead of PIO" depends on SUNDANCE help Enable memory-mapped I/O for interaction with Sundance NIC registers. Do NOT enable this by default, PIO (enabled when MMIO is disabled) is known to solve bugs on certain chips. If unsure, say N. endif # NET_VENDOR_DLINK PK ! �jO�� � dlink/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the D-Link network device drivers. # obj-$(CONFIG_DL2K) += dl2k.o obj-$(CONFIG_SUNDANCE) += sundance.o PK ! ���P P stmicro/stmmac/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config STMMAC_ETH tristate "STMicroelectronics Multi-Gigabit Ethernet driver" depends on HAS_IOMEM && HAS_DMA depends on PTP_1588_CLOCK_OPTIONAL select MII select PCS_XPCS select PAGE_POOL select PHYLINK select CRC32 select RESET_CONTROLLER help This is the driver for the Ethernet IPs built around a Synopsys IP Core. if STMMAC_ETH config STMMAC_SELFTESTS bool "Support for STMMAC Selftests" depends on INET depends on STMMAC_ETH default n help This adds support for STMMAC Selftests using ethtool. Enable this feature if you are facing problems with your HW and submit the test results to the netdev Mailing List. config STMMAC_PLATFORM tristate "STMMAC Platform bus support" depends on STMMAC_ETH select MFD_SYSCON default y help This selects the platform specific bus support for the stmmac driver. This is the driver used on several SoCs: STi, Allwinner, Amlogic Meson, Altera SOCFPGA. If you have a controller with this interface, say Y or M here. If unsure, say N. if STMMAC_PLATFORM config DWMAC_DWC_QOS_ETH tristate "Support for snps,dwc-qos-ethernet.txt DT binding." select CRC32 select MII depends on OF && HAS_DMA help Support for chips using the snps,dwc-qos-ethernet.txt DT binding. config DWMAC_GENERIC tristate "Generic driver for DWMAC" default STMMAC_PLATFORM help Generic DWMAC driver for platforms that don't require any platform specific code to function or is using platform data for setup. config DWMAC_ANARION tristate "Adaptrum Anarion GMAC support" default ARC depends on OF && (ARC || COMPILE_TEST) help Support for Adaptrum Anarion GMAC Ethernet controller. This selects the Anarion SoC glue layer support for the stmmac driver. config DWMAC_INGENIC tristate "Ingenic MAC support" default MACH_INGENIC depends on OF && HAS_IOMEM && (MACH_INGENIC || COMPILE_TEST) select MFD_SYSCON help Support for ethernet controller on Ingenic SoCs. This selects Ingenic SoCs glue layer support for the stmmac device driver. This driver is used on for the Ingenic SoCs MAC ethernet controller. config DWMAC_IPQ806X tristate "QCA IPQ806x DWMAC support" default ARCH_QCOM depends on OF && (ARCH_QCOM || COMPILE_TEST) select MFD_SYSCON help Support for QCA IPQ806X DWMAC Ethernet. This selects the IPQ806x SoC glue layer support for the stmmac device driver. This driver does not use any of the hardware acceleration features available on this SoC. Network devices will behave like standard non-accelerated ethernet interfaces. config DWMAC_LPC18XX tristate "NXP LPC18xx/43xx DWMAC support" default ARCH_LPC18XX depends on OF && (ARCH_LPC18XX || COMPILE_TEST) select MFD_SYSCON help Support for NXP LPC18xx/43xx DWMAC Ethernet. config DWMAC_MEDIATEK tristate "MediaTek MT27xx GMAC support" depends on OF && (ARCH_MEDIATEK || COMPILE_TEST) help Support for MediaTek GMAC Ethernet controller. This selects the MT2712 SoC support for the stmmac driver. config DWMAC_MESON tristate "Amlogic Meson dwmac support" default ARCH_MESON depends on OF && COMMON_CLK && (ARCH_MESON || COMPILE_TEST) help Support for Ethernet controller on Amlogic Meson SoCs. This selects the Amlogic Meson SoC glue layer support for the stmmac device driver. This driver is used for Meson6, Meson8, Meson8b and GXBB SoCs. config DWMAC_OXNAS tristate "Oxford Semiconductor OXNAS dwmac support" default ARCH_OXNAS depends on OF && COMMON_CLK && (ARCH_OXNAS || COMPILE_TEST) select MFD_SYSCON help Support for Ethernet controller on Oxford Semiconductor OXNAS SoCs. This selects the Oxford Semiconductor OXNASSoC glue layer support for the stmmac device driver. This driver is used for OX820. config DWMAC_QCOM_ETHQOS tristate "Qualcomm ETHQOS support" default ARCH_QCOM depends on OF && (ARCH_QCOM || COMPILE_TEST) help Support for the Qualcomm ETHQOS core. This selects the Qualcomm ETHQOS glue layer support for the stmmac device driver. config DWMAC_ROCKCHIP tristate "Rockchip dwmac support" default ARCH_ROCKCHIP depends on OF && (ARCH_ROCKCHIP || COMPILE_TEST) select MFD_SYSCON help Support for Ethernet controller on Rockchip RK3288 SoC. This selects the Rockchip RK3288 SoC glue layer support for the stmmac device driver. config DWMAC_SOCFPGA tristate "SOCFPGA dwmac support" default ARCH_INTEL_SOCFPGA depends on OF && (ARCH_INTEL_SOCFPGA || COMPILE_TEST) select MFD_SYSCON help Support for ethernet controller on Altera SOCFPGA This selects the Altera SOCFPGA SoC glue layer support for the stmmac device driver. This driver is used for arria5 and cyclone5 FPGA SoCs. config DWMAC_STI tristate "STi GMAC support" default ARCH_STI depends on OF && (ARCH_STI || COMPILE_TEST) select MFD_SYSCON help Support for ethernet controller on STi SOCs. This selects STi SoC glue layer support for the stmmac device driver. This driver is used on for the STi series SOCs GMAC ethernet controller. config DWMAC_STM32 tristate "STM32 DWMAC support" default ARCH_STM32 depends on OF && HAS_IOMEM && (ARCH_STM32 || COMPILE_TEST) select MFD_SYSCON help Support for ethernet controller on STM32 SOCs. This selects STM32 SoC glue layer support for the stmmac device driver. This driver is used on for the STM32 series SOCs GMAC ethernet controller. config DWMAC_SUNXI tristate "Allwinner GMAC support" default ARCH_SUNXI depends on OF && (ARCH_SUNXI || COMPILE_TEST) help Support for Allwinner A20/A31 GMAC ethernet controllers. This selects Allwinner SoC glue layer support for the stmmac device driver. This driver is used for A20/A31 GMAC ethernet controller. config DWMAC_SUN8I tristate "Allwinner sun8i GMAC support" default ARCH_SUNXI depends on OF && (ARCH_SUNXI || COMPILE_TEST) select MDIO_BUS_MUX help Support for Allwinner H3 A83T A64 EMAC ethernet controllers. This selects Allwinner SoC glue layer support for the stmmac device driver. This driver is used for H3/A83T/A64 EMAC ethernet controller. config DWMAC_IMX8 tristate "NXP IMX8 DWMAC support" default ARCH_MXC depends on OF && (ARCH_MXC || COMPILE_TEST) select MFD_SYSCON help Support for ethernet controller on NXP i.MX8 SOCs. This selects NXP SoC glue layer support for the stmmac device driver. This driver is used for i.MX8 series like iMX8MP/iMX8DXL GMAC ethernet controller. config DWMAC_INTEL_PLAT tristate "Intel dwmac support" depends on OF && COMMON_CLK depends on STMMAC_ETH help Support for ethernet controllers on Intel SoCs This selects the Intel platform specific glue layer support for the stmmac device driver. This driver is used for the Intel Keem Bay SoC. config DWMAC_VISCONTI tristate "Toshiba Visconti DWMAC support" default ARCH_VISCONTI depends on OF && COMMON_CLK && (ARCH_VISCONTI || COMPILE_TEST) help Support for ethernet controller on Visconti SoCs. endif config DWMAC_INTEL tristate "Intel GMAC support" default X86 depends on X86 && STMMAC_ETH && PCI depends on COMMON_CLK help This selects the Intel platform specific bus support for the stmmac driver. This driver is used for Intel Quark/EHL/TGL. config DWMAC_LOONGSON tristate "Loongson PCI DWMAC support" default MACH_LOONGSON64 depends on (MACH_LOONGSON64 || COMPILE_TEST) && STMMAC_ETH && PCI depends on COMMON_CLK help This selects the LOONGSON PCI bus support for the stmmac driver, Support for ethernet controller on Loongson-2K1000 SoC and LS7A1000 bridge. config STMMAC_PCI tristate "STMMAC PCI bus support" depends on STMMAC_ETH && PCI depends on COMMON_CLK help This selects the platform specific bus support for the stmmac driver. This driver was tested on XLINX XC2V3000 FF1152AMT0221 D1215994A VIRTEX FPGA board and SNPS QoS IPK Prototyping Kit. If you have a controller with this interface, say Y or M here. If unsure, say N. endif PK ! �r#�0 0 stmicro/stmmac/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 obj-$(CONFIG_STMMAC_ETH) += stmmac.o stmmac-objs:= stmmac_main.o stmmac_ethtool.o stmmac_mdio.o ring_mode.o \ chain_mode.o dwmac_lib.o dwmac1000_core.o dwmac1000_dma.o \ dwmac100_core.o dwmac100_dma.o enh_desc.o norm_desc.o \ mmc_core.o stmmac_hwtstamp.o stmmac_ptp.o dwmac4_descs.o \ dwmac4_dma.o dwmac4_lib.o dwmac4_core.o dwmac5.o hwif.o \ stmmac_tc.o dwxgmac2_core.o dwxgmac2_dma.o dwxgmac2_descs.o \ stmmac_xdp.o \ $(stmmac-y) stmmac-$(CONFIG_STMMAC_SELFTESTS) += stmmac_selftests.o # Ordering matters. Generic driver must be last. obj-$(CONFIG_STMMAC_PLATFORM) += stmmac-platform.o obj-$(CONFIG_DWMAC_ANARION) += dwmac-anarion.o obj-$(CONFIG_DWMAC_INGENIC) += dwmac-ingenic.o obj-$(CONFIG_DWMAC_IPQ806X) += dwmac-ipq806x.o obj-$(CONFIG_DWMAC_LPC18XX) += dwmac-lpc18xx.o obj-$(CONFIG_DWMAC_MEDIATEK) += dwmac-mediatek.o obj-$(CONFIG_DWMAC_MESON) += dwmac-meson.o dwmac-meson8b.o obj-$(CONFIG_DWMAC_OXNAS) += dwmac-oxnas.o obj-$(CONFIG_DWMAC_QCOM_ETHQOS) += dwmac-qcom-ethqos.o obj-$(CONFIG_DWMAC_ROCKCHIP) += dwmac-rk.o obj-$(CONFIG_DWMAC_SOCFPGA) += dwmac-altr-socfpga.o obj-$(CONFIG_DWMAC_STI) += dwmac-sti.o obj-$(CONFIG_DWMAC_STM32) += dwmac-stm32.o obj-$(CONFIG_DWMAC_SUNXI) += dwmac-sunxi.o obj-$(CONFIG_DWMAC_SUN8I) += dwmac-sun8i.o obj-$(CONFIG_DWMAC_DWC_QOS_ETH) += dwmac-dwc-qos-eth.o obj-$(CONFIG_DWMAC_INTEL_PLAT) += dwmac-intel-plat.o obj-$(CONFIG_DWMAC_GENERIC) += dwmac-generic.o obj-$(CONFIG_DWMAC_IMX8) += dwmac-imx.o obj-$(CONFIG_DWMAC_VISCONTI) += dwmac-visconti.o stmmac-platform-objs:= stmmac_platform.o dwmac-altr-socfpga-objs := altr_tse_pcs.o dwmac-socfpga.o obj-$(CONFIG_STMMAC_PCI) += stmmac-pci.o obj-$(CONFIG_DWMAC_INTEL) += dwmac-intel.o obj-$(CONFIG_DWMAC_LOONGSON) += dwmac-loongson.o stmmac-pci-objs:= stmmac_pci.o PK ! BI_� � stmicro/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # STMicroelectronics device configuration # config NET_VENDOR_STMICRO bool "STMicroelectronics devices" default y depends on HAS_IOMEM help If you have a network (Ethernet) card based on Synopsys Ethernet IP Cores, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about STMicroelectronics cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_STMICRO source "drivers/net/ethernet/stmicro/stmmac/Kconfig" endif # NET_VENDOR_STMICRO PK ! � z� � stmicro/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the STMicroelectronics device drivers. # obj-$(CONFIG_STMMAC_ETH) += stmmac/ PK ! h5{O@ @ i825xx/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Intel 82596/82593/82596 network device configuration # config NET_VENDOR_I825XX bool "Intel (82586/82593/82596) devices" default y depends on NET_VENDOR_INTEL help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question does not directly affect the kernel: saying N will just cause the configurator to skip all the questions about these devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_I825XX config ARM_ETHER1 tristate "Acorn Ether1 support" depends on ARM && ARCH_ACORN help If you have an Acorn system with one of these (AKA25) network cards, you should say Y to this option if you wish to use it with Linux. config BVME6000_NET tristate "BVME6000 Ethernet support" depends on BVME6000 help This is the driver for the Ethernet interface on BVME4000 and BVME6000 VME boards. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config LASI_82596 tristate "Lasi ethernet" depends on GSC help Say Y here to support the builtin Intel 82596 ethernet controller found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet. config MVME16x_NET tristate "MVME16x Ethernet support" depends on MVME16x help This is the driver for the Ethernet interface on the Motorola MVME162, 166, 167, 172 and 177 boards. Say Y here to include the driver for this chip in your kernel. To compile this driver as a module, choose M here. config SNI_82596 tristate "SNI RM ethernet" depends on SNI_RM help Say Y here to support the on-board Intel 82596 ethernet controller built into SNI RM machines. config SUN3_82586 bool "Sun3 on-board Intel 82586 support" depends on SUN3 help This driver enables support for the on-board Intel 82586 based Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note that this driver does not support 82586-based adapters on additional VME boards. endif # NET_VENDOR_I825XX PK ! 3j)T T i825xx/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Intel 82586/82593/82596 chipset device drivers. # obj-$(CONFIG_ARM_ETHER1) += ether1.o obj-$(CONFIG_SUN3_82586) += sun3_82586.o obj-$(CONFIG_LASI_82596) += lasi_82596.o obj-$(CONFIG_SNI_82596) += sni_82596.o obj-$(CONFIG_MVME16x_NET) += 82596.o obj-$(CONFIG_BVME6000_NET) += 82596.o PK ! �Z�,j j xircom/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Xircom network device configuration # config NET_VENDOR_XIRCOM bool "Xircom devices" default y depends on PCMCIA help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Xircom cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_XIRCOM config PCMCIA_XIRC2PS tristate "Xircom 16-bit PCMCIA support" depends on PCMCIA help Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card) Ethernet or Fast Ethernet card to your computer. To compile this driver as a module, choose M here: the module will be called xirc2ps_cs. If unsure, say N. endif # NET_VENDOR_XIRCOM PK ! �Xw� � xircom/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Xircom network device drivers. # obj-$(CONFIG_PCMCIA_XIRC2PS) += xirc2ps_cs.o PK ! � � � sfc/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Solarflare device configuration # config NET_VENDOR_SOLARFLARE bool "Solarflare devices" default y help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Solarflare devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_SOLARFLARE config SFC tristate "Solarflare SFC9000/SFC9100/EF100-family support" depends on PCI depends on PTP_1588_CLOCK_OPTIONAL select MDIO select CRC32 help This driver supports 10/40-gigabit Ethernet cards based on the Solarflare SFC9000-family and SFC9100-family controllers. It also supports 10/25/40/100-gigabit Ethernet cards based on the Solarflare EF100 networking IP in Xilinx FPGAs. To compile this driver as a module, choose M here. The module will be called sfc. config SFC_MTD bool "Solarflare SFC9000/SFC9100-family MTD support" depends on SFC && MTD && !(SFC=y && MTD=m) default y help This exposes the on-board flash and/or EEPROM as MTD devices (e.g. /dev/mtd1). This is required to update the firmware or the boot configuration under Linux. config SFC_MCDI_MON bool "Solarflare SFC9000/SFC9100-family hwmon support" depends on SFC && HWMON && !(SFC=y && HWMON=m) default y help This exposes the on-board firmware-managed sensors as a hardware monitor device. config SFC_SRIOV bool "Solarflare SFC9000-family SR-IOV support" depends on SFC && PCI_IOV default y help This enables support for the SFC9000 I/O Virtualization features, allowing accelerated network performance in virtualized environments. config SFC_MCDI_LOGGING bool "Solarflare SFC9000/SFC9100-family MCDI logging support" depends on SFC default y help This enables support for tracing of MCDI (Management-Controller-to- Driver-Interface) commands and responses, allowing debugging of driver/firmware interaction. The tracing is actually enabled by a sysfs file 'mcdi_logging' under the PCI device. source "drivers/net/ethernet/sfc/falcon/Kconfig" endif # NET_VENDOR_SOLARFLARE PK ! A��H4 4 sfc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 sfc-y += efx.o efx_common.o efx_channels.o nic.o \ farch.o siena.o ef10.o \ tx.o tx_common.o tx_tso.o rx.o rx_common.o \ selftest.o ethtool.o ethtool_common.o ptp.o \ mcdi.o mcdi_port.o mcdi_port_common.o \ mcdi_functions.o mcdi_filters.o mcdi_mon.o \ ef100.o ef100_nic.o ef100_netdev.o \ ef100_ethtool.o ef100_rx.o ef100_tx.o sfc-$(CONFIG_SFC_MTD) += mtd.o sfc-$(CONFIG_SFC_SRIOV) += sriov.o siena_sriov.o ef10_sriov.o obj-$(CONFIG_SFC) += sfc.o obj-$(CONFIG_SFC_FALCON) += falcon/ PK ! >O�� � sfc/falcon/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config SFC_FALCON tristate "Solarflare SFC4000 support" depends on PCI select MDIO select CRC32 select I2C select I2C_ALGOBIT help This driver supports 10-gigabit Ethernet cards based on the Solarflare SFC4000 controller. To compile this driver as a module, choose M here. The module will be called sfc-falcon. config SFC_FALCON_MTD bool "Solarflare SFC4000 MTD support" depends on SFC_FALCON && MTD && !(SFC_FALCON=y && MTD=m) default y help This exposes the on-board flash and/or EEPROM as MTD devices (e.g. /dev/mtd1). This is required to update the boot configuration under Linux. PK ! ���X sfc/falcon/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 sfc-falcon-y += efx.o nic.o farch.o falcon.o tx.o rx.o selftest.o \ ethtool.o qt202x_phy.o mdio_10g.o tenxpress.o \ txc43128_phy.o falcon_boards.o sfc-falcon-$(CONFIG_SFC_FALCON_MTD) += mtd.o obj-$(CONFIG_SFC_FALCON) += sfc-falcon.o PK ! �l_9 agere/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Agere device configuration # config NET_VENDOR_AGERE bool "Agere devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Agere devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_AGERE config ET131X tristate "Agere ET-1310 Gigabit Ethernet support" depends on PCI select PHYLIB select CRC32 help This driver supports Agere ET-1310 ethernet adapters. To compile this driver as a module, choose M here. The module will be called et131x. endif # NET_VENDOR_AGERE PK ! hb agere/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Agere ET-131x ethernet driver # obj-$(CONFIG_ET131X) += et131x.o PK ! |�i_E E freescale/dpaa2/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FSL_DPAA2_ETH tristate "Freescale DPAA2 Ethernet" depends on FSL_MC_BUS && FSL_MC_DPIO select PHYLINK select PCS_LYNX select FSL_XGMAC_MDIO select NET_DEVLINK help This is the DPAA2 Ethernet driver supporting Freescale SoCs with DPAA2 (DataPath Acceleration Architecture v2). The driver manages network objects discovered on the Freescale MC bus. if FSL_DPAA2_ETH config FSL_DPAA2_ETH_DCB bool "Data Center Bridging (DCB) Support" default n depends on DCB help Enable Priority-Based Flow Control (PFC) support for DPAA2 Ethernet devices. endif config FSL_DPAA2_PTP_CLOCK tristate "Freescale DPAA2 PTP Clock" depends on FSL_DPAA2_ETH && PTP_1588_CLOCK_QORIQ default y help This driver adds support for using the DPAA2 1588 timer module as a PTP clock. config FSL_DPAA2_SWITCH tristate "Freescale DPAA2 Ethernet Switch" depends on BRIDGE || BRIDGE=n depends on NET_SWITCHDEV help Driver for Freescale DPAA2 Ethernet Switch. This driver manages switch objects discovered on the Freeescale MC bus. PK ! �V%ɭ � freescale/dpaa2/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Freescale DPAA2 Ethernet controller # obj-$(CONFIG_FSL_DPAA2_ETH) += fsl-dpaa2-eth.o obj-$(CONFIG_FSL_DPAA2_PTP_CLOCK) += fsl-dpaa2-ptp.o obj-$(CONFIG_FSL_DPAA2_SWITCH) += fsl-dpaa2-switch.o fsl-dpaa2-eth-objs := dpaa2-eth.o dpaa2-ethtool.o dpni.o dpaa2-mac.o dpmac.o dpaa2-eth-devlink.o fsl-dpaa2-eth-${CONFIG_FSL_DPAA2_ETH_DCB} += dpaa2-eth-dcb.o fsl-dpaa2-eth-${CONFIG_DEBUG_FS} += dpaa2-eth-debugfs.o fsl-dpaa2-ptp-objs := dpaa2-ptp.o dprtc.o fsl-dpaa2-switch-objs := dpaa2-switch.o dpaa2-switch-ethtool.o dpsw.o dpaa2-switch-flower.o dpaa2-mac.o dpmac.o # Needed by the tracing framework CFLAGS_dpaa2-eth.o := -I$(src) PK ! D��<S S freescale/fman/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FSL_FMAN tristate "FMan support" depends on FSL_SOC || ARCH_LAYERSCAPE || COMPILE_TEST select GENERIC_ALLOCATOR select PHYLIB select CRC32 default n help Freescale Data-Path Acceleration Architecture Frame Manager (FMan) support config DPAA_ERRATUM_A050385 bool depends on ARM64 && FSL_DPAA default y help DPAA FMan erratum A050385 software workaround implementation: align buffers, data start, SG fragment length to avoid FMan DMA splits. FMAN DMA read or writes under heavy traffic load may cause FMAN internal resource leak thus stopping further packet processing. The FMAN internal queue can overflow when FMAN splits single read or write transactions into multiple smaller transactions such that more than 17 AXI transactions are in flight from FMAN to interconnect. When the FMAN internal queue overflows, it can stall further packet processing. The issue can occur with any one of the following three conditions: 1. FMAN AXI transaction crosses 4K address boundary (Errata A010022) 2. FMAN DMA address for an AXI transaction is not 16 byte aligned, i.e. the last 4 bits of an address are non-zero 3. Scatter Gather (SG) frames have more than one SG buffer in the SG list and any one of the buffers, except the last buffer in the SG list has data size that is not a multiple of 16 bytes, i.e., other than 16, 32, 48, 64, etc. With any one of the above three conditions present, there is likelihood of stalled FMAN packet processing, especially under stress with multiple ports injecting line-rate traffic. PK ! ~'�J� � freescale/fman/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 subdir-ccflags-y += -I$(srctree)/drivers/net/ethernet/freescale/fman obj-$(CONFIG_FSL_FMAN) += fsl_dpaa_fman.o obj-$(CONFIG_FSL_FMAN) += fsl_dpaa_fman_port.o obj-$(CONFIG_FSL_FMAN) += fsl_dpaa_mac.o fsl_dpaa_fman-objs := fman_muram.o fman.o fman_sp.o fman_keygen.o fsl_dpaa_fman_port-objs := fman_port.o fsl_dpaa_mac-objs:= mac.o fman_dtsec.o fman_memac.o fman_tgec.o PK ! ~^��n n freescale/enetc/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0 config FSL_ENETC tristate "ENETC PF driver" depends on PCI && PCI_MSI select FSL_ENETC_IERB select FSL_ENETC_MDIO select PHYLINK select PCS_LYNX select DIMLIB help This driver supports NXP ENETC gigabit ethernet controller PCIe physical function (PF) devices, managing ENETC Ports at a privileged level. If compiled as module (M), the module name is fsl-enetc. config FSL_ENETC_VF tristate "ENETC VF driver" depends on PCI && PCI_MSI select FSL_ENETC_MDIO select PHYLINK select DIMLIB help This driver supports NXP ENETC gigabit ethernet controller PCIe virtual function (VF) devices enabled by the ENETC PF driver. If compiled as module (M), the module name is fsl-enetc-vf. config FSL_ENETC_IERB tristate "ENETC IERB driver" help This driver configures the Integrated Endpoint Register Block on NXP LS1028A. If compiled as module (M), the module name is fsl-enetc-ierb. config FSL_ENETC_MDIO tristate "ENETC MDIO driver" depends on PCI && MDIO_DEVRES && MDIO_BUS help This driver supports NXP ENETC Central MDIO controller as a PCIe physical function (PF) device. If compiled as module (M), the module name is fsl-enetc-mdio. config FSL_ENETC_PTP_CLOCK tristate "ENETC PTP clock driver" depends on PTP_1588_CLOCK_QORIQ && (FSL_ENETC || FSL_ENETC_VF) default y help This driver adds support for using the ENETC 1588 timer as a PTP clock. This clock is only useful if your PTP programs are getting hardware time stamps on the PTP Ethernet packets using the SO_TIMESTAMPING API. If compiled as module (M), the module name is fsl-enetc-ptp. config FSL_ENETC_QOS bool "ENETC hardware Time-sensitive Network support" depends on (FSL_ENETC || FSL_ENETC_VF) && (NET_SCH_TAPRIO || NET_SCH_CBS) help There are Time-Sensitive Network(TSN) capabilities(802.1Qbv/802.1Qci /802.1Qbu etc.) supported by ENETC. These TSN capabilities can be set enable/disable from user space via Qos commands(tc). In the kernel side, it can be loaded by Qos driver. Currently, it is only support taprio(802.1Qbv) and Credit Based Shaper(802.1Qbu). PK ! +��k k freescale/enetc/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 common-objs := enetc.o enetc_cbdr.o enetc_ethtool.o obj-$(CONFIG_FSL_ENETC) += fsl-enetc.o fsl-enetc-y := enetc_pf.o $(common-objs) fsl-enetc-$(CONFIG_PCI_IOV) += enetc_msg.o fsl-enetc-$(CONFIG_FSL_ENETC_QOS) += enetc_qos.o obj-$(CONFIG_FSL_ENETC_VF) += fsl-enetc-vf.o fsl-enetc-vf-y := enetc_vf.o $(common-objs) obj-$(CONFIG_FSL_ENETC_IERB) += fsl-enetc-ierb.o fsl-enetc-ierb-y := enetc_ierb.o obj-$(CONFIG_FSL_ENETC_MDIO) += fsl-enetc-mdio.o fsl-enetc-mdio-y := enetc_pci_mdio.o enetc_mdio.o obj-$(CONFIG_FSL_ENETC_PTP_CLOCK) += fsl-enetc-ptp.o fsl-enetc-ptp-y := enetc_ptp.o PK ! �h��k k freescale/fs_enet/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only config FS_ENET tristate "Freescale Ethernet Driver" depends on NET_VENDOR_FREESCALE && (CPM1 || CPM2 || PPC_MPC512x) select MII select PHYLIB config FS_ENET_MPC5121_FEC def_bool y if (FS_ENET && PPC_MPC512x) select FS_ENET_HAS_FEC config FS_ENET_HAS_SCC bool "Chip has an SCC usable for ethernet" depends on FS_ENET && (CPM1 || CPM2) default y config FS_ENET_HAS_FCC bool "Chip has an FCC usable for ethernet" depends on FS_ENET && CPM2 default y config FS_ENET_HAS_FEC bool "Chip has an FEC usable for ethernet" depends on FS_ENET && (CPM1 || FS_ENET_MPC5121_FEC) select FS_ENET_MDIO_FEC default y config FS_ENET_MDIO_FEC tristate "MDIO driver for FEC" depends on FS_ENET && (CPM1 || FS_ENET_MPC5121_FEC) config FS_ENET_MDIO_FCC tristate "MDIO driver for FCC" depends on FS_ENET && CPM2 select MDIO_BITBANG PK ! Vd� � freescale/fs_enet/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Freescale Ethernet controllers # obj-$(CONFIG_FS_ENET) += fs_enet.o fs_enet-$(CONFIG_FS_ENET_HAS_SCC) += mac-scc.o fs_enet-$(CONFIG_FS_ENET_HAS_FEC) += mac-fec.o fs_enet-$(CONFIG_FS_ENET_HAS_FCC) += mac-fcc.o obj-$(CONFIG_FS_ENET_MDIO_FEC) += mii-fec.o obj-$(CONFIG_FS_ENET_MDIO_FCC) += mii-bitbang.o fs_enet-objs := fs_enet-main.o $(fs_enet-m) PK ! B��ן � freescale/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Freescale device configuration # config NET_VENDOR_FREESCALE bool "Freescale devices" default y depends on FSL_SOC || QUICC_ENGINE || CPM1 || CPM2 || PPC_MPC512x || \ M523x || M527x || M5272 || M528x || M520x || M532x || \ ARCH_MXC || ARCH_MXS || (PPC_MPC52xx && PPC_BESTCOMM) || \ ARCH_LAYERSCAPE || COMPILE_TEST help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Freescale devices. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_FREESCALE config FEC tristate "FEC ethernet controller (of ColdFire and some i.MX CPUs)" depends on (M523x || M527x || M5272 || M528x || M520x || M532x || \ ARCH_MXC || SOC_IMX28 || COMPILE_TEST) default ARCH_MXC || SOC_IMX28 if ARM depends on PTP_1588_CLOCK_OPTIONAL select CRC32 select PHYLIB imply NET_SELFTESTS help Say Y here if you want to use the built-in 10/100 Fast ethernet controller on some Motorola ColdFire and Freescale i.MX processors. config FEC_MPC52xx tristate "FEC MPC52xx driver" depends on PPC_MPC52xx && PPC_BESTCOMM select CRC32 select PHYLIB select PPC_BESTCOMM_FEC help This option enables support for the MPC5200's on-chip Fast Ethernet Controller If compiled as module, it will be called fec_mpc52xx. config FEC_MPC52xx_MDIO bool "FEC MPC52xx MDIO bus driver" depends on FEC_MPC52xx default y help The MPC5200's FEC can connect to the Ethernet either with an external MII PHY chip or 10 Mbps 7-wire interface (Motorola? industry standard). If your board uses an external PHY connected to FEC, enable this. If not sure, enable. If compiled as module, it will be called fec_mpc52xx_phy. source "drivers/net/ethernet/freescale/fs_enet/Kconfig" source "drivers/net/ethernet/freescale/fman/Kconfig" config FSL_PQ_MDIO tristate "Freescale PQ MDIO" select PHYLIB help This driver supports the MDIO bus used by the gianfar and UCC drivers. config FSL_XGMAC_MDIO tristate "Freescale XGMAC MDIO" select PHYLIB depends on OF select OF_MDIO help This driver supports the MDIO bus on the Fman 10G Ethernet MACs, and on the FMan mEMAC (which supports both Clauses 22 and 45) config UCC_GETH tristate "Freescale QE Gigabit Ethernet" depends on QUICC_ENGINE && PPC32 select FSL_PQ_MDIO select PHYLIB select FIXED_PHY help This driver supports the Gigabit Ethernet mode of the QUICC Engine, which is available on some Freescale SOCs. config UGETH_TX_ON_DEMAND bool "Transmit on Demand support" depends on UCC_GETH config GIANFAR tristate "Gianfar Ethernet" depends on HAS_DMA select FSL_PQ_MDIO select PHYLIB select FIXED_PHY select CRC32 help This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, and MPC86xx family of chips, the eTSEC on LS1021A and the FEC on the 8540. source "drivers/net/ethernet/freescale/dpaa/Kconfig" source "drivers/net/ethernet/freescale/dpaa2/Kconfig" source "drivers/net/ethernet/freescale/enetc/Kconfig" endif # NET_VENDOR_FREESCALE PK ! F��� � freescale/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Freescale network device drivers. # obj-$(CONFIG_FEC) += fec.o fec-objs :=fec_main.o fec_ptp.o obj-$(CONFIG_FEC_MPC52xx) += fec_mpc52xx.o ifeq ($(CONFIG_FEC_MPC52xx_MDIO),y) obj-$(CONFIG_FEC_MPC52xx) += fec_mpc52xx_phy.o endif obj-$(CONFIG_FS_ENET) += fs_enet/ obj-$(CONFIG_FSL_PQ_MDIO) += fsl_pq_mdio.o obj-$(CONFIG_FSL_XGMAC_MDIO) += xgmac_mdio.o obj-$(CONFIG_GIANFAR) += gianfar_driver.o gianfar_driver-objs := gianfar.o \ gianfar_ethtool.o obj-$(CONFIG_UCC_GETH) += ucc_geth_driver.o ucc_geth_driver-objs := ucc_geth.o ucc_geth_ethtool.o obj-$(CONFIG_FSL_FMAN) += fman/ obj-$(CONFIG_FSL_DPAA_ETH) += dpaa/ obj-$(CONFIG_FSL_DPAA2_ETH) += dpaa2/ obj-y += enetc/ PK ! ��=` ` freescale/dpaa/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only menuconfig FSL_DPAA_ETH tristate "DPAA Ethernet" depends on FSL_DPAA && FSL_FMAN select PHYLIB select FIXED_PHY help Data Path Acceleration Architecture Ethernet driver, supporting the Freescale QorIQ chips. Depends on Freescale Buffer Manager and Queue Manager driver and Frame Manager Driver. PK ! �RvM M freescale/dpaa/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0 # # Makefile for the Freescale DPAA Ethernet controllers # # Include FMan headers FMAN = $(srctree)/drivers/net/ethernet/freescale/fman ccflags-y += -I$(FMAN) obj-$(CONFIG_FSL_DPAA_ETH) += fsl_dpa.o fsl_dpa-objs += dpaa_eth.o dpaa_ethtool.o dpaa_eth_sysfs.o CFLAGS_dpaa_eth.o := -I$(src) PK ! c �V� � tehuti/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Tehuti network device configuration # config NET_VENDOR_TEHUTI bool "Tehuti devices" default y depends on PCI help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Tehuti cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_TEHUTI config TEHUTI tristate "Tehuti Networks 10G Ethernet" depends on PCI help Tehuti Networks 10G Ethernet NIC endif # NET_VENDOR_TEHUTI PK ! �^�ŀ � tehuti/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Tehuti network device drivers. # obj-$(CONFIG_TEHUTI) += tehuti.o PK ! �Gx�- - tundra/Kconfignu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Tundra network device configuration # config NET_VENDOR_TUNDRA bool "Tundra devices" default y depends on TSI108_BRIDGE help If you have a network (Ethernet) card belonging to this class, say Y. Note that the answer to this question doesn't directly affect the kernel: saying N will just cause the configurator to skip all the questions about Tundra cards. If you say Y, you will be asked for your specific card in the following questions. if NET_VENDOR_TUNDRA config TSI108_ETH tristate "Tundra TSI108 gigabit Ethernet support" depends on TSI108_BRIDGE help This driver supports Tundra TSI108 gigabit Ethernet ports. To compile this driver as a module, choose M here: the module will be called tsi108_eth. endif # NET_VENDOR_TUNDRA PK ! @XI6� � tundra/Makefilenu �[��� # SPDX-License-Identifier: GPL-2.0-only # # Makefile for the Tundra network device drivers. # obj-$(CONFIG_TSI108_ETH) += tsi108_eth.o PK ! �L��! ! aeroflex/Kconfignu �[��� PK ! (wm� � a aeroflex/Makefilenu �[��� PK ! v�$q; ; * ni/Kconfignu �[��� PK ! �T=)X X � ni/Makefilenu �[��� PK ! r�}�, , 2 litex/Kconfignu �[��� PK ! Р �e e � litex/Makefilenu �[��� PK ! ��e� � > silan/Kconfignu �[��� PK ! t�|� � silan/Makefilenu �[��� PK ! �c�{� � � natsemi/Kconfignu �[��� PK ! �,6�( ( � natsemi/Makefilenu �[��� PK ! �J�@ @ micrel/Kconfignu �[��� PK ! =�� � micrel/Makefilenu �[��� PK ! ��,e� � � sun/Kconfignu �[��� PK ! i#ϑ � �- sun/Makefilenu �[��� PK ! �q�� � m/ cisco/enic/Kconfignu �[��� PK ! �� �� � �0 cisco/enic/Makefilenu �[��� PK ! �G�D D �1 cisco/Kconfignu �[��� PK ! ԏ:�r r 04 cisco/Makefilenu �[��� PK ! w,�2 2 �4 moxa/Kconfignu �[��� PK ! ��ڭ� � N8 moxa/Makefilenu �[��� PK ! ����D D 9 intel/ice/Makefilenu �[��� PK ! '���� � �< intel/e1000/Makefilenu �[��� PK ! &��' �= intel/igbvf/Makefilenu �[��� PK ! ���9# # !? intel/i40e/Makefilenu �[��� PK ! ��$%/ / �A intel/igc/Makefilenu �[��� PK ! �Iz� � �B intel/ixgb/Makefilenu �[��� PK ! v7ta� � .D intel/iavf/Makefilenu �[��� PK ! ( ��E E F intel/ixgbevf/Makefilenu �[��� PK ! ���{D D �G intel/igb/Makefilenu �[��� PK ! ��M. . I intel/e1000e/Makefilenu �[��� PK ! 7�;6, 6, �J intel/Kconfignu �[��� PK ! ��� � �v intel/Makefilenu �[��� PK ! ɭ w� � y intel/fm10k/Makefilenu �[��� PK ! ��w� � { intel/ixgbe/Makefilenu �[��� PK ! ��� � +~ mediatek/Kconfignu �[��� PK ! M�z+- - � mediatek/Makefilenu �[��� PK ! �-<O� � �� hisilicon/hns/Makefilenu �[��� PK ! ��:�� � P� hisilicon/hns3/Makefilenu �[��� PK ! �B� � {� hisilicon/Kconfignu �[��� PK ! ���5 5 o� hisilicon/Makefilenu �[��� PK ! 9Y��� � � neterion/vxge/Makefilenu �[��� PK ! w' � � � neterion/Kconfignu �[��� PK ! ���A� � � neterion/Makefilenu �[��� PK ! ���=X X ܤ emulex/benet/Kconfignu �[��� PK ! ��� � x� emulex/benet/Makefilenu �[��� PK ! C��LL L �� emulex/Kconfignu �[��� PK ! 0���v v � emulex/Makefilenu �[��� PK ! �� *7 7 ʮ qualcomm/emac/Makefilenu �[��� PK ! � o�j j G� qualcomm/Kconfignu �[��� PK ! 9�n� � � qualcomm/rmnet/Kconfignu �[��� PK ! 4��� � �� qualcomm/rmnet/Makefilenu �[��� PK ! ���SK K � qualcomm/Makefilenu �[��� PK ! r[�Kv v �� synopsys/Kconfignu �[��� PK ! FI�; ; C� synopsys/Makefilenu �[��� PK ! f���J J �� alteon/Kconfignu �[��� PK ! �_{� � G� alteon/Makefilenu �[��� PK ! :B�W W � pensando/ionic/Makefilenu �[��� PK ! Y �� �� pensando/Kconfignu �[��� PK ! ����z z �� pensando/Makefilenu �[��� PK ! q�$ $ �� calxeda/Kconfignu �[��� PK ! a��S S � calxeda/Makefilenu �[��� PK ! q"�#c c �� microchip/sparx5/Kconfignu �[��� PK ! ߅��g g N� microchip/sparx5/Makefilenu �[��� PK ! ���� �� microchip/Kconfignu �[��� PK ! ۲�O O [� microchip/Makefilenu �[��� PK ! {��� � �� samsung/sxgbe/Makefilenu �[��� PK ! ��� � #� samsung/Kconfignu �[��� PK ! �+��� � � samsung/Makefilenu �[��� PK ! �c4� � �� toshiba/Kconfignu �[��� PK ! �ˉLt t �� toshiba/Makefilenu �[��� PK ! }�n \� realtek/Kconfignu �[��� PK ! �:�� �� realtek/Makefilenu �[��� PK ! �h�s� � � mellanox/mlxsw/Kconfignu �[��� PK ! %�� � � mellanox/mlxsw/Makefilenu �[��� PK ! �Z_� � mellanox/mlxbf_gige/Kconfignu �[��� PK ! � �� � � mellanox/mlxbf_gige/Makefilenu �[��� PK ! ��� < mellanox/mlx4/Kconfignu �[��� PK ! �F<�� � � mellanox/mlx4/Makefilenu �[��� PK ! �?�w w � mellanox/mlxfw/Kconfignu �[��� PK ! ��JL� � k mellanox/mlxfw/Makefilenu �[��� PK ! r1��J J 8 mellanox/Kconfignu �[��� PK ! 4Q:� � mellanox/Makefilenu �[��� PK ! �l�x x mellanox/mlx5/core/Kconfignu �[��� PK ! ߥȋ\ \ �> mellanox/mlx5/core/Makefilenu �[��� PK ! ��l�H H uN mellanox/mlx5/core/esw/Makefilenu �[��� PK ! ��l�H H $ O mellanox/mlx5/core/steering/Makefilenu �[��� PK ! �FX@ @ �O fujitsu/Kconfignu �[��� PK ! [З;� � 'S fujitsu/Makefilenu �[��� PK ! �w�þ � �S google/gve/Makefilenu �[��� PK ! .��� � �T google/Kconfignu �[��� PK ! NufQ Q "X google/Makefilenu �[��� PK ! ����* * �X mscc/Kconfignu �[��� PK ! �R�;� � ] mscc/Makefilenu �[��� PK ! ^��Y� � �^ atheros/atl1e/Makefilenu �[��� PK ! ��e e �_ atheros/alx/Makefilenu �[��� PK ! l�} } r` atheros/atl1c/Makefilenu �[��� PK ! �_E!3 3 5a atheros/Kconfignu �[��� PK ! �7�� �j atheros/Makefilenu �[��� PK ! ���c c �k atheros/atlx/Makefilenu �[��� PK ! �+zD{ { �l amd/xgbe/Makefilenu �[��� PK ! �W�}! ! Un amd/Kconfignu �[��� PK ! ��lX� � �� amd/Makefilenu �[��� PK ! ��.� � y� netronome/nfp/Makefilenu �[��� PK ! S�nV �� netronome/Kconfignu �[��� PK ! FN�{ { � netronome/Makefilenu �[��� PK ! *�f[� � ז seeq/Kconfignu �[��� PK ! ��oS� � ښ seeq/Makefilenu �[��� PK ! ,C�{ { �� microsoft/Kconfignu �[��� PK ! n��Pe e w� microsoft/Makefilenu �[��� PK ! ����� � � microsoft/mana/Makefilenu �[��� PK ! �p6 I� 3com/Kconfignu �[��� PK ! �6O) ) �� 3com/Makefilenu �[��� PK ! � �� � �� apple/Kconfignu �[��� PK ! t��(� � �� apple/Makefilenu �[��� PK ! �ڛ� � rocker/Kconfignu �[��� PK ! �y�j� � 7� rocker/Makefilenu �[��� PK ! �,��; ; ,� altera/Kconfignu �[��� PK ! d#a�� � �� altera/Makefilenu �[��� PK ! ��P�� � ο 8390/Kconfignu �[��� PK ! #�� � �� 8390/Makefilenu �[��� PK ! ܳ��d d �� rdc/Kconfignu �[��� PK ! _C�{ { #� rdc/Makefilenu �[��� PK ! �0��� � �� actions/Kconfignu �[��� PK ! �t$�� � �� actions/Makefilenu �[��� PK ! �w�f f z� via/Kconfignu �[��� PK ! Ũ � � via/Makefilenu �[��� PK ! ;�p p �� dec/Kconfignu �[��� PK ! ˙�ڑ � �� dec/Makefilenu �[��� PK ! �5N_ _ w� dec/tulip/Kconfignu �[��� PK ! ��� dec/tulip/Makefilenu �[��� PK ! ���N: : s arc/Kconfignu �[��� PK ! �:o � arc/Makefilenu �[��� PK ! "iZ� � ' ibm/ehea/Makefilenu �[��� PK ! ��)�� � 5 ibm/emac/Kconfignu �[��� PK ! ��:�' ' ibm/emac/Makefilenu �[��� PK ! ^�m m i ibm/Kconfignu �[��� PK ! �.�� � ibm/Makefilenu �[��� PK ! Pl� * ezchip/Kconfignu �[��� PK ! �Y#_ _ � ezchip/Makefilenu �[��� PK ! ^��{ { ! broadcom/genet/Makefilenu �[��� PK ! ���F F �! broadcom/bnxt/Makefilenu �[��� PK ! �д) l# broadcom/Kconfignu �[��� PK ! �7� � �? broadcom/Makefilenu �[��� PK ! J:��2 2 �B broadcom/bnx2x/Makefilenu �[��� PK ! �5K� � ID ti/Kconfignu �[��� PK ! ��5 5 2\ ti/Makefilenu �[��� PK ! �=�2h h �a wiznet/Kconfignu �[��� PK ! �(� � Hl wiznet/Makefilenu �[��� PK ! gB�V` ` )m myricom/Kconfignu �[��� PK ! w�fȄ � �r myricom/Makefilenu �[��� PK ! ��[�� � �s myricom/myri10ge/Makefilenu �[��� PK ! |U]�� � [t huawei/hinic/Kconfignu �[��� PK ! �斁 � %v huawei/hinic/Makefilenu �[��� PK ! �; a; ; �w huawei/Kconfignu �[��� PK ! E��Tu u dz huawei/Makefilenu �[��� PK ! ��_&s s { allwinner/Kconfignu �[��� PK ! �K�"� � �~ allwinner/Makefilenu �[��� PK ! �[t� � � apm/xgene/Kconfignu �[��� PK ! �QՏ" " R� apm/xgene/Makefilenu �[��� PK ! �=�� � �� apm/xgene-v2/Kconfignu �[��� PK ! ����� � �� apm/xgene-v2/Makefilenu �[��� PK ! ;t�G� � �� apm/Kconfignu �[��� PK ! G�FJ� � d� apm/Makefilenu �[��� PK ! (; � � B� socionext/Kconfignu �[��� PK ! �q� � � socionext/Makefilenu �[��� PK ! ��b b �� nxp/Kconfignu �[��� PK ! �(H�L L �� nxp/Makefilenu �[��� PK ! 9�� � � renesas/Kconfignu �[��� PK ! b@ L� � �� renesas/Makefilenu �[��� PK ! ��>� � � xilinx/Kconfignu �[��� PK ! ��Y Y ؙ xilinx/Makefilenu �[��� PK ! ͗l l p� brocade/Kconfignu �[��� PK ! & �{ { � brocade/Makefilenu �[��� PK ! %}62� � ֞ brocade/bna/Kconfignu �[��� PK ! ֳ�e e � brocade/bna/Makefilenu �[��� PK ! m�W3 �� nvidia/Kconfignu �[��� PK ! 0�R�� � � nvidia/Makefilenu �[��� PK ! ��t2 2 Ŧ qlogic/netxen/Makefilenu �[��� PK ! %�� =� qlogic/qede/Makefilenu �[��� PK ! ���� �� qlogic/Kconfignu �[��� PK ! ���� � � qlogic/Makefilenu �[��� PK ! T��~� � � qlogic/qlcnic/Makefilenu �[��� PK ! �12 2 � qlogic/qed/Makefilenu �[��� PK ! x�j�n n �� aquantia/Kconfignu �[��� PK ! �(�{ { @� aquantia/Makefilenu �[��� PK ! 7ӕ�f f �� aquantia/atlantic/Makefilenu �[��� PK ! �3�� � �� amazon/ena/Makefilenu �[��� PK ! �0��( ( �� amazon/Kconfignu �[��� PK ! �Ö�� � $� amazon/Makefilenu �[��� PK ! �8�_ _ �� cavium/thunder/Makefilenu �[��� PK ! �+� - - �� cavium/liquidio/Makefilenu �[��� PK ! s�~�Q Q � cavium/common/Makefilenu �[��� PK ! �O � �� cavium/octeon/Makefilenu �[��� PK ! <'�� � p� cavium/Kconfignu �[��� PK ! ӊ�� }� cavium/Makefilenu �[��� PK ! �2qH H �� Kconfignu �[��� PK ! ���� � I� Makefilenu �[��� PK ! Z��~ ~ T smsc/Kconfignu �[��� PK ! m��6[ [ smsc/Makefilenu �[��� PK ! �S� � � cadence/Kconfignu �[��� PK ! ��P�� � � cadence/Makefilenu �[��� PK ! ���ӡ � � davicom/Kconfignu �[��� PK ! �߳>y y � davicom/Makefilenu �[��� PK ! i%��� � g! adaptec/Kconfignu �[��� PK ! A��� � �% adaptec/Makefilenu �[��� PK ! �%� � ]& packetengines/Kconfignu �[��� PK ! |�N]� � ", packetengines/Makefilenu �[��� PK ! ��V5 - pasemi/Kconfignu �[��� PK ! �)�� � Z0 pasemi/Makefilenu �[��� PK ! O]��C C d1 sgi/Kconfignu �[��� PK ! �W�a� � �4 sgi/Makefilenu �[��� PK ! �䴢 �5 sis/Kconfignu �[��� PK ! c�7B� � < sis/Makefilenu �[��� PK ! ��1� � �< faraday/Kconfignu �[��� PK ! �@� � #B faraday/Makefilenu �[��� PK ! �R.a a C xscale/Kconfignu �[��� PK ! `�� �H xscale/Makefilenu �[��� PK ! ��0� � �I marvell/octeontx2/nic/Makefilenu �[��� PK ! �J*� � L marvell/octeontx2/af/Makefilenu �[��� PK ! �s^�R R �M marvell/octeontx2/Kconfignu �[��� PK ! �.��� � �S marvell/octeontx2/Makefilenu �[��� PK ! ���d d �T marvell/Kconfignu �[��� PK ! &� � Ik marvell/mvpp2/Makefilenu �[��� PK ! nx'x� � gl marvell/Makefilenu �[��� PK ! ���� � 8n marvell/prestera/Kconfignu �[��� PK ! v�|(Y Y wq marvell/prestera/Makefilenu �[��� PK ! �|>� � s alacritech/Kconfignu �[��� PK ! �1`| | �v alacritech/Makefilenu �[��� PK ! ɨQy� � �w chelsio/libcxgb/Makefilenu �[��� PK ! ���� � ' �x chelsio/inline_crypto/ch_ipsec/Makefilenu �[��� PK ! ���]U U �y chelsio/inline_crypto/Kconfignu �[��� PK ! �� $ �� chelsio/inline_crypto/chtls/Makefilenu �[��� PK ! � �ߴ � � chelsio/inline_crypto/Makefilenu �[��� PK ! ��g� � & � chelsio/inline_crypto/ch_ktls/Makefilenu �[��� PK ! Q�O� � � chelsio/cxgb/Makefilenu �[��� PK ! [ %�y y *� chelsio/Kconfignu �[��� PK ! ��� F F � chelsio/Makefilenu �[��� PK ! ���� � h� chelsio/cxgb3/Makefilenu �[��� PK ! ���� � �� chelsio/cxgb4vf/Makefilenu �[��� PK ! �f�UJ J �� chelsio/cxgb4/Makefilenu �[��� PK ! ���h h � oki-semi/Kconfignu �[��� PK ! _�;�� � �� oki-semi/Makefilenu �[��� PK ! sK�� � }� oki-semi/pch_gbe/Kconfignu �[��� PK ! 4��� � o� oki-semi/pch_gbe/Makefilenu �[��� PK ! ����2 2 ]� cortina/Kconfignu �[��� PK ! �D�� � Φ cortina/Makefilenu �[��� PK ! " ��� � �� cirrus/Kconfignu �[��� PK ! �R�� � Я cirrus/Makefilenu �[��� PK ! x�* ۰ dlink/Kconfignu �[��� PK ! �jO�� � -� dlink/Makefilenu �[��� PK ! ���P P � stmicro/stmmac/Kconfignu �[��� PK ! �r#�0 0 �� stmicro/stmmac/Makefilenu �[��� PK ! BI_� � � stmicro/Kconfignu �[��� PK ! � z� � �� stmicro/Makefilenu �[��� PK ! h5{O@ @ �� i825xx/Kconfignu �[��� PK ! 3j)T T '� i825xx/Makefilenu �[��� PK ! �Z�,j j �� xircom/Kconfignu �[��� PK ! �Xw� � b� xircom/Makefilenu �[��� PK ! � � � -� sfc/Kconfignu �[��� PK ! A��H4 4 3� sfc/Makefilenu �[��� PK ! >O�� � �� sfc/falcon/Kconfignu �[��� PK ! ���X y� sfc/falcon/Makefilenu �[��� PK ! �l_9 � agere/Kconfignu �[��� PK ! hb 2 agere/Makefilenu �[��� PK ! |�i_E E � freescale/dpaa2/Kconfignu �[��� PK ! �V%ɭ � { freescale/dpaa2/Makefilenu �[��� PK ! D��<S S p freescale/fman/Kconfignu �[��� PK ! ~'�J� � freescale/fman/Makefilenu �[��� PK ! ~^��n n � freescale/enetc/Kconfignu �[��� PK ! +��k k � freescale/enetc/Makefilenu �[��� PK ! �h��k k N freescale/fs_enet/Kconfignu �[��� PK ! Vd� � $ freescale/fs_enet/Makefilenu �[��� PK ! B��ן � �% freescale/Kconfignu �[��� PK ! F��� � �2 freescale/Makefilenu �[��� PK ! ��=` ` �5 freescale/dpaa/Kconfignu �[��� PK ! �RvM M �7 freescale/dpaa/Makefilenu �[��� PK ! c �V� � 9 tehuti/Kconfignu �[��� PK ! �^�ŀ � �; tehuti/Makefilenu �[��� PK ! �Gx�- - �< tundra/Kconfignu �[��� PK ! @XI6� � @ tundra/Makefilenu �[��� PK <Y �@
| ver. 1.1 | |
.
| PHP 8.4.18 | Ð“ÐµÐ½ÐµÑ€Ð°Ñ†Ð¸Ñ Ñтраницы: 0.1 |
proxy
|
phpinfo
|
ÐаÑтройка