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