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