1# 2# Network device configuration 3# 4 5menuconfig NETDEVICES 6 default y if UML 7 depends on NET 8 bool "Network device support" 9 ---help--- 10 You can say N here if you don't intend to connect your Linux box to 11 any other computer at all. 12 13 You'll have to say Y if your computer contains a network card that 14 you want to use under Linux. If you are going to run SLIP or PPP over 15 telephone line or null modem cable you need say Y here. Connecting 16 two machines with parallel ports using PLIP needs this, as well as 17 AX.25/KISS for sending Internet traffic over amateur radio links. 18 19 See also "The Linux Network Administrator's Guide" by Olaf Kirch and 20 Terry Dawson. Available at <http://www.tldp.org/guides.html>. 21 22 If unsure, say Y. 23 24# All the following symbols are dependent on NETDEVICES - do not repeat 25# that for each of the symbols. 26if NETDEVICES 27 28config IFB 29 tristate "Intermediate Functional Block support" 30 depends on NET_CLS_ACT 31 ---help--- 32 This is an intermediate driver that allows sharing of 33 resources. 34 To compile this driver as a module, choose M here: the module 35 will be called ifb. If you want to use more than one ifb 36 device at a time, you need to compile this driver as a module. 37 Instead of 'ifb', the devices will then be called 'ifb0', 38 'ifb1' etc. 39 Look at the iproute2 documentation directory for usage etc 40 41config DUMMY 42 tristate "Dummy net driver support" 43 ---help--- 44 This is essentially a bit-bucket device (i.e. traffic you send to 45 this device is consigned into oblivion) with a configurable IP 46 address. It is most commonly used in order to make your currently 47 inactive SLIP address seem like a real address for local programs. 48 If you use SLIP or PPP, you might want to say Y here. Since this 49 thing often comes in handy, the default is Y. It won't enlarge your 50 kernel either. What a deal. Read about it in the Network 51 Administrator's Guide, available from 52 <http://www.tldp.org/docs.html#guide>. 53 54 To compile this driver as a module, choose M here: the module 55 will be called dummy. If you want to use more than one dummy 56 device at a time, you need to compile this driver as a module. 57 Instead of 'dummy', the devices will then be called 'dummy0', 58 'dummy1' etc. 59 60config BONDING 61 tristate "Bonding driver support" 62 depends on INET 63 depends on IPV6 || IPV6=n 64 ---help--- 65 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet 66 Channels together. This is called 'Etherchannel' by Cisco, 67 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux. 68 69 The driver supports multiple bonding modes to allow for both high 70 performance and high availability operation. 71 72 Refer to <file:Documentation/networking/bonding.txt> for more 73 information. 74 75 To compile this driver as a module, choose M here: the module 76 will be called bonding. 77 78config MACVLAN 79 tristate "MAC-VLAN support (EXPERIMENTAL)" 80 depends on EXPERIMENTAL 81 ---help--- 82 This allows one to create virtual interfaces that map packets to 83 or from specific MAC addresses to a particular interface. 84 85 Macvlan devices can be added using the "ip" command from the 86 iproute2 package starting with the iproute2-2.6.23 release: 87 88 "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan" 89 90 To compile this driver as a module, choose M here: the module 91 will be called macvlan. 92 93config EQUALIZER 94 tristate "EQL (serial line load balancing) support" 95 ---help--- 96 If you have two serial connections to some other computer (this 97 usually requires two modems and two telephone lines) and you use 98 SLIP (the protocol for sending Internet traffic over telephone 99 lines) or PPP (a better SLIP) on them, you can make them behave like 100 one double speed connection using this driver. Naturally, this has 101 to be supported at the other end as well, either with a similar EQL 102 Linux driver or with a Livingston Portmaster 2e. 103 104 Say Y if you want this and read 105 <file:Documentation/networking/eql.txt>. You may also want to read 106 section 6.2 of the NET-3-HOWTO, available from 107 <http://www.tldp.org/docs.html#howto>. 108 109 To compile this driver as a module, choose M here: the module 110 will be called eql. If unsure, say N. 111 112config TUN 113 tristate "Universal TUN/TAP device driver support" 114 select CRC32 115 ---help--- 116 TUN/TAP provides packet reception and transmission for user space 117 programs. It can be viewed as a simple Point-to-Point or Ethernet 118 device, which instead of receiving packets from a physical media, 119 receives them from user space program and instead of sending packets 120 via physical media writes them to the user space program. 121 122 When a program opens /dev/net/tun, driver creates and registers 123 corresponding net device tunX or tapX. After a program closed above 124 devices, driver will automatically delete tunXX or tapXX device and 125 all routes corresponding to it. 126 127 Please read <file:Documentation/networking/tuntap.txt> for more 128 information. 129 130 To compile this driver as a module, choose M here: the module 131 will be called tun. 132 133 If you don't know what to use this for, you don't need it. 134 135config VETH 136 tristate "Virtual ethernet pair device" 137 ---help--- 138 This device is a local ethernet tunnel. Devices are created in pairs. 139 When one end receives the packet it appears on its pair and vice 140 versa. 141 142config NET_SB1000 143 tristate "General Instruments Surfboard 1000" 144 depends on PNP 145 ---help--- 146 This is a driver for the General Instrument (also known as 147 NextLevel) SURFboard 1000 internal 148 cable modem. This is an ISA card which is used by a number of cable 149 TV companies to provide cable modem access. It's a one-way 150 downstream-only cable modem, meaning that your upstream net link is 151 provided by your regular phone modem. 152 153 At present this driver only compiles as a module, so say M here if 154 you have this card. The module will be called sb1000. Then read 155 <file:Documentation/networking/README.sb1000> for information on how 156 to use this module, as it needs special ppp scripts for establishing 157 a connection. Further documentation and the necessary scripts can be 158 found at: 159 160 <http://www.jacksonville.net/~fventuri/> 161 <http://home.adelphia.net/~siglercm/sb1000.html> 162 <http://linuxpower.cx/~cable/> 163 164 If you don't have this card, of course say N. 165 166source "drivers/net/arcnet/Kconfig" 167 168source "drivers/net/phy/Kconfig" 169 170# 171# Ethernet 172# 173 174menuconfig NET_ETHERNET 175 bool "Ethernet (10 or 100Mbit)" 176 depends on !UML 177 ---help--- 178 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 179 type of Local Area Network (LAN) in universities and companies. 180 181 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over 182 coaxial cable, linking computers in a chain), 10BASE-T or twisted 183 pair (10 Mbps over twisted pair cable, linking computers to central 184 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs), 185 100BASE-TX (100 Mbps over two twisted pair cables, using hubs), 186 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair 187 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links) 188 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit 189 Ethernet (1 Gbps over optical fiber or short copper links). 190 191 If your Linux machine will be connected to an Ethernet and you have 192 an Ethernet network interface card (NIC) installed in your computer, 193 say Y here and read the Ethernet-HOWTO, available from 194 <http://www.tldp.org/docs.html#howto>. You will then also have 195 to say Y to the driver for your particular NIC. 196 197 Note that the answer to this question won't directly affect the 198 kernel: saying N will just cause the configurator to skip all 199 the questions about Ethernet network cards. If unsure, say N. 200 201if NET_ETHERNET 202 203config MII 204 tristate "Generic Media Independent Interface device support" 205 help 206 Most ethernet controllers have MII transceiver either as an external 207 or internal device. It is safe to say Y or M here even if your 208 ethernet card lack MII. 209 210config MACB 211 tristate "Atmel MACB support" 212 depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91SAM9G20 || ARCH_AT91SAM9G45 || ARCH_AT91CAP9 213 select PHYLIB 214 help 215 The Atmel MACB ethernet interface is found on many AT32 and AT91 216 parts. Say Y to include support for the MACB chip. 217 218 To compile this driver as a module, choose M here: the module 219 will be called macb. 220 221source "drivers/net/arm/Kconfig" 222 223config AX88796 224 tristate "ASIX AX88796 NE2000 clone support" 225 depends on ARM || MIPS || SUPERH 226 select CRC32 227 select MII 228 help 229 AX88796 driver, using platform bus to provide 230 chip detection and resources 231 232config AX88796_93CX6 233 bool "ASIX AX88796 external 93CX6 eeprom support" 234 depends on AX88796 235 select EEPROM_93CX6 236 help 237 Select this if your platform comes with an external 93CX6 eeprom. 238 239config MACE 240 tristate "MACE (Power Mac ethernet) support" 241 depends on PPC_PMAC && PPC32 242 select CRC32 243 help 244 Power Macintoshes and clones with Ethernet built-in on the 245 motherboard will usually use a MACE (Medium Access Control for 246 Ethernet) interface. Say Y to include support for the MACE chip. 247 248 To compile this driver as a module, choose M here: the module 249 will be called mace. 250 251config MACE_AAUI_PORT 252 bool "Use AAUI port instead of TP by default" 253 depends on MACE 254 help 255 Some Apple machines (notably the Apple Network Server) which use the 256 MACE ethernet chip have an Apple AUI port (small 15-pin connector), 257 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say 258 Y here if you have such a machine. If unsure, say N. 259 The driver will default to AAUI on ANS anyway, and if you use it as 260 a module, you can provide the port_aaui=0|1 to force the driver. 261 262config BMAC 263 tristate "BMAC (G3 ethernet) support" 264 depends on PPC_PMAC && PPC32 265 select CRC32 266 help 267 Say Y for support of BMAC Ethernet interfaces. These are used on G3 268 computers. 269 270 To compile this driver as a module, choose M here: the module 271 will be called bmac. 272 273config ARIADNE 274 tristate "Ariadne support" 275 depends on ZORRO 276 help 277 If you have a Village Tronic Ariadne Ethernet adapter, say Y. 278 Otherwise, say N. 279 280 To compile this driver as a module, choose M here: the module 281 will be called ariadne. 282 283config A2065 284 tristate "A2065 support" 285 depends on ZORRO 286 select CRC32 287 help 288 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, 289 say N. 290 291 To compile this driver as a module, choose M here: the module 292 will be called a2065. 293 294config HYDRA 295 tristate "Hydra support" 296 depends on ZORRO 297 select CRC32 298 help 299 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. 300 301 To compile this driver as a module, choose M here: the module 302 will be called hydra. 303 304config ZORRO8390 305 tristate "Zorro NS8390-based Ethernet support" 306 depends on ZORRO 307 select CRC32 308 help 309 This driver is for Zorro Ethernet cards using an NS8390-compatible 310 chipset, like the Village Tronic Ariadne II and the Individual 311 Computers X-Surf Ethernet cards. If you have such a card, say Y. 312 Otherwise, say N. 313 314 To compile this driver as a module, choose M here: the module 315 will be called zorro8390. 316 317config APNE 318 tristate "PCMCIA NE2000 support" 319 depends on AMIGA_PCMCIA 320 select CRC32 321 help 322 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, 323 say N. 324 325 To compile this driver as a module, choose M here: the module 326 will be called apne. 327 328config MAC8390 329 bool "Macintosh NS 8390 based ethernet cards" 330 depends on MAC 331 select CRC32 332 help 333 If you want to include a driver to support Nubus or LC-PDS 334 Ethernet cards using an NS8390 chipset or its equivalent, say Y 335 and read the Ethernet-HOWTO, available from 336 <http://www.tldp.org/docs.html#howto>. 337 338config MAC89x0 339 tristate "Macintosh CS89x0 based ethernet cards" 340 depends on MAC 341 ---help--- 342 Support for CS89x0 chipset based Ethernet cards. If you have a 343 Nubus or LC-PDS network (Ethernet) card of this type, say Y and 344 read the Ethernet-HOWTO, available from 345 <http://www.tldp.org/docs.html#howto>. 346 347 To compile this driver as a module, choose M here. This module will 348 be called mac89x0. 349 350config MACSONIC 351 tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)" 352 depends on MAC 353 ---help--- 354 Support for NatSemi SONIC based Ethernet devices. This includes 355 the onboard Ethernet in many Quadras as well as some LC-PDS, 356 a few Nubus and all known Comm Slot Ethernet cards. If you have 357 one of these say Y and read the Ethernet-HOWTO, available from 358 <http://www.tldp.org/docs.html#howto>. 359 360 To compile this driver as a module, choose M here. This module will 361 be called macsonic. 362 363config MACMACE 364 bool "Macintosh (AV) onboard MACE ethernet" 365 depends on MAC 366 select CRC32 367 help 368 Support for the onboard AMD 79C940 MACE Ethernet controller used in 369 the 660AV and 840AV Macintosh. If you have one of these Macintoshes 370 say Y and read the Ethernet-HOWTO, available from 371 <http://www.tldp.org/docs.html#howto>. 372 373config MVME147_NET 374 tristate "MVME147 (Lance) Ethernet support" 375 depends on MVME147 376 select CRC32 377 help 378 Support for the on-board Ethernet interface on the Motorola MVME147 379 single-board computer. Say Y here to include the 380 driver for this chip in your kernel. 381 To compile this driver as a module, choose M here. 382 383config MVME16x_NET 384 tristate "MVME16x Ethernet support" 385 depends on MVME16x 386 help 387 This is the driver for the Ethernet interface on the Motorola 388 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the 389 driver for this chip in your kernel. 390 To compile this driver as a module, choose M here. 391 392config BVME6000_NET 393 tristate "BVME6000 Ethernet support" 394 depends on BVME6000 395 help 396 This is the driver for the Ethernet interface on BVME4000 and 397 BVME6000 VME boards. Say Y here to include the driver for this chip 398 in your kernel. 399 To compile this driver as a module, choose M here. 400 401config ATARILANCE 402 tristate "Atari Lance support" 403 depends on ATARI 404 help 405 Say Y to include support for several Atari Ethernet adapters based 406 on the AMD Lance chipset: RieblCard (with or without battery), or 407 PAMCard VME (also the version by Rhotron, with different addresses). 408 409config SUN3LANCE 410 tristate "Sun3/Sun3x on-board LANCE support" 411 depends on SUN3 || SUN3X 412 help 413 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80) 414 featured an AMD Lance 10Mbit Ethernet controller on board; say Y 415 here to compile in the Linux driver for this and enable Ethernet. 416 General Linux information on the Sun 3 and 3x series (now 417 discontinued) is at 418 <http://www.angelfire.com/ca2/tech68k/sun3.html>. 419 420 If you're not building a kernel for a Sun 3, say N. 421 422config SUN3_82586 423 bool "Sun3 on-board Intel 82586 support" 424 depends on SUN3 425 help 426 This driver enables support for the on-board Intel 82586 based 427 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note 428 that this driver does not support 82586-based adapters on additional 429 VME boards. 430 431config HPLANCE 432 bool "HP on-board LANCE support" 433 depends on DIO 434 select CRC32 435 help 436 If you want to use the builtin "LANCE" Ethernet controller on an 437 HP300 machine, say Y here. 438 439config LASI_82596 440 tristate "Lasi ethernet" 441 depends on GSC 442 help 443 Say Y here to support the builtin Intel 82596 ethernet controller 444 found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet. 445 446config SNI_82596 447 tristate "SNI RM ethernet" 448 depends on NET_ETHERNET && SNI_RM 449 help 450 Say Y here to support the on-board Intel 82596 ethernet controller 451 built into SNI RM machines. 452 453config KORINA 454 tristate "Korina (IDT RC32434) Ethernet support" 455 depends on NET_ETHERNET && MIKROTIK_RB532 456 help 457 If you have a Mikrotik RouterBoard 500 or IDT RC32434 458 based system say Y. Otherwise say N. 459 460config MIPS_JAZZ_SONIC 461 tristate "MIPS JAZZ onboard SONIC Ethernet support" 462 depends on MACH_JAZZ 463 help 464 This is the driver for the onboard card of MIPS Magnum 4000, 465 Acer PICA, Olivetti M700-10 and a few other identical OEM systems. 466 467config XTENSA_XT2000_SONIC 468 tristate "Xtensa XT2000 onboard SONIC Ethernet support" 469 depends on XTENSA_PLATFORM_XT2000 470 help 471 This is the driver for the onboard card of the Xtensa XT2000 board. 472 473config MIPS_AU1X00_ENET 474 bool "MIPS AU1000 Ethernet support" 475 depends on SOC_AU1X00 476 select PHYLIB 477 select CRC32 478 help 479 If you have an Alchemy Semi AU1X00 based system 480 say Y. Otherwise, say N. 481 482config SGI_IOC3_ETH 483 bool "SGI IOC3 Ethernet" 484 depends on PCI && SGI_IP27 485 select CRC32 486 select MII 487 help 488 If you have a network (Ethernet) card of this type, say Y and read 489 the Ethernet-HOWTO, available from 490 <http://www.tldp.org/docs.html#howto>. 491 492config MIPS_SIM_NET 493 tristate "MIPS simulator Network device" 494 depends on MIPS_SIM 495 help 496 The MIPSNET device is a simple Ethernet network device which is 497 emulated by the MIPS Simulator. 498 If you are not using a MIPSsim or are unsure, say N. 499 500config SGI_O2MACE_ETH 501 tristate "SGI O2 MACE Fast Ethernet support" 502 depends on SGI_IP32=y 503 504config STNIC 505 tristate "National DP83902AV support" 506 depends on SUPERH 507 select CRC32 508 help 509 Support for cards based on the National Semiconductor DP83902AV 510 ST-NIC Serial Network Interface Controller for Twisted Pair. This 511 is a 10Mbit/sec Ethernet controller. Product overview and specs at 512 <http://www.national.com/pf/DP/DP83902A.html>. 513 514 If unsure, say N. 515 516config SH_ETH 517 tristate "Renesas SuperH Ethernet support" 518 depends on SUPERH && \ 519 (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \ 520 CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \ 521 CPU_SUBTYPE_SH7724) 522 select CRC32 523 select MII 524 select MDIO_BITBANG 525 select PHYLIB 526 help 527 Renesas SuperH Ethernet device driver. 528 This driver support SH7710, SH7712, SH7763, SH7619, and SH7724. 529 530config SUNLANCE 531 tristate "Sun LANCE support" 532 depends on SBUS 533 select CRC32 534 help 535 This driver supports the "le" interface present on all 32-bit Sparc 536 systems, on some older Ultra systems and as an Sbus option. These 537 cards are based on the AMD Lance chipset, which is better known 538 via the NE2100 cards. 539 540 To compile this driver as a module, choose M here: the module 541 will be called sunlance. 542 543config HAPPYMEAL 544 tristate "Sun Happy Meal 10/100baseT support" 545 depends on SBUS || PCI 546 select CRC32 547 help 548 This driver supports the "hme" interface present on most Ultra 549 systems and as an option on older Sbus systems. This driver supports 550 both PCI and Sbus devices. This driver also supports the "qfe" quad 551 100baseT device available in both PCI and Sbus configurations. 552 553 To compile this driver as a module, choose M here: the module 554 will be called sunhme. 555 556config SUNBMAC 557 tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)" 558 depends on SBUS && EXPERIMENTAL 559 select CRC32 560 help 561 This driver supports the "be" interface available as an Sbus option. 562 This is Sun's older 100baseT Ethernet device. 563 564 To compile this driver as a module, choose M here: the module 565 will be called sunbmac. 566 567config SUNQE 568 tristate "Sun QuadEthernet support" 569 depends on SBUS 570 select CRC32 571 help 572 This driver supports the "qe" 10baseT Ethernet device, available as 573 an Sbus option. Note that this is not the same as Quad FastEthernet 574 "qfe" which is supported by the Happy Meal driver instead. 575 576 To compile this driver as a module, choose M here: the module 577 will be called sunqe. 578 579config SUNGEM 580 tristate "Sun GEM support" 581 depends on PCI 582 select CRC32 583 help 584 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also 585 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>. 586 587config CASSINI 588 tristate "Sun Cassini support" 589 depends on PCI 590 select CRC32 591 help 592 Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also 593 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf> 594 595config SUNVNET 596 tristate "Sun Virtual Network support" 597 depends on SUN_LDOMS 598 help 599 Support for virtual network devices under Sun Logical Domains. 600 601config NET_VENDOR_3COM 602 bool "3COM cards" 603 depends on ISA || EISA || MCA || PCI 604 help 605 If you have a network (Ethernet) card belonging to this class, say Y 606 and read the Ethernet-HOWTO, available from 607 <http://www.tldp.org/docs.html#howto>. 608 609 Note that the answer to this question doesn't directly affect the 610 kernel: saying N will just cause the configurator to skip all 611 the questions about 3COM cards. If you say Y, you will be asked for 612 your specific card in the following questions. 613 614config EL1 615 tristate "3c501 \"EtherLink\" support" 616 depends on NET_VENDOR_3COM && ISA 617 ---help--- 618 If you have a network (Ethernet) card of this type, say Y and read 619 the Ethernet-HOWTO, available from 620 <http://www.tldp.org/docs.html#howto>. Also, consider buying a 621 new card, since the 3c501 is slow, broken, and obsolete: you will 622 have problems. Some people suggest to ping ("man ping") a nearby 623 machine every minute ("man cron") when using this card. 624 625 To compile this driver as a module, choose M here. The module 626 will be called 3c501. 627 628config EL2 629 tristate "3c503 \"EtherLink II\" support" 630 depends on NET_VENDOR_3COM && ISA 631 select CRC32 632 help 633 If you have a network (Ethernet) card of this type, say Y and read 634 the Ethernet-HOWTO, available from 635 <http://www.tldp.org/docs.html#howto>. 636 637 To compile this driver as a module, choose M here. The module 638 will be called 3c503. 639 640config ELPLUS 641 tristate "3c505 \"EtherLink Plus\" support" 642 depends on NET_VENDOR_3COM && ISA && ISA_DMA_API 643 ---help--- 644 Information about this network (Ethernet) card can be found in 645 <file:Documentation/networking/3c505.txt>. If you have a card of 646 this type, say Y and read the Ethernet-HOWTO, available from 647 <http://www.tldp.org/docs.html#howto>. 648 649 To compile this driver as a module, choose M here. The module 650 will be called 3c505. 651 652config EL16 653 tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)" 654 depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL 655 help 656 If you have a network (Ethernet) card of this type, say Y and read 657 the Ethernet-HOWTO, available from 658 <http://www.tldp.org/docs.html#howto>. 659 660 To compile this driver as a module, choose M here. The module 661 will be called 3c507. 662 663config EL3 664 tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support" 665 depends on NET_VENDOR_3COM && (ISA || EISA || MCA) 666 ---help--- 667 If you have a network (Ethernet) card belonging to the 3Com 668 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available 669 from <http://www.tldp.org/docs.html#howto>. 670 671 If your card is not working you may need to use the DOS 672 setup disk to disable Plug & Play mode, and to select the default 673 media type. 674 675 To compile this driver as a module, choose M here. The module 676 will be called 3c509. 677 678config 3C515 679 tristate "3c515 ISA \"Fast EtherLink\"" 680 depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API 681 help 682 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet 683 network card, say Y and read the Ethernet-HOWTO, available from 684 <http://www.tldp.org/docs.html#howto>. 685 686 To compile this driver as a module, choose M here. The module 687 will be called 3c515. 688 689config ELMC 690 tristate "3c523 \"EtherLink/MC\" support" 691 depends on NET_VENDOR_3COM && MCA_LEGACY 692 help 693 If you have a network (Ethernet) card of this type, say Y and read 694 the Ethernet-HOWTO, available from 695 <http://www.tldp.org/docs.html#howto>. 696 697 To compile this driver as a module, choose M here. The module 698 will be called 3c523. 699 700config ELMC_II 701 tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)" 702 depends on NET_VENDOR_3COM && MCA && MCA_LEGACY 703 help 704 If you have a network (Ethernet) card of this type, say Y and read 705 the Ethernet-HOWTO, available from 706 <http://www.tldp.org/docs.html#howto>. 707 708 To compile this driver as a module, choose M here. The module 709 will be called 3c527. 710 711config VORTEX 712 tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support" 713 depends on NET_VENDOR_3COM && (PCI || EISA) 714 select MII 715 ---help--- 716 This option enables driver support for a large number of 10Mbps and 717 10/100Mbps EISA, PCI and PCMCIA 3Com network cards: 718 719 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI 720 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI 721 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus 722 "Tornado" (3c905) PCI 723 "Hurricane" (3c555/3cSOHO) PCI 724 725 If you have such a card, say Y and read the Ethernet-HOWTO, 726 available from <http://www.tldp.org/docs.html#howto>. More 727 specific information is in 728 <file:Documentation/networking/vortex.txt> and in the comments at 729 the beginning of <file:drivers/net/3c59x.c>. 730 731 To compile this support as a module, choose M here. 732 733config TYPHOON 734 tristate "3cr990 series \"Typhoon\" support" 735 depends on NET_VENDOR_3COM && PCI 736 select CRC32 737 ---help--- 738 This option enables driver support for the 3cr990 series of cards: 739 740 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97, 741 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server, 742 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR 743 744 If you have a network (Ethernet) card of this type, say Y and read 745 the Ethernet-HOWTO, available from 746 <http://www.tldp.org/docs.html#howto>. 747 748 To compile this driver as a module, choose M here. The module 749 will be called typhoon. 750 751config LANCE 752 tristate "AMD LANCE and PCnet (AT1500 and NE2100) support" 753 depends on ISA && ISA_DMA_API 754 help 755 If you have a network (Ethernet) card of this type, say Y and read 756 the Ethernet-HOWTO, available from 757 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are 758 of this type. 759 760 To compile this driver as a module, choose M here: the module 761 will be called lance. This is recommended. 762 763config NET_VENDOR_SMC 764 bool "Western Digital/SMC cards" 765 depends on ISA || MCA || EISA || MAC 766 help 767 If you have a network (Ethernet) card belonging to this class, say Y 768 and read the Ethernet-HOWTO, available from 769 <http://www.tldp.org/docs.html#howto>. 770 771 Note that the answer to this question doesn't directly affect the 772 kernel: saying N will just cause the configurator to skip all 773 the questions about Western Digital cards. If you say Y, you will be 774 asked for your specific card in the following questions. 775 776config WD80x3 777 tristate "WD80*3 support" 778 depends on NET_VENDOR_SMC && ISA 779 select CRC32 780 help 781 If you have a network (Ethernet) card of this type, say Y and read 782 the Ethernet-HOWTO, available from 783 <http://www.tldp.org/docs.html#howto>. 784 785 To compile this driver as a module, choose M here. The module 786 will be called wd. 787 788config ULTRAMCA 789 tristate "SMC Ultra MCA support" 790 depends on NET_VENDOR_SMC && MCA 791 select CRC32 792 help 793 If you have a network (Ethernet) card of this type and are running 794 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO, 795 available from <http://www.tldp.org/docs.html#howto>. 796 797 To compile this driver as a module, choose M here. The module 798 will be called smc-mca. 799 800config ULTRA 801 tristate "SMC Ultra support" 802 depends on NET_VENDOR_SMC && ISA 803 select CRC32 804 ---help--- 805 If you have a network (Ethernet) card of this type, say Y and read 806 the Ethernet-HOWTO, available from 807 <http://www.tldp.org/docs.html#howto>. 808 809 Important: There have been many reports that, with some motherboards 810 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible, 811 such as some BusLogic models) causes corruption problems with many 812 operating systems. The Linux smc-ultra driver has a work-around for 813 this but keep it in mind if you have such a SCSI card and have 814 problems. 815 816 To compile this driver as a module, choose M here. The module 817 will be called smc-ultra. 818 819config ULTRA32 820 tristate "SMC Ultra32 EISA support" 821 depends on NET_VENDOR_SMC && EISA 822 select CRC32 823 help 824 If you have a network (Ethernet) card of this type, say Y and read 825 the Ethernet-HOWTO, available from 826 <http://www.tldp.org/docs.html#howto>. 827 828 To compile this driver as a module, choose M here. The module 829 will be called smc-ultra32. 830 831config BFIN_MAC 832 tristate "Blackfin on-chip MAC support" 833 depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537) 834 select CRC32 835 select MII 836 select PHYLIB 837 select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE 838 help 839 This is the driver for Blackfin on-chip mac device. Say Y if you want it 840 compiled into the kernel. This driver is also available as a module 841 ( = code which can be inserted in and removed from the running kernel 842 whenever you want). The module will be called bfin_mac. 843 844config BFIN_MAC_USE_L1 845 bool "Use L1 memory for rx/tx packets" 846 depends on BFIN_MAC && (BF527 || BF537) 847 default y 848 help 849 To get maximum network performance, you should use L1 memory as rx/tx buffers. 850 Say N here if you want to reserve L1 memory for other uses. 851 852config BFIN_TX_DESC_NUM 853 int "Number of transmit buffer packets" 854 depends on BFIN_MAC 855 range 6 10 if BFIN_MAC_USE_L1 856 range 10 100 857 default "10" 858 help 859 Set the number of buffer packets used in driver. 860 861config BFIN_RX_DESC_NUM 862 int "Number of receive buffer packets" 863 depends on BFIN_MAC 864 range 20 100 if BFIN_MAC_USE_L1 865 range 20 800 866 default "20" 867 help 868 Set the number of buffer packets used in driver. 869 870config BFIN_MAC_RMII 871 bool "RMII PHY Interface (EXPERIMENTAL)" 872 depends on BFIN_MAC && EXPERIMENTAL 873 default y if BFIN527_EZKIT 874 default n if BFIN537_STAMP 875 help 876 Use Reduced PHY MII Interface 877 878config SMC9194 879 tristate "SMC 9194 support" 880 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN) 881 select CRC32 882 ---help--- 883 This is support for the SMC9xxx based Ethernet cards. Choose this 884 option if you have a DELL laptop with the docking station, or 885 another SMC9192/9194 based chipset. Say Y if you want it compiled 886 into the kernel, and read the file 887 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 888 available from <http://www.tldp.org/docs.html#howto>. 889 890 To compile this driver as a module, choose M here. The module 891 will be called smc9194. 892 893config SMC91X 894 tristate "SMC 91C9x/91C1xxx support" 895 select CRC32 896 select MII 897 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \ 898 MIPS || BLACKFIN || MN10300 899 help 900 This is a driver for SMC's 91x series of Ethernet chipsets, 901 including the SMC91C94 and the SMC91C111. Say Y if you want it 902 compiled into the kernel, and read the file 903 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 904 available from <http://www.linuxdoc.org/docs.html#howto>. 905 906 This driver is also available as a module ( = code which can be 907 inserted in and removed from the running kernel whenever you want). 908 The module will be called smc91x. If you want to compile it as a 909 module, say M here and read <file:Documentation/kbuild/modules.txt>. 910 911config NET_NETX 912 tristate "NetX Ethernet support" 913 select MII 914 depends on ARCH_NETX 915 help 916 This is support for the Hilscher netX builtin Ethernet ports 917 918 To compile this driver as a module, choose M here. The module 919 will be called netx-eth. 920 921config TI_DAVINCI_EMAC 922 tristate "TI DaVinci EMAC Support" 923 depends on ARM && ARCH_DAVINCI 924 select PHYLIB 925 help 926 This driver supports TI's DaVinci Ethernet . 927 928 To compile this driver as a module, choose M here: the module 929 will be called davinci_emac_driver. This is recommended. 930 931config DM9000 932 tristate "DM9000 support" 933 depends on ARM || BLACKFIN || MIPS 934 select CRC32 935 select MII 936 ---help--- 937 Support for DM9000 chipset. 938 939 To compile this driver as a module, choose M here. The module 940 will be called dm9000. 941 942config DM9000_DEBUGLEVEL 943 int "DM9000 maximum debug level" 944 depends on DM9000 945 default 4 946 help 947 The maximum level of debugging code compiled into the DM9000 948 driver. 949 950config DM9000_FORCE_SIMPLE_PHY_POLL 951 bool "Force simple NSR based PHY polling" 952 depends on DM9000 953 ---help--- 954 This configuration forces the DM9000 to use the NSR's LinkStatus 955 bit to determine if the link is up or down instead of the more 956 costly MII PHY reads. Note, this will not work if the chip is 957 operating with an external PHY. 958 959config ENC28J60 960 tristate "ENC28J60 support" 961 depends on EXPERIMENTAL && SPI && NET_ETHERNET 962 select CRC32 963 ---help--- 964 Support for the Microchip EN28J60 ethernet chip. 965 966 To compile this driver as a module, choose M here. The module will be 967 called enc28j60. 968 969config ENC28J60_WRITEVERIFY 970 bool "Enable write verify" 971 depends on ENC28J60 972 ---help--- 973 Enable the verify after the buffer write useful for debugging purpose. 974 If unsure, say N. 975 976config ETHOC 977 tristate "OpenCores 10/100 Mbps Ethernet MAC support" 978 depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA 979 select MII 980 select PHYLIB 981 select CRC32 982 select BITREVERSE 983 help 984 Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC. 985 986config SMC911X 987 tristate "SMSC LAN911[5678] support" 988 select CRC32 989 select MII 990 depends on ARM || SUPERH 991 help 992 This is a driver for SMSC's LAN911x series of Ethernet chipsets 993 including the new LAN9115, LAN9116, LAN9117, and LAN9118. 994 Say Y if you want it compiled into the kernel, 995 and read the Ethernet-HOWTO, available from 996 <http://www.linuxdoc.org/docs.html#howto>. 997 998 This driver is also available as a module. The module will be 999 called smc911x. If you want to compile it as a module, say M 1000 here and read <file:Documentation/kbuild/modules.txt>
1001 1002config SMSC911X 1003 tristate "SMSC LAN911x/LAN921x families embedded ethernet support" 1004 depends on ARM || SUPERH || BLACKFIN || MIPS 1005 select CRC32 1006 select MII 1007 select PHYLIB 1008 ---help--- 1009 Say Y here if you want support for SMSC LAN911x and LAN921x families 1010 of ethernet controllers. 1011 1012 To compile this driver as a module, choose M here and read 1013 <file:Documentation/networking/net-modules.txt>. The module 1014 will be called smsc911x. 1015 1016config NET_VENDOR_RACAL 1017 bool "Racal-Interlan (Micom) NI cards" 1018 depends on ISA 1019 help 1020 If you have a network (Ethernet) card belonging to this class, such 1021 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, 1022 available from <http://www.tldp.org/docs.html#howto>. 1023 1024 Note that the answer to this question doesn't directly affect the 1025 kernel: saying N will just cause the configurator to skip all 1026 the questions about NI cards. If you say Y, you will be asked for 1027 your specific card in the following questions. 1028 1029config NI5010 1030 tristate "NI5010 support (EXPERIMENTAL)" 1031 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP 1032 ---help--- 1033 If you have a network (Ethernet) card of this type, say Y and read 1034 the Ethernet-HOWTO, available from 1035 <http://www.tldp.org/docs.html#howto>. Note that this is still 1036 experimental code. 1037 1038 To compile this driver as a module, choose M here. The module 1039 will be called ni5010. 1040 1041config NI52 1042 tristate "NI5210 support" 1043 depends on NET_VENDOR_RACAL && ISA 1044 help 1045 If you have a network (Ethernet) card of this type, say Y and read 1046 the Ethernet-HOWTO, available from 1047 <http://www.tldp.org/docs.html#howto>. 1048 1049 To compile this driver as a module, choose M here. The module 1050 will be called ni52. 1051 1052config NI65 1053 tristate "NI6510 support" 1054 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API 1055 help 1056 If you have a network (Ethernet) card of this type, say Y and read 1057 the Ethernet-HOWTO, available from 1058 <http://www.tldp.org/docs.html#howto>. 1059 1060 To compile this driver as a module, choose M here. The module 1061 will be called ni65. 1062 1063config DNET 1064 tristate "Dave ethernet support (DNET)" 1065 depends on NET_ETHERNET && HAS_IOMEM 1066 select PHYLIB 1067 help 1068 The Dave ethernet interface (DNET) is found on Qong Board FPGA. 1069 Say Y to include support for the DNET chip. 1070 1071 To compile this driver as a module, choose M here: the module 1072 will be called dnet. 1073 1074source "drivers/net/tulip/Kconfig" 1075 1076config AT1700 1077 tristate "AT1700/1720 support (EXPERIMENTAL)" 1078 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL 1079 select CRC32 1080 ---help--- 1081 If you have a network (Ethernet) card of this type, say Y and read 1082 the Ethernet-HOWTO, available from 1083 <http://www.tldp.org/docs.html#howto>. 1084 1085 To compile this driver as a module, choose M here. The module 1086 will be called at1700. 1087 1088config DEPCA 1089 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" 1090 depends on ISA || EISA || MCA 1091 select CRC32 1092 ---help--- 1093 If you have a network (Ethernet) card of this type, say Y and read 1094 the Ethernet-HOWTO, available from 1095 <http://www.tldp.org/docs.html#howto> as well as 1096 <file:drivers/net/depca.c>. 1097 1098 To compile this driver as a module, choose M here. The module 1099 will be called depca. 1100 1101config HP100 1102 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" 1103 depends on ISA || EISA || PCI 1104 help 1105 If you have a network (Ethernet) card of this type, say Y and read 1106 the Ethernet-HOWTO, available from 1107 <http://www.tldp.org/docs.html#howto>. 1108 1109 To compile this driver as a module, choose M here. The module 1110 will be called hp100. 1111 1112config NET_ISA 1113 bool "Other ISA cards" 1114 depends on ISA 1115 ---help--- 1116 If your network (Ethernet) card hasn't been mentioned yet and its 1117 bus system (that's the way the cards talks to the other components 1118 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. 1119 Make sure you know the name of your card. Read the Ethernet-HOWTO, 1120 available from <http://www.tldp.org/docs.html#howto>. 1121 1122 If unsure, say Y. 1123 1124 Note that the answer to this question doesn't directly affect the 1125 kernel: saying N will just cause the configurator to skip all 1126 the remaining ISA network card questions. If you say Y, you will be 1127 asked for your specific card in the following questions. 1128 1129config E2100 1130 tristate "Cabletron E21xx support" 1131 depends on NET_ISA 1132 select CRC32 1133 help 1134 If you have a network (Ethernet) card of this type, say Y and read 1135 the Ethernet-HOWTO, available from 1136 <http://www.tldp.org/docs.html#howto>. 1137 1138 To compile this driver as a module, choose M here. The module 1139 will be called e2100. 1140 1141config EWRK3 1142 tristate "EtherWORKS 3 (DE203, DE204, DE205) support" 1143 depends on NET_ISA 1144 select CRC32 1145 ---help--- 1146 This driver supports the DE203, DE204 and DE205 network (Ethernet) 1147 cards. If this is for you, say Y and read 1148 <file:Documentation/networking/ewrk3.txt> in the kernel source as 1149 well as the Ethernet-HOWTO, available from 1150 <http://www.tldp.org/docs.html#howto>. 1151 1152 To compile this driver as a module, choose M here. The module 1153 will be called ewrk3. 1154 1155config EEXPRESS 1156 tristate "EtherExpress 16 support" 1157 depends on NET_ISA 1158 ---help--- 1159 If you have an EtherExpress16 network (Ethernet) card, say Y and 1160 read the Ethernet-HOWTO, available from 1161 <http://www.tldp.org/docs.html#howto>. Note that the Intel 1162 EtherExpress16 card used to be regarded as a very poor choice 1163 because the driver was very unreliable. We now have a new driver 1164 that should do better. 1165 1166 To compile this driver as a module, choose M here. The module 1167 will be called eexpress. 1168 1169config EEXPRESS_PRO 1170 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support" 1171 depends on NET_ISA 1172 ---help--- 1173 If you have a network (Ethernet) card of this type, say Y. This 1174 driver supports Intel i82595{FX,TX} based boards. Note however 1175 that the EtherExpress PRO/100 Ethernet card has its own separate 1176 driver. Please read the Ethernet-HOWTO, available from 1177 <http://www.tldp.org/docs.html#howto>. 1178 1179 To compile this driver as a module, choose M here. The module 1180 will be called eepro. 1181 1182config HPLAN_PLUS 1183 tristate "HP PCLAN+ (27247B and 27252A) support" 1184 depends on NET_ISA 1185 select CRC32 1186 help 1187 If you have a network (Ethernet) card of this type, say Y and read 1188 the Ethernet-HOWTO, available from 1189 <http://www.tldp.org/docs.html#howto>. 1190 1191 To compile this driver as a module, choose M here. The module 1192 will be called hp-plus. 1193 1194config HPLAN 1195 tristate "HP PCLAN (27245 and other 27xxx series) support" 1196 depends on NET_ISA 1197 select CRC32 1198 help 1199 If you have a network (Ethernet) card of this type, say Y and read 1200 the Ethernet-HOWTO, available from 1201 <http://www.tldp.org/docs.html#howto>. 1202 1203 To compile this driver as a module, choose M here. The module 1204 will be called hp. 1205 1206config LP486E 1207 tristate "LP486E on board Ethernet" 1208 depends on NET_ISA 1209 help 1210 Say Y here to support the 82596-based on-board Ethernet controller 1211 for the Panther motherboard, which is one of the two shipped in the 1212 Intel Professional Workstation. 1213 1214config ETH16I 1215 tristate "ICL EtherTeam 16i/32 support" 1216 depends on NET_ISA 1217 help 1218 If you have a network (Ethernet) card of this type, say Y and read 1219 the Ethernet-HOWTO, available from 1220 <http://www.tldp.org/docs.html#howto>. 1221 1222 To compile this driver as a module, choose M here. The module 1223 will be called eth16i. 1224 1225config NE2000 1226 tristate "NE2000/NE1000 support" 1227 depends on NET_ISA || (Q40 && m) || M32R || MACH_TX49XX 1228 select CRC32 1229 ---help--- 1230 If you have a network (Ethernet) card of this type, say Y and read 1231 the Ethernet-HOWTO, available from 1232 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards 1233 without a specific driver are compatible with NE2000. 1234 1235 If you have a PCI NE2000 card however, say N here and Y to "PCI 1236 NE2000 and clone support" under "EISA, VLB, PCI and on board 1237 controllers" below. If you have a NE2000 card and are running on 1238 an MCA system (a bus system used on some IBM PS/2 computers and 1239 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", 1240 below. 1241 1242 To compile this driver as a module, choose M here. The module 1243 will be called ne. 1244 1245config ZNET 1246 tristate "Zenith Z-Note support (EXPERIMENTAL)" 1247 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API 1248 help 1249 The Zenith Z-Note notebook computer has a built-in network 1250 (Ethernet) card, and this is the Linux driver for it. Note that the 1251 IBM Thinkpad 300 is compatible with the Z-Note and is also supported 1252 by this driver. Read the Ethernet-HOWTO, available from 1253 <http://www.tldp.org/docs.html#howto>. 1254 1255config SEEQ8005 1256 tristate "SEEQ8005 support (EXPERIMENTAL)" 1257 depends on NET_ISA && EXPERIMENTAL 1258 help 1259 This is a driver for the SEEQ 8005 network (Ethernet) card. If this 1260 is for you, read the Ethernet-HOWTO, available from 1261 <http://www.tldp.org/docs.html#howto>. 1262 1263 To compile this driver as a module, choose M here. The module 1264 will be called seeq8005. 1265 1266config NE2_MCA 1267 tristate "NE/2 (ne2000 MCA version) support" 1268 depends on MCA_LEGACY 1269 select CRC32 1270 help 1271 If you have a network (Ethernet) card of this type, say Y and read 1272 the Ethernet-HOWTO, available from 1273 <http://www.tldp.org/docs.html#howto>. 1274 1275 To compile this driver as a module, choose M here. The module 1276 will be called ne2. 1277 1278config IBMLANA 1279 tristate "IBM LAN Adapter/A support" 1280 depends on MCA 1281 ---help--- 1282 This is a Micro Channel Ethernet adapter. You need to set 1283 CONFIG_MCA to use this driver. It is both available as an in-kernel 1284 driver and as a module. 1285 1286 To compile this driver as a module, choose M here. The only 1287 currently supported card is the IBM LAN Adapter/A for Ethernet. It 1288 will both support 16K and 32K memory windows, however a 32K window 1289 gives a better security against packet losses. Usage of multiple 1290 boards with this driver should be possible, but has not been tested 1291 up to now due to lack of hardware. 1292 1293config IBMVETH 1294 tristate "IBM LAN Virtual Ethernet support" 1295 depends on PPC_PSERIES 1296 ---help--- 1297 This driver supports virtual ethernet adapters on newer IBM iSeries 1298 and pSeries systems. 1299 1300 To compile this driver as a module, choose M here. The module will 1301 be called ibmveth. 1302 1303source "drivers/net/ibm_newemac/Kconfig" 1304 1305config NET_PCI 1306 bool "EISA, VLB, PCI and on board controllers" 1307 depends on ISA || EISA || PCI 1308 help 1309 This is another class of network cards which attach directly to the 1310 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 1311 available from <http://www.tldp.org/docs.html#howto>. 1312 1313 Note that the answer to this question doesn't directly affect the 1314 kernel: saying N will just cause the configurator to skip all 1315 the questions about this class of network cards. If you say Y, you 1316 will be asked for your specific card in the following questions. If 1317 you are unsure, say Y. 1318 1319config PCNET32 1320 tristate "AMD PCnet32 PCI support" 1321 depends on NET_PCI && PCI 1322 select CRC32 1323 select MII 1324 help 1325 If you have a PCnet32 or PCnetPCI based network (Ethernet) card, 1326 answer Y here and read the Ethernet-HOWTO, available from 1327 <http://www.tldp.org/docs.html#howto>. 1328 1329 To compile this driver as a module, choose M here. The module 1330 will be called pcnet32. 1331 1332config AMD8111_ETH 1333 tristate "AMD 8111 (new PCI lance) support" 1334 depends on NET_PCI && PCI 1335 select CRC32 1336 select MII 1337 help 1338 If you have an AMD 8111-based PCI lance ethernet card, 1339 answer Y here and read the Ethernet-HOWTO, available from 1340 <http://www.tldp.org/docs.html#howto>. 1341 1342 To compile this driver as a module, choose M here. The module 1343 will be called amd8111e. 1344 1345config ADAPTEC_STARFIRE 1346 tristate "Adaptec Starfire/DuraLAN support" 1347 depends on NET_PCI && PCI 1348 select CRC32 1349 select MII 1350 help 1351 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network 1352 adapter. The DuraLAN chip is used on the 64 bit PCI boards from 1353 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip 1354 driver. 1355 1356 To compile this driver as a module, choose M here: the module 1357 will be called starfire. This is recommended. 1358 1359config AC3200 1360 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" 1361 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL 1362 select CRC32 1363 help 1364 If you have a network (Ethernet) card of this type, say Y and read 1365 the Ethernet-HOWTO, available from 1366 <http://www.tldp.org/docs.html#howto>. 1367 1368 To compile this driver as a module, choose M here. The module 1369 will be called ac3200. 1370 1371config APRICOT 1372 tristate "Apricot Xen-II on board Ethernet" 1373 depends on NET_PCI && ISA 1374 help 1375 If you have a network (Ethernet) controller of this type, say Y and 1376 read the Ethernet-HOWTO, available from 1377 <http://www.tldp.org/docs.html#howto>. 1378 1379 To compile this driver as a module, choose M here. The module 1380 will be called apricot. 1381 1382config B44 1383 tristate "Broadcom 440x/47xx ethernet support" 1384 depends on SSB_POSSIBLE && HAS_DMA 1385 select SSB 1386 select MII 1387 help 1388 If you have a network (Ethernet) controller of this type, say Y 1389 or M and read the Ethernet-HOWTO, available from 1390 <http://www.tldp.org/docs.html#howto>. 1391 1392 To compile this driver as a module, choose M here. The module 1393 will be called b44. 1394 1395# Auto-select SSB PCI-HOST support, if possible 1396config B44_PCI_AUTOSELECT 1397 bool 1398 depends on B44 && SSB_PCIHOST_POSSIBLE 1399 select SSB_PCIHOST 1400 default y 1401 1402# Auto-select SSB PCICORE driver, if possible 1403config B44_PCICORE_AUTOSELECT 1404 bool 1405 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE 1406 select SSB_DRIVER_PCICORE 1407 default y 1408 1409config B44_PCI 1410 bool 1411 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT 1412 default y 1413 1414config FORCEDETH 1415 tristate "nForce Ethernet support" 1416 depends on NET_PCI && PCI 1417 help 1418 If you have a network (Ethernet) controller of this type, say Y and 1419 read the Ethernet-HOWTO, available from 1420 <http://www.tldp.org/docs.html#howto>. 1421 1422 To compile this driver as a module, choose M here. The module 1423 will be called forcedeth. 1424 1425config FORCEDETH_NAPI 1426 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 1427 depends on FORCEDETH && EXPERIMENTAL 1428 help 1429 NAPI is a new driver API designed to reduce CPU and interrupt load 1430 when the driver is receiving lots of packets from the card. It is 1431 still somewhat experimental and thus not yet enabled by default. 1432 1433 If your estimated Rx load is 10kpps or more, or if the card will be 1434 deployed on potentially unfriendly networks (e.g. in a firewall), 1435 then say Y here. 1436 1437 If in doubt, say N. 1438 1439config CS89x0 1440 tristate "CS89x0 support" 1441 depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \ 1442 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS) 1443 ---help--- 1444 Support for CS89x0 chipset based Ethernet cards. If you have a 1445 network (Ethernet) card of this type, say Y and read the 1446 Ethernet-HOWTO, available from 1447 <http://www.tldp.org/docs.html#howto> as well as 1448 <file:Documentation/networking/cs89x0.txt>. 1449 1450 To compile this driver as a module, choose M here. The module 1451 will be called cs89x0. 1452 1453config CS89x0_NONISA_IRQ 1454 def_bool y 1455 depends on CS89x0 != n 1456 depends on MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X || MACH_MX31ADS 1457 1458config TC35815 1459 tristate "TOSHIBA TC35815 Ethernet support" 1460 depends on NET_PCI && PCI && MIPS 1461 select PHYLIB 1462 1463config E100 1464 tristate "Intel(R) PRO/100+ support" 1465 depends on NET_PCI && PCI 1466 select MII 1467 ---help--- 1468 This driver supports Intel(R) PRO/100 family of adapters. 1469 To verify that your adapter is supported, find the board ID number 1470 on the adapter. Look for a label that has a barcode and a number 1471 in the format 123456-001 (six digits hyphen three digits). 1472 1473 Use the above information and the Adapter & Driver ID Guide at: 1474 1475 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 1476 1477 to identify the adapter. 1478 1479 For the latest Intel PRO/100 network driver for Linux, see: 1480 1481 <http://appsr.intel.com/scripts-df/support_intel.asp> 1482 1483 More specific information on configuring the driver is in 1484 <file:Documentation/networking/e100.txt>. 1485 1486 To compile this driver as a module, choose M here. The module 1487 will be called e100. 1488 1489config LNE390 1490 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" 1491 depends on NET_PCI && EISA && EXPERIMENTAL 1492 select CRC32 1493 help 1494 If you have a network (Ethernet) card of this type, say Y and read 1495 the Ethernet-HOWTO, available from 1496 <http://www.tldp.org/docs.html#howto>. 1497 1498 To compile this driver as a module, choose M here. The module 1499 will be called lne390. 1500 1501config FEALNX 1502 tristate "Myson MTD-8xx PCI Ethernet support" 1503 depends on NET_PCI && PCI 1504 select CRC32 1505 select MII 1506 help 1507 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet 1508 cards. Specifications and data at 1509 <http://www.myson.com.hk/mtd/datasheet/>. 1510 1511config NATSEMI 1512 tristate "National Semiconductor DP8381x series PCI Ethernet support" 1513 depends on NET_PCI && PCI 1514 select CRC32 1515 help 1516 This driver is for the National Semiconductor DP83810 series, 1517 which is used in cards from PureData, NetGear, Linksys 1518 and others, including the 83815 chip. 1519 More specific information and updates are available from 1520 <http://www.scyld.com/network/natsemi.html>. 1521 1522config NE2K_PCI 1523 tristate "PCI NE2000 and clones support (see help)" 1524 depends on NET_PCI && PCI 1525 select CRC32 1526 ---help--- 1527 This driver is for NE2000 compatible PCI cards. It will not work 1528 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 1529 support" below). If you have a PCI NE2000 network (Ethernet) card, 1530 say Y and read the Ethernet-HOWTO, available from 1531 <http://www.tldp.org/docs.html#howto>. 1532 1533 This driver also works for the following NE2000 clone cards: 1534 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 1535 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond 1536 Holtek HT80232 Holtek HT80229 1537 1538 To compile this driver as a module, choose M here. The module 1539 will be called ne2k-pci. 1540 1541config NE3210 1542 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" 1543 depends on NET_PCI && EISA && EXPERIMENTAL 1544 select CRC32 1545 ---help--- 1546 If you have a network (Ethernet) card of this type, say Y and read 1547 the Ethernet-HOWTO, available from 1548 <http://www.tldp.org/docs.html#howto>. Note that this driver 1549 will NOT WORK for NE3200 cards as they are completely different. 1550 1551 To compile this driver as a module, choose M here. The module 1552 will be called ne3210. 1553 1554config ES3210 1555 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" 1556 depends on NET_PCI && EISA && EXPERIMENTAL 1557 select CRC32 1558 help 1559 If you have a network (Ethernet) card of this type, say Y and read 1560 the Ethernet-HOWTO, available from 1561 <http://www.tldp.org/docs.html#howto>. 1562 1563 To compile this driver as a module, choose M here. The module 1564 will be called es3210. 1565 1566config 8139CP 1567 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" 1568 depends on NET_PCI && PCI && EXPERIMENTAL 1569 select CRC32 1570 select MII 1571 help 1572 This is a driver for the Fast Ethernet PCI network cards based on 1573 the RTL8139C+ chips. If you have one of those, say Y and read 1574 the Ethernet-HOWTO, available from 1575 <http://www.tldp.org/docs.html#howto>. 1576 1577 To compile this driver as a module, choose M here: the module 1578 will be called 8139cp. This is recommended. 1579 1580config 8139TOO 1581 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" 1582 depends on NET_PCI && PCI 1583 select CRC32 1584 select MII 1585 ---help--- 1586 This is a driver for the Fast Ethernet PCI network cards based on 1587 the RTL 8129/8130/8139 chips. If you have one of those, say Y and 1588 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. 1589 1590 To compile this driver as a module, choose M here: the module 1591 will be called 8139too. This is recommended. 1592 1593config 8139TOO_PIO 1594 bool "Use PIO instead of MMIO" 1595 default y 1596 depends on 8139TOO 1597 help 1598 This instructs the driver to use programmed I/O ports (PIO) instead 1599 of PCI shared memory (MMIO). This can possibly solve some problems 1600 in case your mainboard has memory consistency issues. If unsure, 1601 say N. 1602 1603config 8139TOO_TUNE_TWISTER 1604 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" 1605 depends on 8139TOO 1606 help 1607 This implements a function which might come in handy in case you 1608 are using low quality on long cabling. It is required for RealTek 1609 RTL-8139 revision K boards, and totally unused otherwise. It tries 1610 to match the transceiver to the cable characteristics. This is 1611 experimental since hardly documented by the manufacturer. 1612 If unsure, say Y. 1613 1614config 8139TOO_8129 1615 bool "Support for older RTL-8129/8130 boards" 1616 depends on 8139TOO 1617 help 1618 This enables support for the older and uncommon RTL-8129 and 1619 RTL-8130 chips, which support MII via an external transceiver, 1620 instead of an internal one. Disabling this option will save some 1621 memory by making the code size smaller. If unsure, say Y. 1622 1623config 8139_OLD_RX_RESET 1624 bool "Use older RX-reset method" 1625 depends on 8139TOO 1626 help 1627 The 8139too driver was recently updated to contain a more rapid 1628 reset sequence, in the face of severe receive errors. This "new" 1629 RX-reset method should be adequate for all boards. But if you 1630 experience problems, you can enable this option to restore the 1631 old RX-reset behavior. If unsure, say N. 1632 1633config R6040 1634 tristate "RDC R6040 Fast Ethernet Adapter support" 1635 depends on NET_PCI && PCI 1636 select CRC32 1637 select MII 1638 help 1639 This is a driver for the R6040 Fast Ethernet MACs found in the 1640 the RDC R-321x System-on-chips. 1641 1642 To compile this driver as a module, choose M here: the module 1643 will be called r6040. This is recommended. 1644 1645config SIS900 1646 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" 1647 depends on NET_PCI && PCI 1648 select CRC32 1649 select MII 1650 ---help--- 1651 This is a driver for the Fast Ethernet PCI network cards based on 1652 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in 1653 SiS 630 and SiS 540 chipsets. 1654 1655 This driver also supports AMD 79C901 HomePNA so that you can use 1656 your phone line as a network cable. 1657 1658 To compile this driver as a module, choose M here: the module 1659 will be called sis900. This is recommended. 1660 1661config EPIC100 1662 tristate "SMC EtherPower II" 1663 depends on NET_PCI && PCI 1664 select CRC32 1665 select MII 1666 help 1667 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, 1668 which is based on the SMC83c17x (EPIC/100). 1669 More specific information and updates are available from 1670 <http://www.scyld.com/network/epic100.html>. 1671 1672config SMSC9420 1673 tristate "SMSC LAN9420 PCI ethernet adapter support" 1674 depends on NET_PCI && PCI 1675 select CRC32 1676 select PHYLIB 1677 select SMSC_PHY 1678 help 1679 This is a driver for SMSC's LAN9420 PCI ethernet adapter. 1680 Say Y if you want it compiled into the kernel, 1681 and read the Ethernet-HOWTO, available from 1682 <http://www.linuxdoc.org/docs.html#howto>. 1683 1684 This driver is also available as a module. The module will be 1685 called smsc9420. If you want to compile it as a module, say M 1686 here and read <file:Documentation/kbuild/modules.txt> 1687 1688config SUNDANCE 1689 tristate "Sundance Alta support" 1690 depends on NET_PCI && PCI 1691 select CRC32 1692 select MII 1693 help 1694 This driver is for the Sundance "Alta" chip. 1695 More specific information and updates are available from 1696 <http://www.scyld.com/network/sundance.html>. 1697 1698config SUNDANCE_MMIO 1699 bool "Use MMIO instead of PIO" 1700 depends on SUNDANCE 1701 help 1702 Enable memory-mapped I/O for interaction with Sundance NIC registers. 1703 Do NOT enable this by default, PIO (enabled when MMIO is disabled) 1704 is known to solve bugs on certain chips. 1705 1706 If unsure, say N. 1707 1708config TLAN 1709 tristate "TI ThunderLAN support" 1710 depends on NET_PCI && (PCI || EISA) 1711 ---help--- 1712 If you have a PCI Ethernet network card based on the ThunderLAN chip 1713 which is supported by this driver, say Y and read the 1714 Ethernet-HOWTO, available from 1715 <http://www.tldp.org/docs.html#howto>. 1716 1717 Devices currently supported by this driver are Compaq Netelligent, 1718 Compaq NetFlex and Olicom cards. Please read the file 1719 <file:Documentation/networking/tlan.txt> for more details. 1720 1721 To compile this driver as a module, choose M here. The module 1722 will be called tlan. 1723 1724 Please email feedback to <torben.mathiasen@compaq.com>. 1725 1726config KS8842 1727 tristate "Micrel KSZ8842" 1728 depends on HAS_IOMEM 1729 help 1730 This platform driver is for Micrel KSZ8842 / KS8842 1731 2-port ethernet switch chip (managed, VLAN, QoS). 1732 1733config KS8851 1734 tristate "Micrel KS8851 SPI" 1735 depends on SPI 1736 select MII 1737 select CRC32 1738 help 1739 SPI driver for Micrel KS8851 SPI attached network chip. 1740 1741config KS8851_MLL 1742 tristate "Micrel KS8851 MLL" 1743 depends on HAS_IOMEM 1744 select MII 1745 help 1746 This platform driver is for Micrel KS8851 Address/data bus 1747 multiplexed network chip. 1748 1749config VIA_RHINE 1750 tristate "VIA Rhine support" 1751 depends on NET_PCI && PCI 1752 select CRC32 1753 select MII 1754 help 1755 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), 1756 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type 1757 Ethernet functions can also be found integrated on South Bridges 1758 (e.g. VT8235). 1759 1760 To compile this driver as a module, choose M here. The module 1761 will be called via-rhine. 1762 1763config VIA_RHINE_MMIO 1764 bool "Use MMIO instead of PIO" 1765 depends on VIA_RHINE 1766 help 1767 This instructs the driver to use PCI shared memory (MMIO) instead of 1768 programmed I/O ports (PIO). Enabling this gives an improvement in 1769 processing time in parts of the driver. 1770 1771 If unsure, say Y. 1772 1773config SC92031 1774 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)" 1775 depends on NET_PCI && PCI && EXPERIMENTAL 1776 select CRC32 1777 ---help--- 1778 This is a driver for the Fast Ethernet PCI network cards based on 1779 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you 1780 have one of these, say Y here. 1781 1782 To compile this driver as a module, choose M here: the module 1783 will be called sc92031. This is recommended. 1784 1785config CPMAC 1786 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" 1787 depends on NET_ETHERNET && EXPERIMENTAL && AR7 1788 select PHYLIB 1789 help 1790 TI AR7 CPMAC Ethernet support 1791 1792config NET_POCKET 1793 bool "Pocket and portable adapters" 1794 depends on PARPORT 1795 ---help--- 1796 Cute little network (Ethernet) devices which attach to the parallel 1797 port ("pocket adapters"), commonly used with laptops. If you have 1798 one of those, say Y and read the Ethernet-HOWTO, available from 1799 <http://www.tldp.org/docs.html#howto>. 1800 1801 If you want to plug a network (or some other) card into the PCMCIA 1802 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 1803 credit card size extension cards used by all modern laptops), you 1804 need the pcmcia-cs package (location contained in the file 1805 <file:Documentation/Changes>) and you can say N here. 1806 1807 Laptop users should read the Linux Laptop home page at 1808 <http://www.linux-on-laptops.com/> or 1809 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 1810 1811 Note that the answer to this question doesn't directly affect the 1812 kernel: saying N will just cause the configurator to skip all 1813 the questions about this class of network devices. If you say Y, you 1814 will be asked for your specific device in the following questions. 1815 1816config ATP 1817 tristate "AT-LAN-TEC/RealTek pocket adapter support" 1818 depends on NET_POCKET && PARPORT && X86 1819 select CRC32 1820 ---help--- 1821 This is a network (Ethernet) device which attaches to your parallel 1822 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, 1823 available from <http://www.tldp.org/docs.html#howto>, if you 1824 want to use this. If you intend to use this driver, you should have 1825 said N to the "Parallel printer support", because the two drivers 1826 don't like each other. 1827 1828 To compile this driver as a module, choose M here: the module 1829 will be called atp. 1830 1831config DE600 1832 tristate "D-Link DE600 pocket adapter support" 1833 depends on NET_POCKET && PARPORT 1834 ---help--- 1835 This is a network (Ethernet) device which attaches to your parallel 1836 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1837 Ethernet-HOWTO, available from 1838 <http://www.tldp.org/docs.html#howto>, if you want to use 1839 this. It is possible to have several devices share a single parallel 1840 port and it is safe to compile the corresponding drivers into the 1841 kernel. 1842 1843 To compile this driver as a module, choose M here: the module 1844 will be called de600. 1845 1846config DE620 1847 tristate "D-Link DE620 pocket adapter support" 1848 depends on NET_POCKET && PARPORT 1849 ---help--- 1850 This is a network (Ethernet) device which attaches to your parallel 1851 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1852 Ethernet-HOWTO, available from 1853 <http://www.tldp.org/docs.html#howto>, if you want to use 1854 this. It is possible to have several devices share a single parallel 1855 port and it is safe to compile the corresponding drivers into the 1856 kernel. 1857 1858 To compile this driver as a module, choose M here: the module 1859 will be called de620. 1860 1861config SGISEEQ 1862 tristate "SGI Seeq ethernet controller support" 1863 depends on SGI_HAS_SEEQ 1864 help 1865 Say Y here if you have an Seeq based Ethernet network card. This is 1866 used in many Silicon Graphics machines. 1867 1868config DECLANCE 1869 tristate "DEC LANCE ethernet controller support" 1870 depends on MACH_DECSTATION 1871 select CRC32 1872 help 1873 This driver is for the series of Ethernet controllers produced by 1874 DEC (now Compaq) based on the AMD Lance chipset, including the 1875 DEPCA series. (This chipset is better known via the NE2100 cards.) 1876 1877config 68360_ENET 1878 bool "Motorola 68360 ethernet controller" 1879 depends on M68360 1880 help 1881 Say Y here if you want to use the built-in ethernet controller of 1882 the Motorola 68360 processor. 1883 1884config FEC 1885 bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)" 1886 depends on M523x || M527x || M5272 || M528x || M520x || M532x || MACH_MX27 || ARCH_MX35 || ARCH_MX25 1887 help 1888 Say Y here if you want to use the built-in 10/100 Fast ethernet 1889 controller on some Motorola ColdFire and Freescale i.MX processors. 1890 1891config FEC2 1892 bool "Second FEC ethernet controller (on some ColdFire CPUs)" 1893 depends on FEC 1894 help 1895 Say Y here if you want to use the second built-in 10/100 Fast 1896 ethernet controller on some Motorola ColdFire processors. 1897 1898config FEC_MPC52xx 1899 tristate "MPC52xx FEC driver" 1900 depends on PPC_MPC52xx && PPC_BESTCOMM 1901 select CRC32 1902 select PHYLIB 1903 select PPC_BESTCOMM_FEC 1904 ---help--- 1905 This option enables support for the MPC5200's on-chip 1906 Fast Ethernet Controller 1907 If compiled as module, it will be called fec_mpc52xx. 1908 1909config FEC_MPC52xx_MDIO 1910 bool "MPC52xx FEC MDIO bus driver" 1911 depends on FEC_MPC52xx 1912 default y 1913 ---help--- 1914 The MPC5200's FEC can connect to the Ethernet either with 1915 an external MII PHY chip or 10 Mbps 7-wire interface 1916 (Motorola? industry standard). 1917 If your board uses an external PHY connected to FEC, enable this. 1918 If not sure, enable. 1919 If compiled as module, it will be called fec_mpc52xx_phy. 1920 1921config NE_H8300 1922 tristate "NE2000 compatible support for H8/300" 1923 depends on H8300 1924 help 1925 Say Y here if you want to use the NE2000 compatible 1926 controller on the Renesas H8/300 processor. 1927 1928config ATL2 1929 tristate "Atheros L2 Fast Ethernet support" 1930 depends on PCI 1931 select CRC32 1932 select MII 1933 help 1934 This driver supports the Atheros L2 fast ethernet adapter. 1935 1936 To compile this driver as a module, choose M here. The module 1937 will be called atl2. 1938 1939config XILINX_EMACLITE 1940 tristate "Xilinx 10/100 Ethernet Lite support" 1941 depends on PPC32 || MICROBLAZE 1942 help 1943 This driver supports the 10/100 Ethernet Lite from Xilinx. 1944 1945config BCM63XX_ENET 1946 tristate "Broadcom 63xx internal mac support" 1947 depends on BCM63XX 1948 select MII 1949 select PHYLIB 1950 help 1951 This driver supports the ethernet MACs in the Broadcom 63xx 1952 MIPS chipset family (BCM63XX). 1953 1954source "drivers/net/fs_enet/Kconfig" 1955 1956source "drivers/net/octeon/Kconfig" 1957 1958endif # NET_ETHERNET 1959 1960# 1961# Gigabit Ethernet 1962# 1963 1964menuconfig NETDEV_1000 1965 bool "Ethernet (1000 Mbit)" 1966 depends on !UML 1967 default y 1968 ---help--- 1969 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 1970 type of Local Area Network (LAN) in universities and companies. 1971 1972 Say Y here to get to see options for Gigabit Ethernet drivers. 1973 This option alone does not add any kernel code. 1974 Note that drivers supporting both 100 and 1000 MBit may be listed 1975 under "Ethernet (10 or 100MBit)" instead. 1976 1977 If you say N, all options in this submenu will be skipped and disabled. 1978 1979if NETDEV_1000 1980 1981config ACENIC 1982 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" 1983 depends on PCI 1984 ---help--- 1985 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear 1986 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet 1987 adapter. The driver allows for using the Jumbo Frame option (9000 1988 bytes/frame) however it requires that your switches can handle this 1989 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig 1990 line. 1991 1992 To compile this driver as a module, choose M here: the 1993 module will be called acenic. 1994 1995config ACENIC_OMIT_TIGON_I 1996 bool "Omit support for old Tigon I based AceNICs" 1997 depends on ACENIC 1998 help 1999 Say Y here if you only have Tigon II based AceNICs and want to leave 2000 out support for the older Tigon I based cards which are no longer
2001 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B 2002 version)). This will reduce the size of the driver object by 2003 app. 100KB. If you are not sure whether your card is a Tigon I or a 2004 Tigon II, say N here. 2005 2006 The safe and default value for this is N. 2007 2008config DL2K 2009 tristate "DL2000/TC902x-based Gigabit Ethernet support" 2010 depends on PCI 2011 select CRC32 2012 help 2013 This driver supports DL2000/TC902x-based Gigabit ethernet cards, 2014 which includes 2015 D-Link DGE-550T Gigabit Ethernet Adapter. 2016 D-Link DL2000-based Gigabit Ethernet Adapter. 2017 Sundance/Tamarack TC902x Gigabit Ethernet Adapter. 2018 2019 To compile this driver as a module, choose M here: the 2020 module will be called dl2k. 2021 2022config E1000 2023 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" 2024 depends on PCI 2025 ---help--- 2026 This driver supports Intel(R) PRO/1000 gigabit ethernet family of 2027 adapters. For more information on how to identify your adapter, go 2028 to the Adapter & Driver ID Guide at: 2029 2030 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2031 2032 For general information and support, go to the Intel support 2033 website at: 2034 2035 <http://support.intel.com> 2036 2037 More specific information on configuring the driver is in 2038 <file:Documentation/networking/e1000.txt>. 2039 2040 To compile this driver as a module, choose M here. The module 2041 will be called e1000. 2042 2043config E1000E 2044 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" 2045 depends on PCI && (!SPARC32 || BROKEN) 2046 ---help--- 2047 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit 2048 ethernet family of adapters. For PCI or PCI-X e1000 adapters, 2049 use the regular e1000 driver For more information on how to 2050 identify your adapter, go to the Adapter & Driver ID Guide at: 2051 2052 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2053 2054 For general information and support, go to the Intel support 2055 website at: 2056 2057 <http://support.intel.com> 2058 2059 To compile this driver as a module, choose M here. The module 2060 will be called e1000e. 2061 2062config IP1000 2063 tristate "IP1000 Gigabit Ethernet support" 2064 depends on PCI && EXPERIMENTAL 2065 select MII 2066 ---help--- 2067 This driver supports IP1000 gigabit Ethernet cards. 2068 2069 To compile this driver as a module, choose M here: the module 2070 will be called ipg. This is recommended. 2071 2072config IGB 2073 tristate "Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support" 2074 depends on PCI 2075 ---help--- 2076 This driver supports Intel(R) 82575/82576 gigabit ethernet family of 2077 adapters. For more information on how to identify your adapter, go 2078 to the Adapter & Driver ID Guide at: 2079 2080 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2081 2082 For general information and support, go to the Intel support 2083 website at: 2084 2085 <http://support.intel.com> 2086 2087 More specific information on configuring the driver is in 2088 <file:Documentation/networking/e1000.txt>. 2089 2090 To compile this driver as a module, choose M here. The module 2091 will be called igb. 2092 2093config IGB_DCA 2094 bool "Direct Cache Access (DCA) Support" 2095 default y 2096 depends on IGB && DCA && !(IGB=y && DCA=m) 2097 ---help--- 2098 Say Y here if you want to use Direct Cache Access (DCA) in the 2099 driver. DCA is a method for warming the CPU cache before data 2100 is used, with the intent of lessening the impact of cache misses. 2101 2102config IGBVF 2103 tristate "Intel(R) 82576 Virtual Function Ethernet support" 2104 depends on PCI 2105 ---help--- 2106 This driver supports Intel(R) 82576 virtual functions. For more 2107 information on how to identify your adapter, go to the Adapter & 2108 Driver ID Guide at: 2109 2110 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2111 2112 For general information and support, go to the Intel support 2113 website at: 2114 2115 <http://support.intel.com> 2116 2117 More specific information on configuring the driver is in 2118 <file:Documentation/networking/e1000.txt>. 2119 2120 To compile this driver as a module, choose M here. The module 2121 will be called igbvf. 2122 2123source "drivers/net/ixp2000/Kconfig" 2124 2125config MYRI_SBUS 2126 tristate "MyriCOM Gigabit Ethernet support" 2127 depends on SBUS 2128 help 2129 This driver supports MyriCOM Sbus gigabit Ethernet cards. 2130 2131 To compile this driver as a module, choose M here: the module 2132 will be called myri_sbus. This is recommended. 2133 2134config NS83820 2135 tristate "National Semiconductor DP83820 support" 2136 depends on PCI 2137 help 2138 This is a driver for the National Semiconductor DP83820 series 2139 of gigabit ethernet MACs. Cards using this chipset include 2140 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, 2141 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of 2142 zero copy. 2143 2144config HAMACHI 2145 tristate "Packet Engines Hamachi GNIC-II support" 2146 depends on PCI 2147 select MII 2148 help 2149 If you have a Gigabit Ethernet card of this type, say Y and read 2150 the Ethernet-HOWTO, available from 2151 <http://www.tldp.org/docs.html#howto>. 2152 2153 To compile this driver as a module, choose M here. The module will be 2154 called hamachi. 2155 2156config YELLOWFIN 2157 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 2158 depends on PCI && EXPERIMENTAL 2159 select CRC32 2160 ---help--- 2161 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 2162 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 2163 used by the Beowulf Linux cluster project. See 2164 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 2165 information about this driver in particular and Beowulf in general. 2166 2167 To compile this driver as a module, choose M here: the module 2168 will be called yellowfin. This is recommended. 2169 2170config R8169 2171 tristate "Realtek 8169 gigabit ethernet support" 2172 depends on PCI 2173 select CRC32 2174 select MII 2175 ---help--- 2176 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. 2177 2178 To compile this driver as a module, choose M here: the module 2179 will be called r8169. This is recommended. 2180 2181config R8169_VLAN 2182 bool "VLAN support" 2183 depends on R8169 && VLAN_8021Q 2184 ---help--- 2185 Say Y here for the r8169 driver to support the functions required 2186 by the kernel 802.1Q code. 2187 2188 If in doubt, say Y. 2189 2190config SB1250_MAC 2191 tristate "SB1250 Gigabit Ethernet support" 2192 depends on SIBYTE_SB1xxx_SOC 2193 select PHYLIB 2194 ---help--- 2195 This driver supports Gigabit Ethernet interfaces based on the 2196 Broadcom SiByte family of System-On-a-Chip parts. They include 2197 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 2198 and BCM1480 chips. 2199 2200 To compile this driver as a module, choose M here: the module 2201 will be called sb1250-mac. 2202 2203config SIS190 2204 tristate "SiS190/SiS191 gigabit ethernet support" 2205 depends on PCI 2206 select CRC32 2207 select MII 2208 ---help--- 2209 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or 2210 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to 2211 appear in lan on motherboard designs which are based on SiS 965 2212 and SiS 966 south bridge. 2213 2214 To compile this driver as a module, choose M here: the module 2215 will be called sis190. This is recommended. 2216 2217config SKGE 2218 tristate "New SysKonnect GigaEthernet support" 2219 depends on PCI 2220 select CRC32 2221 ---help--- 2222 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2223 and related Gigabit Ethernet adapters. It is a new smaller driver 2224 with better performance and more complete ethtool support. 2225 2226 It does not support the link failover and network management 2227 features that "portable" vendor supplied sk98lin driver does. 2228 2229 This driver supports adapters based on the original Yukon chipset: 2230 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, 2231 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. 2232 2233 It does not support the newer Yukon2 chipset: a separate driver, 2234 sky2, is provided for Yukon2-based adapters. 2235 2236 To compile this driver as a module, choose M here: the module 2237 will be called skge. This is recommended. 2238 2239config SKGE_DEBUG 2240 bool "Debugging interface" 2241 depends on SKGE && DEBUG_FS 2242 help 2243 This option adds the ability to dump driver state for debugging. 2244 The file /sys/kernel/debug/skge/ethX displays the state of the internal 2245 transmit and receive rings. 2246 2247 If unsure, say N. 2248 2249config SKY2 2250 tristate "SysKonnect Yukon2 support" 2251 depends on PCI 2252 select CRC32 2253 ---help--- 2254 This driver supports Gigabit Ethernet adapters based on the 2255 Marvell Yukon 2 chipset: 2256 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 2257 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 2258 2259 There is companion driver for the older Marvell Yukon and 2260 Genesis based adapters: skge. 2261 2262 To compile this driver as a module, choose M here: the module 2263 will be called sky2. This is recommended. 2264 2265config SKY2_DEBUG 2266 bool "Debugging interface" 2267 depends on SKY2 && DEBUG_FS 2268 help 2269 This option adds the ability to dump driver state for debugging. 2270 The file /sys/kernel/debug/sky2/ethX displays the state of the internal 2271 transmit and receive rings. 2272 2273 If unsure, say N. 2274 2275config VIA_VELOCITY 2276 tristate "VIA Velocity support" 2277 depends on PCI 2278 select CRC32 2279 select CRC_CCITT 2280 select MII 2281 help 2282 If you have a VIA "Velocity" based network card say Y here. 2283 2284 To compile this driver as a module, choose M here. The module 2285 will be called via-velocity. 2286 2287config TIGON3 2288 tristate "Broadcom Tigon3 support" 2289 depends on PCI 2290 select PHYLIB 2291 help 2292 This driver supports Broadcom Tigon3 based gigabit Ethernet cards. 2293 2294 To compile this driver as a module, choose M here: the module 2295 will be called tg3. This is recommended. 2296 2297config BNX2 2298 tristate "Broadcom NetXtremeII support" 2299 depends on PCI 2300 select CRC32 2301 select FW_LOADER 2302 help 2303 This driver supports Broadcom NetXtremeII gigabit Ethernet cards. 2304 2305 To compile this driver as a module, choose M here: the module 2306 will be called bnx2. This is recommended. 2307 2308config CNIC 2309 tristate "Broadcom CNIC support" 2310 depends on PCI 2311 select BNX2 2312 select UIO 2313 help 2314 This driver supports offload features of Broadcom NetXtremeII 2315 gigabit Ethernet cards. 2316 2317 To compile this driver as a module, choose M here: the module 2318 will be called cnic. This is recommended. 2319 2320config SPIDER_NET 2321 tristate "Spider Gigabit Ethernet driver" 2322 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 2323 select FW_LOADER 2324 help 2325 This driver supports the Gigabit Ethernet chips present on the 2326 Cell Processor-Based Blades from IBM. 2327 2328config TSI108_ETH 2329 tristate "Tundra TSI108 gigabit Ethernet support" 2330 depends on TSI108_BRIDGE 2331 help 2332 This driver supports Tundra TSI108 gigabit Ethernet ports. 2333 To compile this driver as a module, choose M here: the module 2334 will be called tsi108_eth. 2335 2336config GELIC_NET 2337 tristate "PS3 Gigabit Ethernet driver" 2338 depends on PPC_PS3 2339 select PS3_SYS_MANAGER 2340 help 2341 This driver supports the network device on the PS3 game 2342 console. This driver has built-in support for Ethernet. 2343 2344 To compile this driver as a module, choose M here: the 2345 module will be called ps3_gelic. 2346 2347config GELIC_WIRELESS 2348 bool "PS3 Wireless support" 2349 depends on WLAN 2350 depends on GELIC_NET 2351 select WIRELESS_EXT 2352 help 2353 This option adds the support for the wireless feature of PS3. 2354 If you have the wireless-less model of PS3 or have no plan to 2355 use wireless feature, disabling this option saves memory. As 2356 the driver automatically distinguishes the models, you can 2357 safely enable this option even if you have a wireless-less model. 2358 2359config GELIC_WIRELESS_OLD_PSK_INTERFACE 2360 bool "PS3 Wireless private PSK interface (OBSOLETE)" 2361 depends on GELIC_WIRELESS 2362 select WEXT_PRIV 2363 help 2364 This option retains the obsolete private interface to pass 2365 the PSK from user space programs to the driver. The PSK 2366 stands for 'Pre Shared Key' and is used for WPA[2]-PSK 2367 (WPA-Personal) environment. 2368 If WPA[2]-PSK is used and you need to use old programs that 2369 support only this old interface, say Y. Otherwise N. 2370 2371 If unsure, say N. 2372 2373config FSL_PQ_MDIO 2374 tristate "Freescale PQ MDIO" 2375 depends on FSL_SOC 2376 select PHYLIB 2377 help 2378 This driver supports the MDIO bus used by the gianfar and UCC drivers. 2379 2380config GIANFAR 2381 tristate "Gianfar Ethernet" 2382 depends on FSL_SOC 2383 select FSL_PQ_MDIO 2384 select PHYLIB 2385 select CRC32 2386 help 2387 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, 2388 and MPC86xx family of chips, and the FEC on the 8540. 2389 2390config UCC_GETH 2391 tristate "Freescale QE Gigabit Ethernet" 2392 depends on QUICC_ENGINE 2393 select FSL_PQ_MDIO 2394 select PHYLIB 2395 help 2396 This driver supports the Gigabit Ethernet mode of the QUICC Engine, 2397 which is available on some Freescale SOCs. 2398 2399config UGETH_TX_ON_DEMAND 2400 bool "Transmit on Demand support" 2401 depends on UCC_GETH 2402 2403config MV643XX_ETH 2404 tristate "Marvell Discovery (643XX) and Orion ethernet support" 2405 depends on MV64X60 || PPC32 || PLAT_ORION 2406 select INET_LRO 2407 select PHYLIB 2408 help 2409 This driver supports the gigabit ethernet MACs in the 2410 Marvell Discovery PPC/MIPS chipset family (MV643XX) and 2411 in the Marvell Orion ARM SoC family. 2412 2413 Some boards that use the Discovery chipset are the Momenco 2414 Ocelot C and Jaguar ATX and Pegasos II. 2415 2416config XILINX_LL_TEMAC 2417 tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver" 2418 select PHYLIB 2419 depends on PPC_DCR_NATIVE 2420 help 2421 This driver supports the Xilinx 10/100/1000 LocalLink TEMAC 2422 core used in Xilinx Spartan and Virtex FPGAs 2423 2424config QLA3XXX 2425 tristate "QLogic QLA3XXX Network Driver Support" 2426 depends on PCI 2427 help 2428 This driver supports QLogic ISP3XXX gigabit Ethernet cards. 2429 2430 To compile this driver as a module, choose M here: the module 2431 will be called qla3xxx. 2432 2433config ATL1 2434 tristate "Atheros/Attansic L1 Gigabit Ethernet support" 2435 depends on PCI 2436 select CRC32 2437 select MII 2438 help 2439 This driver supports the Atheros/Attansic L1 gigabit ethernet 2440 adapter. 2441 2442 To compile this driver as a module, choose M here. The module 2443 will be called atl1. 2444 2445config ATL1E 2446 tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)" 2447 depends on PCI && EXPERIMENTAL 2448 select CRC32 2449 select MII 2450 help 2451 This driver supports the Atheros L1E gigabit ethernet adapter. 2452 2453 To compile this driver as a module, choose M here. The module 2454 will be called atl1e. 2455 2456config ATL1C 2457 tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)" 2458 depends on PCI && EXPERIMENTAL 2459 select CRC32 2460 select MII 2461 help 2462 This driver supports the Atheros L1C gigabit ethernet adapter. 2463 2464 To compile this driver as a module, choose M here. The module 2465 will be called atl1c. 2466 2467config JME 2468 tristate "JMicron(R) PCI-Express Gigabit Ethernet support" 2469 depends on PCI 2470 select CRC32 2471 select MII 2472 ---help--- 2473 This driver supports the PCI-Express gigabit ethernet adapters 2474 based on JMicron JMC250 chipset. 2475 2476 To compile this driver as a module, choose M here. The module 2477 will be called jme. 2478 2479config S6GMAC 2480 tristate "S6105 GMAC ethernet support" 2481 depends on XTENSA_VARIANT_S6000 2482 select PHYLIB 2483 help 2484 This driver supports the on chip ethernet device on the 2485 S6105 xtensa processor. 2486 2487 To compile this driver as a module, choose M here. The module 2488 will be called s6gmac. 2489 2490source "drivers/net/stmmac/Kconfig" 2491 2492endif # NETDEV_1000 2493 2494# 2495# 10 Gigabit Ethernet 2496# 2497 2498menuconfig NETDEV_10000 2499 bool "Ethernet (10000 Mbit)" 2500 depends on !UML 2501 default y 2502 ---help--- 2503 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 2504 This option alone does not add any kernel code. 2505 2506 If you say N, all options in this submenu will be skipped and disabled. 2507 2508if NETDEV_10000 2509 2510config MDIO 2511 tristate 2512 2513config CHELSIO_T1 2514 tristate "Chelsio 10Gb Ethernet support" 2515 depends on PCI 2516 select CRC32 2517 select MDIO 2518 help 2519 This driver supports Chelsio gigabit and 10-gigabit 2520 Ethernet cards. More information about adapter features and 2521 performance tuning is in <file:Documentation/networking/cxgb.txt>. 2522 2523 For general information about Chelsio and our products, visit 2524 our website at <http://www.chelsio.com>. 2525 2526 For customer support, please visit our customer support page at 2527 <http://www.chelsio.com/support.htm>. 2528 2529 Please send feedback to <linux-bugs@chelsio.com>. 2530 2531 To compile this driver as a module, choose M here: the module 2532 will be called cxgb. 2533 2534config CHELSIO_T1_1G 2535 bool "Chelsio gigabit Ethernet support" 2536 depends on CHELSIO_T1 2537 help 2538 Enables support for Chelsio's gigabit Ethernet PCI cards. If you 2539 are using only 10G cards say 'N' here. 2540 2541config CHELSIO_T3_DEPENDS 2542 tristate 2543 depends on PCI && INET 2544 default y 2545 2546config CHELSIO_T3 2547 tristate "Chelsio Communications T3 10Gb Ethernet support" 2548 depends on CHELSIO_T3_DEPENDS 2549 select FW_LOADER 2550 select MDIO 2551 help 2552 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet 2553 adapters. 2554 2555 For general information about Chelsio and our products, visit 2556 our website at <http://www.chelsio.com>. 2557 2558 For customer support, please visit our customer support page at 2559 <http://www.chelsio.com/support.htm>. 2560 2561 Please send feedback to <linux-bugs@chelsio.com>. 2562 2563 To compile this driver as a module, choose M here: the module 2564 will be called cxgb3. 2565 2566config EHEA 2567 tristate "eHEA Ethernet support" 2568 depends on IBMEBUS && INET && SPARSEMEM 2569 select INET_LRO 2570 ---help--- 2571 This driver supports the IBM pSeries eHEA ethernet adapter. 2572 2573 To compile the driver as a module, choose M here. The module 2574 will be called ehea. 2575 2576config ENIC 2577 tristate "Cisco 10G Ethernet NIC support" 2578 depends on PCI && INET 2579 select INET_LRO 2580 help 2581 This enables the support for the Cisco 10G Ethernet card. 2582 2583config IXGBE 2584 tristate "Intel(R) 10GbE PCI Express adapters support" 2585 depends on PCI && INET 2586 select MDIO 2587 ---help--- 2588 This driver supports Intel(R) 10GbE PCI Express family of 2589 adapters. For more information on how to identify your adapter, go 2590 to the Adapter & Driver ID Guide at: 2591 2592 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2593 2594 For general information and support, go to the Intel support 2595 website at: 2596 2597 <http://support.intel.com> 2598 2599 To compile this driver as a module, choose M here. The module 2600 will be called ixgbe. 2601 2602config IXGBE_DCA 2603 bool "Direct Cache Access (DCA) Support" 2604 default y 2605 depends on IXGBE && DCA && !(IXGBE=y && DCA=m) 2606 ---help--- 2607 Say Y here if you want to use Direct Cache Access (DCA) in the 2608 driver. DCA is a method for warming the CPU cache before data 2609 is used, with the intent of lessening the impact of cache misses. 2610 2611config IXGBE_DCB 2612 bool "Data Center Bridging (DCB) Support" 2613 default n 2614 depends on IXGBE && DCB 2615 ---help--- 2616 Say Y here if you want to use Data Center Bridging (DCB) in the 2617 driver. 2618 2619 If unsure, say N. 2620 2621config IXGB 2622 tristate "Intel(R) PRO/10GbE support" 2623 depends on PCI 2624 ---help--- 2625 This driver supports Intel(R) PRO/10GbE family of adapters for 2626 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 2627 instead. For more information on how to identify your adapter, go 2628 to the Adapter & Driver ID Guide at: 2629 2630 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2631 2632 For general information and support, go to the Intel support 2633 website at: 2634 2635 <http://support.intel.com> 2636 2637 More specific information on configuring the driver is in 2638 <file:Documentation/networking/ixgb.txt>. 2639 2640 To compile this driver as a module, choose M here. The module 2641 will be called ixgb. 2642 2643config S2IO 2644 tristate "S2IO 10Gbe XFrame NIC" 2645 depends on PCI 2646 ---help--- 2647 This driver supports the 10Gbe XFrame NIC of S2IO. 2648 More specific information on configuring the driver is in 2649 <file:Documentation/networking/s2io.txt>. 2650 2651config VXGE 2652 tristate "Neterion X3100 Series 10GbE PCIe Server Adapter" 2653 depends on PCI && INET 2654 ---help--- 2655 This driver supports Neterion Inc's X3100 Series 10 GbE PCIe 2656 I/O Virtualized Server Adapter. 2657 More specific information on configuring the driver is in 2658 <file:Documentation/networking/vxge.txt>. 2659 2660config VXGE_DEBUG_TRACE_ALL 2661 bool "Enabling All Debug trace statments in driver" 2662 default n 2663 depends on VXGE 2664 ---help--- 2665 Say Y here if you want to enabling all the debug trace statements in 2666 driver. By default only few debug trace statements are enabled. 2667 2668config MYRI10GE 2669 tristate "Myricom Myri-10G Ethernet support" 2670 depends on PCI && INET 2671 select FW_LOADER 2672 select CRC32 2673 select INET_LRO 2674 ---help--- 2675 This driver supports Myricom Myri-10G Dual Protocol interface in 2676 Ethernet mode. If the eeprom on your board is not recent enough, 2677 you will need a newer firmware image. 2678 You may get this image or more information, at: 2679 2680 <http://www.myri.com/scs/download-Myri10GE.html> 2681 2682 To compile this driver as a module, choose M here. The module 2683 will be called myri10ge. 2684 2685config MYRI10GE_DCA 2686 bool "Direct Cache Access (DCA) Support" 2687 default y 2688 depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m) 2689 ---help--- 2690 Say Y here if you want to use Direct Cache Access (DCA) in the 2691 driver. DCA is a method for warming the CPU cache before data 2692 is used, with the intent of lessening the impact of cache misses. 2693 2694config NETXEN_NIC 2695 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" 2696 depends on PCI 2697 help 2698 This enables the support for NetXen's Gigabit Ethernet card. 2699 2700config NIU 2701 tristate "Sun Neptune 10Gbit Ethernet support" 2702 depends on PCI 2703 select CRC32 2704 help 2705 This enables support for cards based upon Sun's 2706 Neptune chipset. 2707 2708config PASEMI_MAC 2709 tristate "PA Semi 1/10Gbit MAC" 2710 depends on PPC_PASEMI && PCI 2711 select PHYLIB 2712 select INET_LRO 2713 help 2714 This driver supports the on-chip 1/10Gbit Ethernet controller on 2715 PA Semi's PWRficient line of chips. 2716 2717config MLX4_EN 2718 tristate "Mellanox Technologies 10Gbit Ethernet support" 2719 depends on PCI && INET 2720 select MLX4_CORE 2721 select INET_LRO 2722 help 2723 This driver supports Mellanox Technologies ConnectX Ethernet 2724 devices. 2725 2726config MLX4_CORE 2727 tristate 2728 depends on PCI 2729 default n 2730 2731config MLX4_DEBUG 2732 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED) 2733 depends on MLX4_CORE 2734 default y 2735 ---help--- 2736 This option causes debugging code to be compiled into the 2737 mlx4_core driver. The output can be turned on via the 2738 debug_level module parameter (which can also be set after 2739 the driver is loaded through sysfs). 2740 2741config TEHUTI 2742 tristate "Tehuti Networks 10G Ethernet" 2743 depends on PCI 2744 help 2745 Tehuti Networks 10G Ethernet NIC 2746 2747config BNX2X 2748 tristate "Broadcom NetXtremeII 10Gb support" 2749 depends on PCI 2750 select FW_LOADER 2751 select ZLIB_INFLATE 2752 select LIBCRC32C 2753 select MDIO 2754 help 2755 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. 2756 To compile this driver as a module, choose M here: the module 2757 will be called bnx2x. This is recommended. 2758 2759config QLGE 2760 tristate "QLogic QLGE 10Gb Ethernet Driver Support" 2761 depends on PCI 2762 help 2763 This driver supports QLogic ISP8XXX 10Gb Ethernet cards. 2764 2765 To compile this driver as a module, choose M here: the module 2766 will be called qlge. 2767 2768source "drivers/net/sfc/Kconfig" 2769 2770source "drivers/net/benet/Kconfig" 2771 2772endif # NETDEV_10000 2773 2774source "drivers/net/tokenring/Kconfig" 2775 2776source "drivers/net/wireless/Kconfig" 2777 2778source "drivers/net/wimax/Kconfig" 2779 2780source "drivers/net/usb/Kconfig" 2781 2782source "drivers/net/pcmcia/Kconfig" 2783 2784source "drivers/net/wan/Kconfig" 2785 2786source "drivers/atm/Kconfig" 2787 2788source "drivers/ieee802154/Kconfig" 2789 2790source "drivers/s390/net/Kconfig" 2791 2792config XEN_NETDEV_FRONTEND 2793 tristate "Xen network device frontend driver" 2794 depends on XEN 2795 default y 2796 help 2797 The network device frontend driver allows the kernel to 2798 access network devices exported exported by a virtual 2799 machine containing a physical network device driver. The 2800 frontend driver is intended for unprivileged guest domains; 2801 if you are compiling a kernel for a Xen guest, you almost 2802 certainly want to enable this. 2803 2804config ISERIES_VETH 2805 tristate "iSeries Virtual Ethernet driver support" 2806 depends on PPC_ISERIES 2807 2808config RIONET 2809 tristate "RapidIO Ethernet over messaging driver support" 2810 depends on RAPIDIO 2811 2812config RIONET_TX_SIZE 2813 int "Number of outbound queue entries" 2814 depends on RIONET 2815 default "128" 2816 2817config RIONET_RX_SIZE 2818 int "Number of inbound queue entries" 2819 depends on RIONET 2820 default "128" 2821 2822config FDDI 2823 tristate "FDDI driver support" 2824 depends on (PCI || EISA || TC) 2825 help 2826 Fiber Distributed Data Interface is a high speed local area network 2827 design; essentially a replacement for high speed Ethernet. FDDI can 2828 run over copper or fiber. If you are connected to such a network and 2829 want a driver for the FDDI card in your computer, say Y here (and 2830 then also Y to the driver for your FDDI card, below). Most people 2831 will say N. 2832 2833config DEFXX 2834 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 2835 depends on FDDI && (PCI || EISA || TC) 2836 ---help--- 2837 This is support for the DIGITAL series of TURBOchannel (DEFTA), 2838 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 2839 to a local FDDI network. 2840 2841 To compile this driver as a module, choose M here: the module 2842 will be called defxx. If unsure, say N. 2843 2844config DEFXX_MMIO 2845 bool 2846 prompt "Use MMIO instead of PIO" if PCI || EISA 2847 depends on DEFXX 2848 default n if PCI || EISA 2849 default y 2850 ---help--- 2851 This instructs the driver to use EISA or PCI memory-mapped I/O 2852 (MMIO) as appropriate instead of programmed I/O ports (PIO). 2853 Enabling this gives an improvement in processing time in parts 2854 of the driver, but it may cause problems with EISA (DEFEA) 2855 adapters. TURBOchannel does not have the concept of I/O ports, 2856 so MMIO is always used for these (DEFTA) adapters. 2857 2858 If unsure, say N. 2859 2860config SKFP 2861 tristate "SysKonnect FDDI PCI support" 2862 depends on FDDI && PCI 2863 select BITREVERSE 2864 ---help--- 2865 Say Y here if you have a SysKonnect FDDI PCI adapter. 2866 The following adapters are supported by this driver: 2867 - SK-5521 (SK-NET FDDI-UP) 2868 - SK-5522 (SK-NET FDDI-UP DAS) 2869 - SK-5541 (SK-NET FDDI-FP) 2870 - SK-5543 (SK-NET FDDI-LP) 2871 - SK-5544 (SK-NET FDDI-LP DAS) 2872 - SK-5821 (SK-NET FDDI-UP64) 2873 - SK-5822 (SK-NET FDDI-UP64 DAS) 2874 - SK-5841 (SK-NET FDDI-FP64) 2875 - SK-5843 (SK-NET FDDI-LP64) 2876 - SK-5844 (SK-NET FDDI-LP64 DAS) 2877 - Netelligent 100 FDDI DAS Fibre SC 2878 - Netelligent 100 FDDI SAS Fibre SC 2879 - Netelligent 100 FDDI DAS UTP 2880 - Netelligent 100 FDDI SAS UTP 2881 - Netelligent 100 FDDI SAS Fibre MIC 2882 2883 Read <file:Documentation/networking/skfp.txt> for information about 2884 the driver. 2885 2886 Questions concerning this driver can be addressed to: 2887 <linux@syskonnect.de> 2888 2889 To compile this driver as a module, choose M here: the module 2890 will be called skfp. This is recommended. 2891 2892config HIPPI 2893 bool "HIPPI driver support (EXPERIMENTAL)" 2894 depends on EXPERIMENTAL && INET && PCI 2895 help 2896 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 2897 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 2898 can run over copper (25m) or fiber (300m on multi-mode or 10km on 2899 single-mode). HIPPI networks are commonly used for clusters and to 2900 connect to super computers. If you are connected to a HIPPI network 2901 and have a HIPPI network card in your computer that you want to use 2902 under Linux, say Y here (you must also remember to enable the driver 2903 for your HIPPI card below). Most people will say N here. 2904 2905config ROADRUNNER 2906 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 2907 depends on HIPPI && PCI 2908 help 2909 Say Y here if this is your PCI HIPPI network card. 2910 2911 To compile this driver as a module, choose M here: the module 2912 will be called rrunner. If unsure, say N. 2913 2914config ROADRUNNER_LARGE_RINGS 2915 bool "Use large TX/RX rings (EXPERIMENTAL)" 2916 depends on ROADRUNNER 2917 help 2918 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 2919 of additional memory to allow for fastest operation, both for 2920 transmitting and receiving. This memory cannot be used by any other 2921 kernel code or by user space programs. Say Y here only if you have 2922 the memory. 2923 2924config PLIP 2925 tristate "PLIP (parallel port) support" 2926 depends on PARPORT 2927 ---help--- 2928 PLIP (Parallel Line Internet Protocol) is used to create a 2929 reasonably fast mini network consisting of two (or, rarely, more) 2930 local machines. A PLIP link from a Linux box is a popular means to 2931 install a Linux distribution on a machine which doesn't have a 2932 CD-ROM drive (a minimal system has to be transferred with floppies 2933 first). The kernels on both machines need to have this PLIP option 2934 enabled for this to work. 2935 2936 The PLIP driver has two modes, mode 0 and mode 1. The parallel 2937 ports (the connectors at the computers with 25 holes) are connected 2938 with "null printer" or "Turbo Laplink" cables which can transmit 4 2939 bits at a time (mode 0) or with special PLIP cables, to be used on 2940 bidirectional parallel ports only, which can transmit 8 bits at a 2941 time (mode 1); you can find the wiring of these cables in 2942 <file:Documentation/networking/PLIP.txt>. The cables can be up to 2943 15m long. Mode 0 works also if one of the machines runs DOS/Windows 2944 and has some PLIP software installed, e.g. the Crynwr PLIP packet 2945 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 2946 and winsock or NCSA's telnet. 2947 2948 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 2949 as the NET-3-HOWTO, both available from 2950 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 2951 protocol has been changed and this PLIP driver won't work together 2952 with the PLIP support in Linux versions 1.0.x. This option enlarges 2953 your kernel by about 8 KB. 2954 2955 To compile this driver as a module, choose M here. The module 2956 will be called plip. If unsure, say Y or M, in case you buy 2957 a laptop later. 2958 2959config PPP 2960 tristate "PPP (point-to-point protocol) support" 2961 select SLHC 2962 ---help--- 2963 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 2964 the same purpose: sending Internet traffic over telephone (and other 2965 serial) lines. Ask your access provider if they support it, because 2966 otherwise you can't use it; most Internet access providers these 2967 days support PPP rather than SLIP. 2968 2969 To use PPP, you need an additional program called pppd as described 2970 in the PPP-HOWTO, available at 2971 <http://www.tldp.org/docs.html#howto>. Make sure that you have 2972 the version of pppd recommended in <file:Documentation/Changes>. 2973 The PPP option enlarges your kernel by about 16 KB. 2974 2975 There are actually two versions of PPP: the traditional PPP for 2976 asynchronous lines, such as regular analog phone lines, and 2977 synchronous PPP which can be used over digital ISDN lines for 2978 example. If you want to use PPP over phone lines or other 2979 asynchronous serial lines, you need to say Y (or M) here and also to 2980 the next option, "PPP support for async serial ports". For PPP over 2981 synchronous lines, you should say Y (or M) here and to "Support 2982 synchronous PPP", below. 2983 2984 If you said Y to "Version information on all symbols" above, then 2985 you cannot compile the PPP driver into the kernel; you can then only 2986 compile it as a module. To compile this driver as a module, choose M 2987 here. The module will be called ppp_generic. 2988 2989config PPP_MULTILINK 2990 bool "PPP multilink support (EXPERIMENTAL)" 2991 depends on PPP && EXPERIMENTAL 2992 help 2993 PPP multilink is a protocol (defined in RFC 1990) which allows you 2994 to combine several (logical or physical) lines into one logical PPP 2995 connection, so that you can utilize your full bandwidth. 2996 2997 This has to be supported at the other end as well and you need a 2998 version of the pppd daemon which understands the multilink protocol. 2999 3000 If unsure, say N.
3001 3002config PPP_FILTER 3003 bool "PPP filtering" 3004 depends on PPP 3005 help 3006 Say Y here if you want to be able to filter the packets passing over 3007 PPP interfaces. This allows you to control which packets count as 3008 activity (i.e. which packets will reset the idle timer or bring up 3009 a demand-dialed link) and which packets are to be dropped entirely. 3010 You need to say Y here if you wish to use the pass-filter and 3011 active-filter options to pppd. 3012 3013 If unsure, say N. 3014 3015config PPP_ASYNC 3016 tristate "PPP support for async serial ports" 3017 depends on PPP 3018 select CRC_CCITT 3019 ---help--- 3020 Say Y (or M) here if you want to be able to use PPP over standard 3021 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 3022 a modem (not a synchronous or ISDN modem) to contact your ISP, you 3023 need this option. 3024 3025 To compile this driver as a module, choose M here. 3026 3027 If unsure, say Y. 3028 3029config PPP_SYNC_TTY 3030 tristate "PPP support for sync tty ports" 3031 depends on PPP 3032 help 3033 Say Y (or M) here if you want to be able to use PPP over synchronous 3034 (HDLC) tty devices, such as the SyncLink adapter. These devices 3035 are often used for high-speed leased lines like T1/E1. 3036 3037 To compile this driver as a module, choose M here. 3038 3039config PPP_DEFLATE 3040 tristate "PPP Deflate compression" 3041 depends on PPP 3042 select ZLIB_INFLATE 3043 select ZLIB_DEFLATE 3044 ---help--- 3045 Support for the Deflate compression method for PPP, which uses the 3046 Deflate algorithm (the same algorithm that gzip uses) to compress 3047 each PPP packet before it is sent over the wire. The machine at the 3048 other end of the PPP link (usually your ISP) has to support the 3049 Deflate compression method as well for this to be useful. Even if 3050 they don't support it, it is safe to say Y here. 3051 3052 To compile this driver as a module, choose M here. 3053 3054config PPP_BSDCOMP 3055 tristate "PPP BSD-Compress compression" 3056 depends on PPP 3057 ---help--- 3058 Support for the BSD-Compress compression method for PPP, which uses 3059 the LZW compression method to compress each PPP packet before it is 3060 sent over the wire. The machine at the other end of the PPP link 3061 (usually your ISP) has to support the BSD-Compress compression 3062 method as well for this to be useful. Even if they don't support it, 3063 it is safe to say Y here. 3064 3065 The PPP Deflate compression method ("PPP Deflate compression", 3066 above) is preferable to BSD-Compress, because it compresses better 3067 and is patent-free. 3068 3069 Note that the BSD compression code will always be compiled as a 3070 module; it is called bsd_comp and will show up in the directory 3071 modules once you have said "make modules". If unsure, say N. 3072 3073config PPP_MPPE 3074 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 3075 depends on PPP && EXPERIMENTAL 3076 select CRYPTO 3077 select CRYPTO_SHA1 3078 select CRYPTO_ARC4 3079 select CRYPTO_ECB 3080 ---help--- 3081 Support for the MPPE Encryption protocol, as employed by the 3082 Microsoft Point-to-Point Tunneling Protocol. 3083 3084 See http://pptpclient.sourceforge.net/ for information on 3085 configuring PPTP clients and servers to utilize this method. 3086 3087config PPPOE 3088 tristate "PPP over Ethernet (EXPERIMENTAL)" 3089 depends on EXPERIMENTAL && PPP 3090 help 3091 Support for PPP over Ethernet. 3092 3093 This driver requires the latest version of pppd from the CVS 3094 repository at cvs.samba.org. Alternatively, see the 3095 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 3096 which contains instruction on how to use this driver (under 3097 the heading "Kernel mode PPPoE"). 3098 3099config PPPOATM 3100 tristate "PPP over ATM" 3101 depends on ATM && PPP 3102 help 3103 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 3104 This implementation does not yet comply with section 8 of RFC2364, 3105 which can lead to bad results if the ATM peer loses state and 3106 changes its encapsulation unilaterally. 3107 3108config PPPOL2TP 3109 tristate "PPP over L2TP (EXPERIMENTAL)" 3110 depends on EXPERIMENTAL && PPP && INET 3111 help 3112 Support for PPP-over-L2TP socket family. L2TP is a protocol 3113 used by ISPs and enterprises to tunnel PPP traffic over UDP 3114 tunnels. L2TP is replacing PPTP for VPN uses. 3115 3116 This kernel component handles only L2TP data packets: a 3117 userland daemon handles L2TP the control protocol (tunnel 3118 and session setup). One such daemon is OpenL2TP 3119 (http://openl2tp.sourceforge.net/). 3120 3121config SLIP 3122 tristate "SLIP (serial line) support" 3123 ---help--- 3124 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 3125 connect to your Internet service provider or to connect to some 3126 other local Unix box or if you want to configure your Linux box as a 3127 Slip/CSlip server for other people to dial in. SLIP (Serial Line 3128 Internet Protocol) is a protocol used to send Internet traffic over 3129 serial connections such as telephone lines or null modem cables; 3130 nowadays, the protocol PPP is more commonly used for this same 3131 purpose. 3132 3133 Normally, your access provider has to support SLIP in order for you 3134 to be able to use it, but there is now a SLIP emulator called SLiRP 3135 around (available from 3136 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3137 allows you to use SLIP over a regular dial up shell connection. If 3138 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 3139 NET-3-HOWTO, available from 3140 <http://www.tldp.org/docs.html#howto>, explains how to 3141 configure SLIP. Note that you don't need this option if you just 3142 want to run term (term is a program which gives you almost full 3143 Internet connectivity if you have a regular dial up shell account on 3144 some Internet connected Unix computer. Read 3145 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 3146 support will enlarge your kernel by about 4 KB. If unsure, say N. 3147 3148 To compile this driver as a module, choose M here. The module 3149 will be called slip. 3150 3151config SLIP_COMPRESSED 3152 bool "CSLIP compressed headers" 3153 depends on SLIP 3154 select SLHC 3155 ---help--- 3156 This protocol is faster than SLIP because it uses compression on the 3157 TCP/IP headers (not on the data itself), but it has to be supported 3158 on both ends. Ask your access provider if you are not sure and 3159 answer Y, just in case. You will still be able to use plain SLIP. If 3160 you plan to use SLiRP, the SLIP emulator (available from 3161 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3162 allows you to use SLIP over a regular dial up shell connection, you 3163 definitely want to say Y here. The NET-3-HOWTO, available from 3164 <http://www.tldp.org/docs.html#howto>, explains how to configure 3165 CSLIP. This won't enlarge your kernel. 3166 3167config SLHC 3168 tristate 3169 help 3170 This option enables Van Jacobsen serial line header compression 3171 routines. 3172 3173config SLIP_SMART 3174 bool "Keepalive and linefill" 3175 depends on SLIP 3176 help 3177 Adds additional capabilities to the SLIP driver to support the 3178 RELCOM line fill and keepalive monitoring. Ideal on poor quality 3179 analogue lines. 3180 3181config SLIP_MODE_SLIP6 3182 bool "Six bit SLIP encapsulation" 3183 depends on SLIP 3184 help 3185 Just occasionally you may need to run IP over hostile serial 3186 networks that don't pass all control characters or are only seven 3187 bit. Saying Y here adds an extra mode you can use with SLIP: 3188 "slip6". In this mode, SLIP will only send normal ASCII symbols over 3189 the serial device. Naturally, this has to be supported at the other 3190 end of the link as well. It's good enough, for example, to run IP 3191 over the async ports of a Camtec JNT Pad. If unsure, say N. 3192 3193config NET_FC 3194 bool "Fibre Channel driver support" 3195 depends on SCSI && PCI 3196 help 3197 Fibre Channel is a high speed serial protocol mainly used to connect 3198 large storage devices to the computer; it is compatible with and 3199 intended to replace SCSI. 3200 3201 If you intend to use Fibre Channel, you need to have a Fibre channel 3202 adaptor card in your computer; say Y here and to the driver for your 3203 adaptor below. You also should have said Y to "SCSI support" and 3204 "SCSI generic support". 3205 3206config NETCONSOLE 3207 tristate "Network console logging support (EXPERIMENTAL)" 3208 depends on EXPERIMENTAL 3209 ---help--- 3210 If you want to log kernel messages over the network, enable this. 3211 See <file:Documentation/networking/netconsole.txt> for details. 3212 3213config NETCONSOLE_DYNAMIC 3214 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)" 3215 depends on NETCONSOLE && SYSFS && EXPERIMENTAL 3216 select CONFIGFS_FS 3217 help 3218 This option enables the ability to dynamically reconfigure target 3219 parameters (interface, IP addresses, port numbers, MAC addresses) 3220 at runtime through a userspace interface exported using configfs. 3221 See <file:Documentation/networking/netconsole.txt> for details. 3222 3223config NETPOLL 3224 def_bool NETCONSOLE 3225 3226config NETPOLL_TRAP 3227 bool "Netpoll traffic trapping" 3228 default n 3229 depends on NETPOLL 3230 3231config NET_POLL_CONTROLLER 3232 def_bool NETPOLL 3233 3234config VIRTIO_NET 3235 tristate "Virtio network driver (EXPERIMENTAL)" 3236 depends on EXPERIMENTAL && VIRTIO 3237 ---help--- 3238 This is the virtual network driver for virtio. It can be used with 3239 lguest or QEMU based VMMs (like KVM or Xen). Say Y or M. 3240 3241config VMXNET3 3242 tristate "VMware VMXNET3 ethernet driver" 3243 depends on PCI && INET 3244 help 3245 This driver supports VMware's vmxnet3 virtual ethernet NIC. 3246 To compile this driver as a module, choose M here: the 3247 module will be called vmxnet3. 3248 3249endif # NETDEVICES 3250