Kconfig revision 5b10ca19ea4859d3884d10a3eb8495de92089792
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 536/537 on-chip mac support" 818 depends on NET_ETHERNET && (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 && 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 n 859 help 860 Use Reduced PHY MII Interface 861 862config SMC9194 863 tristate "SMC 9194 support" 864 depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN) 865 select CRC32 866 ---help--- 867 This is support for the SMC9xxx based Ethernet cards. Choose this 868 option if you have a DELL laptop with the docking station, or 869 another SMC9192/9194 based chipset. Say Y if you want it compiled 870 into the kernel, and read the file 871 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 872 available from <http://www.tldp.org/docs.html#howto>. 873 874 To compile this driver as a module, choose M here. The module 875 will be called smc9194. 876 877config SMC91X 878 tristate "SMC 91C9x/91C1xxx support" 879 select CRC32 880 select MII 881 depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || SOC_AU1X00 || BLACKFIN 882 help 883 This is a driver for SMC's 91x series of Ethernet chipsets, 884 including the SMC91C94 and the SMC91C111. Say Y if you want it 885 compiled into the kernel, and read the file 886 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO, 887 available from <http://www.linuxdoc.org/docs.html#howto>. 888 889 This driver is also available as a module ( = code which can be 890 inserted in and removed from the running kernel whenever you want). 891 The module will be called smc91x. If you want to compile it as a 892 module, say M here and read <file:Documentation/kbuild/modules.txt>. 893 894config NET_NETX 895 tristate "NetX Ethernet support" 896 select MII 897 depends on ARCH_NETX 898 help 899 This is support for the Hilscher netX builtin Ethernet ports 900 901 To compile this driver as a module, choose M here. The module 902 will be called netx-eth. 903 904config DM9000 905 tristate "DM9000 support" 906 depends on ARM || BLACKFIN || MIPS 907 select CRC32 908 select MII 909 ---help--- 910 Support for DM9000 chipset. 911 912 To compile this driver as a module, choose M here. The module 913 will be called dm9000. 914 915config ENC28J60 916 tristate "ENC28J60 support" 917 depends on EXPERIMENTAL && SPI && NET_ETHERNET 918 select CRC32 919 ---help--- 920 Support for the Microchip EN28J60 ethernet chip. 921 922 To compile this driver as a module, choose M here and read 923 <file:Documentation/networking/net-modules.txt>. The module will be 924 called enc28j60. 925 926config ENC28J60_WRITEVERIFY 927 bool "Enable write verify" 928 depends on ENC28J60 929 ---help--- 930 Enable the verify after the buffer write useful for debugging purpose. 931 If unsure, say N. 932 933config SMC911X 934 tristate "SMSC LAN911[5678] support" 935 select CRC32 936 select MII 937 depends on ARCH_PXA || SH_MAGIC_PANEL_R2 938 help 939 This is a driver for SMSC's LAN911x series of Ethernet chipsets 940 including the new LAN9115, LAN9116, LAN9117, and LAN9118. 941 Say Y if you want it compiled into the kernel, 942 and read the Ethernet-HOWTO, available from 943 <http://www.linuxdoc.org/docs.html#howto>. 944 945 This driver is also available as a module. The module will be 946 called smc911x. If you want to compile it as a module, say M 947 here and read <file:Documentation/kbuild/modules.txt> 948 949config NET_VENDOR_RACAL 950 bool "Racal-Interlan (Micom) NI cards" 951 depends on ISA 952 help 953 If you have a network (Ethernet) card belonging to this class, such 954 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO, 955 available from <http://www.tldp.org/docs.html#howto>. 956 957 Note that the answer to this question doesn't directly affect the 958 kernel: saying N will just cause the configurator to skip all 959 the questions about NI cards. If you say Y, you will be asked for 960 your specific card in the following questions. 961 962config NI5010 963 tristate "NI5010 support (EXPERIMENTAL)" 964 depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP 965 ---help--- 966 If you have a network (Ethernet) card of this type, say Y and read 967 the Ethernet-HOWTO, available from 968 <http://www.tldp.org/docs.html#howto>. Note that this is still 969 experimental code. 970 971 To compile this driver as a module, choose M here. The module 972 will be called ni5010. 973 974config NI52 975 tristate "NI5210 support" 976 depends on NET_VENDOR_RACAL && ISA 977 help 978 If you have a network (Ethernet) card of this type, say Y and read 979 the Ethernet-HOWTO, available from 980 <http://www.tldp.org/docs.html#howto>. 981 982 To compile this driver as a module, choose M here. The module 983 will be called ni52. 984 985config NI65 986 tristate "NI6510 support" 987 depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API 988 help 989 If you have a network (Ethernet) card of this type, say Y and read 990 the Ethernet-HOWTO, available from 991 <http://www.tldp.org/docs.html#howto>. 992 993 To compile this driver as a module, choose M here. The module 994 will be called ni65. 995 996source "drivers/net/tulip/Kconfig" 997 998config AT1700 999 tristate "AT1700/1720 support (EXPERIMENTAL)" 1000 depends on (ISA || MCA_LEGACY) && EXPERIMENTAL 1001 select CRC32 1002 ---help--- 1003 If you have a network (Ethernet) card of this type, say Y and read 1004 the Ethernet-HOWTO, available from 1005 <http://www.tldp.org/docs.html#howto>. 1006 1007 To compile this driver as a module, choose M here. The module 1008 will be called at1700. 1009 1010config DEPCA 1011 tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support" 1012 depends on ISA || EISA || MCA 1013 select CRC32 1014 ---help--- 1015 If you have a network (Ethernet) card of this type, say Y and read 1016 the Ethernet-HOWTO, available from 1017 <http://www.tldp.org/docs.html#howto> as well as 1018 <file:drivers/net/depca.c>. 1019 1020 To compile this driver as a module, choose M here. The module 1021 will be called depca. 1022 1023config HP100 1024 tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support" 1025 depends on ISA || EISA || PCI 1026 help 1027 If you have a network (Ethernet) card of this type, say Y and read 1028 the Ethernet-HOWTO, available from 1029 <http://www.tldp.org/docs.html#howto>. 1030 1031 To compile this driver as a module, choose M here. The module 1032 will be called hp100. 1033 1034config NET_ISA 1035 bool "Other ISA cards" 1036 depends on ISA 1037 ---help--- 1038 If your network (Ethernet) card hasn't been mentioned yet and its 1039 bus system (that's the way the cards talks to the other components 1040 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y. 1041 Make sure you know the name of your card. Read the Ethernet-HOWTO, 1042 available from <http://www.tldp.org/docs.html#howto>. 1043 1044 If unsure, say Y. 1045 1046 Note that the answer to this question doesn't directly affect the 1047 kernel: saying N will just cause the configurator to skip all 1048 the remaining ISA network card questions. If you say Y, you will be 1049 asked for your specific card in the following questions. 1050 1051config E2100 1052 tristate "Cabletron E21xx support" 1053 depends on NET_ISA 1054 select CRC32 1055 help 1056 If you have a network (Ethernet) card of this type, say Y and read 1057 the Ethernet-HOWTO, available from 1058 <http://www.tldp.org/docs.html#howto>. 1059 1060 To compile this driver as a module, choose M here. The module 1061 will be called e2100. 1062 1063config EWRK3 1064 tristate "EtherWORKS 3 (DE203, DE204, DE205) support" 1065 depends on NET_ISA 1066 select CRC32 1067 ---help--- 1068 This driver supports the DE203, DE204 and DE205 network (Ethernet) 1069 cards. If this is for you, say Y and read 1070 <file:Documentation/networking/ewrk3.txt> in the kernel source as 1071 well as the Ethernet-HOWTO, available from 1072 <http://www.tldp.org/docs.html#howto>. 1073 1074 To compile this driver as a module, choose M here. The module 1075 will be called ewrk3. 1076 1077config EEXPRESS 1078 tristate "EtherExpress 16 support" 1079 depends on NET_ISA 1080 ---help--- 1081 If you have an EtherExpress16 network (Ethernet) card, say Y and 1082 read the Ethernet-HOWTO, available from 1083 <http://www.tldp.org/docs.html#howto>. Note that the Intel 1084 EtherExpress16 card used to be regarded as a very poor choice 1085 because the driver was very unreliable. We now have a new driver 1086 that should do better. 1087 1088 To compile this driver as a module, choose M here. The module 1089 will be called eexpress. 1090 1091config EEXPRESS_PRO 1092 tristate "EtherExpressPro support/EtherExpress 10 (i82595) support" 1093 depends on NET_ISA 1094 ---help--- 1095 If you have a network (Ethernet) card of this type, say Y. This 1096 driver supports Intel i82595{FX,TX} based boards. Note however 1097 that the EtherExpress PRO/100 Ethernet card has its own separate 1098 driver. Please read the Ethernet-HOWTO, available from 1099 <http://www.tldp.org/docs.html#howto>. 1100 1101 To compile this driver as a module, choose M here. The module 1102 will be called eepro. 1103 1104config HPLAN_PLUS 1105 tristate "HP PCLAN+ (27247B and 27252A) support" 1106 depends on NET_ISA 1107 select CRC32 1108 help 1109 If you have a network (Ethernet) card of this type, say Y and read 1110 the Ethernet-HOWTO, available from 1111 <http://www.tldp.org/docs.html#howto>. 1112 1113 To compile this driver as a module, choose M here. The module 1114 will be called hp-plus. 1115 1116config HPLAN 1117 tristate "HP PCLAN (27245 and other 27xxx series) support" 1118 depends on NET_ISA 1119 select CRC32 1120 help 1121 If you have a network (Ethernet) card of this type, say Y and read 1122 the Ethernet-HOWTO, available from 1123 <http://www.tldp.org/docs.html#howto>. 1124 1125 To compile this driver as a module, choose M here. The module 1126 will be called hp. 1127 1128config LP486E 1129 tristate "LP486E on board Ethernet" 1130 depends on NET_ISA 1131 help 1132 Say Y here to support the 82596-based on-board Ethernet controller 1133 for the Panther motherboard, which is one of the two shipped in the 1134 Intel Professional Workstation. 1135 1136config ETH16I 1137 tristate "ICL EtherTeam 16i/32 support" 1138 depends on NET_ISA 1139 help 1140 If you have a network (Ethernet) card of this type, say Y and read 1141 the Ethernet-HOWTO, available from 1142 <http://www.tldp.org/docs.html#howto>. 1143 1144 To compile this driver as a module, choose M here. The module 1145 will be called eth16i. 1146 1147config NE2000 1148 tristate "NE2000/NE1000 support" 1149 depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938 1150 select CRC32 1151 ---help--- 1152 If you have a network (Ethernet) card of this type, say Y and read 1153 the Ethernet-HOWTO, available from 1154 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards 1155 without a specific driver are compatible with NE2000. 1156 1157 If you have a PCI NE2000 card however, say N here and Y to "PCI 1158 NE2000 and clone support" under "EISA, VLB, PCI and on board 1159 controllers" below. If you have a NE2000 card and are running on 1160 an MCA system (a bus system used on some IBM PS/2 computers and 1161 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support", 1162 below. 1163 1164 To compile this driver as a module, choose M here. The module 1165 will be called ne. 1166 1167config ZNET 1168 tristate "Zenith Z-Note support (EXPERIMENTAL)" 1169 depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API 1170 help 1171 The Zenith Z-Note notebook computer has a built-in network 1172 (Ethernet) card, and this is the Linux driver for it. Note that the 1173 IBM Thinkpad 300 is compatible with the Z-Note and is also supported 1174 by this driver. Read the Ethernet-HOWTO, available from 1175 <http://www.tldp.org/docs.html#howto>. 1176 1177config SEEQ8005 1178 tristate "SEEQ8005 support (EXPERIMENTAL)" 1179 depends on NET_ISA && EXPERIMENTAL 1180 help 1181 This is a driver for the SEEQ 8005 network (Ethernet) card. If this 1182 is for you, read the Ethernet-HOWTO, available from 1183 <http://www.tldp.org/docs.html#howto>. 1184 1185 To compile this driver as a module, choose M here. The module 1186 will be called seeq8005. 1187 1188config NE2_MCA 1189 tristate "NE/2 (ne2000 MCA version) support" 1190 depends on MCA_LEGACY 1191 select CRC32 1192 help 1193 If you have a network (Ethernet) card of this type, say Y and read 1194 the Ethernet-HOWTO, available from 1195 <http://www.tldp.org/docs.html#howto>. 1196 1197 To compile this driver as a module, choose M here. The module 1198 will be called ne2. 1199 1200config IBMLANA 1201 tristate "IBM LAN Adapter/A support" 1202 depends on MCA && MCA_LEGACY 1203 ---help--- 1204 This is a Micro Channel Ethernet adapter. You need to set 1205 CONFIG_MCA to use this driver. It is both available as an in-kernel 1206 driver and as a module. 1207 1208 To compile this driver as a module, choose M here. The only 1209 currently supported card is the IBM LAN Adapter/A for Ethernet. It 1210 will both support 16K and 32K memory windows, however a 32K window 1211 gives a better security against packet losses. Usage of multiple 1212 boards with this driver should be possible, but has not been tested 1213 up to now due to lack of hardware. 1214 1215config IBMVETH 1216 tristate "IBM LAN Virtual Ethernet support" 1217 depends on PPC_PSERIES 1218 ---help--- 1219 This driver supports virtual ethernet adapters on newer IBM iSeries 1220 and pSeries systems. 1221 1222 To compile this driver as a module, choose M here. The module will 1223 be called ibmveth. 1224 1225source "drivers/net/ibm_emac/Kconfig" 1226source "drivers/net/ibm_newemac/Kconfig" 1227 1228config NET_PCI 1229 bool "EISA, VLB, PCI and on board controllers" 1230 depends on ISA || EISA || PCI 1231 help 1232 This is another class of network cards which attach directly to the 1233 bus. If you have one of those, say Y and read the Ethernet-HOWTO, 1234 available from <http://www.tldp.org/docs.html#howto>. 1235 1236 Note that the answer to this question doesn't directly affect the 1237 kernel: saying N will just cause the configurator to skip all 1238 the questions about this class of network cards. If you say Y, you 1239 will be asked for your specific card in the following questions. If 1240 you are unsure, say Y. 1241 1242config PCNET32 1243 tristate "AMD PCnet32 PCI support" 1244 depends on NET_PCI && PCI 1245 select CRC32 1246 select MII 1247 help 1248 If you have a PCnet32 or PCnetPCI based network (Ethernet) card, 1249 answer Y here and read the Ethernet-HOWTO, available from 1250 <http://www.tldp.org/docs.html#howto>. 1251 1252 To compile this driver as a module, choose M here. The module 1253 will be called pcnet32. 1254 1255config PCNET32_NAPI 1256 bool "Use RX polling (NAPI)" 1257 depends on PCNET32 1258 help 1259 NAPI is a new driver API designed to reduce CPU and interrupt load 1260 when the driver is receiving lots of packets from the card. It is 1261 still somewhat experimental and thus not yet enabled by default. 1262 1263 If your estimated Rx load is 10kpps or more, or if the card will be 1264 deployed on potentially unfriendly networks (e.g. in a firewall), 1265 then say Y here. 1266 1267 If in doubt, say N. 1268 1269config AMD8111_ETH 1270 tristate "AMD 8111 (new PCI lance) support" 1271 depends on NET_PCI && PCI 1272 select CRC32 1273 select MII 1274 help 1275 If you have an AMD 8111-based PCI lance ethernet card, 1276 answer Y here and read the Ethernet-HOWTO, available from 1277 <http://www.tldp.org/docs.html#howto>. 1278 1279 To compile this driver as a module, choose M here. The module 1280 will be called amd8111e. 1281 1282config AMD8111E_NAPI 1283 bool "Use RX polling (NAPI)" 1284 depends on AMD8111_ETH 1285 help 1286 NAPI is a new driver API designed to reduce CPU and interrupt load 1287 when the driver is receiving lots of packets from the card. It is 1288 still somewhat experimental and thus not yet enabled by default. 1289 1290 If your estimated Rx load is 10kpps or more, or if the card will be 1291 deployed on potentially unfriendly networks (e.g. in a firewall), 1292 then say Y here. 1293 1294 If in doubt, say N. 1295 1296config ADAPTEC_STARFIRE 1297 tristate "Adaptec Starfire/DuraLAN support" 1298 depends on NET_PCI && PCI 1299 select CRC32 1300 select MII 1301 help 1302 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network 1303 adapter. The DuraLAN chip is used on the 64 bit PCI boards from 1304 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip 1305 driver. 1306 1307 To compile this driver as a module, choose M here: the module 1308 will be called starfire. This is recommended. 1309 1310config ADAPTEC_STARFIRE_NAPI 1311 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 1312 depends on ADAPTEC_STARFIRE && EXPERIMENTAL 1313 help 1314 NAPI is a new driver API designed to reduce CPU and interrupt load 1315 when the driver is receiving lots of packets from the card. It is 1316 still somewhat experimental and thus not yet enabled by default. 1317 1318 If your estimated Rx load is 10kpps or more, or if the card will be 1319 deployed on potentially unfriendly networks (e.g. in a firewall), 1320 then say Y here. 1321 1322 If in doubt, say N. 1323 1324config AC3200 1325 tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)" 1326 depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL 1327 select CRC32 1328 help 1329 If you have a network (Ethernet) card of this type, say Y and read 1330 the Ethernet-HOWTO, available from 1331 <http://www.tldp.org/docs.html#howto>. 1332 1333 To compile this driver as a module, choose M here. The module 1334 will be called ac3200. 1335 1336config APRICOT 1337 tristate "Apricot Xen-II on board Ethernet" 1338 depends on NET_PCI && ISA 1339 help 1340 If you have a network (Ethernet) controller of this type, say Y and 1341 read the Ethernet-HOWTO, available from 1342 <http://www.tldp.org/docs.html#howto>. 1343 1344 To compile this driver as a module, choose M here. The module 1345 will be called apricot. 1346 1347config B44 1348 tristate "Broadcom 440x/47xx ethernet support" 1349 depends on SSB_POSSIBLE 1350 select SSB 1351 select MII 1352 help 1353 If you have a network (Ethernet) controller of this type, say Y 1354 or M and read the Ethernet-HOWTO, available from 1355 <http://www.tldp.org/docs.html#howto>. 1356 1357 To compile this driver as a module, choose M here. The module 1358 will be called b44. 1359 1360# Auto-select SSB PCI-HOST support, if possible 1361config B44_PCI_AUTOSELECT 1362 bool 1363 depends on B44 && SSB_PCIHOST_POSSIBLE 1364 select SSB_PCIHOST 1365 default y 1366 1367# Auto-select SSB PCICORE driver, if possible 1368config B44_PCICORE_AUTOSELECT 1369 bool 1370 depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE 1371 select SSB_DRIVER_PCICORE 1372 default y 1373 1374config B44_PCI 1375 bool 1376 depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT 1377 default y 1378 1379config FORCEDETH 1380 tristate "nForce Ethernet support" 1381 depends on NET_PCI && PCI 1382 help 1383 If you have a network (Ethernet) controller of this type, say Y and 1384 read the Ethernet-HOWTO, available from 1385 <http://www.tldp.org/docs.html#howto>. 1386 1387 To compile this driver as a module, choose M here. The module 1388 will be called forcedeth. 1389 1390config FORCEDETH_NAPI 1391 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 1392 depends on FORCEDETH && EXPERIMENTAL 1393 help 1394 NAPI is a new driver API designed to reduce CPU and interrupt load 1395 when the driver is receiving lots of packets from the card. It is 1396 still somewhat experimental and thus not yet enabled by default. 1397 1398 If your estimated Rx load is 10kpps or more, or if the card will be 1399 deployed on potentially unfriendly networks (e.g. in a firewall), 1400 then say Y here. 1401 1402 If in doubt, say N. 1403 1404config CS89x0 1405 tristate "CS89x0 support" 1406 depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X) 1407 ---help--- 1408 Support for CS89x0 chipset based Ethernet cards. If you have a 1409 network (Ethernet) card of this type, say Y and read the 1410 Ethernet-HOWTO, available from 1411 <http://www.tldp.org/docs.html#howto> as well as 1412 <file:Documentation/networking/cs89x0.txt>. 1413 1414 To compile this driver as a module, choose M here. The module 1415 will be called cs89x0. 1416 1417config TC35815 1418 tristate "TOSHIBA TC35815 Ethernet support" 1419 depends on NET_PCI && PCI && MIPS 1420 select MII 1421 1422config EEPRO100 1423 tristate "EtherExpressPro/100 support (eepro100, original Becker driver)" 1424 depends on NET_PCI && PCI 1425 select MII 1426 help 1427 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet) 1428 card, say Y and read the Ethernet-HOWTO, available from 1429 <http://www.tldp.org/docs.html#howto>. 1430 1431 To compile this driver as a module, choose M here. The module 1432 will be called eepro100. 1433 1434 1435config E100 1436 tristate "Intel(R) PRO/100+ support" 1437 depends on NET_PCI && PCI 1438 select MII 1439 ---help--- 1440 This driver supports Intel(R) PRO/100 family of adapters. 1441 To verify that your adapter is supported, find the board ID number 1442 on the adapter. Look for a label that has a barcode and a number 1443 in the format 123456-001 (six digits hyphen three digits). 1444 1445 Use the above information and the Adapter & Driver ID Guide at: 1446 1447 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 1448 1449 to identify the adapter. 1450 1451 For the latest Intel PRO/100 network driver for Linux, see: 1452 1453 <http://appsr.intel.com/scripts-df/support_intel.asp> 1454 1455 More specific information on configuring the driver is in 1456 <file:Documentation/networking/e100.txt>. 1457 1458 To compile this driver as a module, choose M here. The module 1459 will be called e100. 1460 1461config LNE390 1462 tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)" 1463 depends on NET_PCI && EISA && EXPERIMENTAL 1464 select CRC32 1465 help 1466 If you have a network (Ethernet) card of this type, say Y and read 1467 the Ethernet-HOWTO, available from 1468 <http://www.tldp.org/docs.html#howto>. 1469 1470 To compile this driver as a module, choose M here. The module 1471 will be called lne390. 1472 1473config FEALNX 1474 tristate "Myson MTD-8xx PCI Ethernet support" 1475 depends on NET_PCI && PCI 1476 select CRC32 1477 select MII 1478 help 1479 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet 1480 cards. Specifications and data at 1481 <http://www.myson.com.hk/mtd/datasheet/>. 1482 1483config NATSEMI 1484 tristate "National Semiconductor DP8381x series PCI Ethernet support" 1485 depends on NET_PCI && PCI 1486 select CRC32 1487 help 1488 This driver is for the National Semiconductor DP83810 series, 1489 which is used in cards from PureData, NetGear, Linksys 1490 and others, including the 83815 chip. 1491 More specific information and updates are available from 1492 <http://www.scyld.com/network/natsemi.html>. 1493 1494config NE2K_PCI 1495 tristate "PCI NE2000 and clones support (see help)" 1496 depends on NET_PCI && PCI 1497 select CRC32 1498 ---help--- 1499 This driver is for NE2000 compatible PCI cards. It will not work 1500 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000 1501 support" below). If you have a PCI NE2000 network (Ethernet) card, 1502 say Y and read the Ethernet-HOWTO, available from 1503 <http://www.tldp.org/docs.html#howto>. 1504 1505 This driver also works for the following NE2000 clone cards: 1506 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2 1507 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond 1508 Holtek HT80232 Holtek HT80229 1509 1510 To compile this driver as a module, choose M here. The module 1511 will be called ne2k-pci. 1512 1513config NE3210 1514 tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)" 1515 depends on NET_PCI && EISA && EXPERIMENTAL 1516 select CRC32 1517 ---help--- 1518 If you have a network (Ethernet) card of this type, say Y and read 1519 the Ethernet-HOWTO, available from 1520 <http://www.tldp.org/docs.html#howto>. Note that this driver 1521 will NOT WORK for NE3200 cards as they are completely different. 1522 1523 To compile this driver as a module, choose M here. The module 1524 will be called ne3210. 1525 1526config ES3210 1527 tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)" 1528 depends on NET_PCI && EISA && EXPERIMENTAL 1529 select CRC32 1530 help 1531 If you have a network (Ethernet) card of this type, say Y and read 1532 the Ethernet-HOWTO, available from 1533 <http://www.tldp.org/docs.html#howto>. 1534 1535 To compile this driver as a module, choose M here. The module 1536 will be called es3210. 1537 1538config 8139CP 1539 tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)" 1540 depends on NET_PCI && PCI && EXPERIMENTAL 1541 select CRC32 1542 select MII 1543 help 1544 This is a driver for the Fast Ethernet PCI network cards based on 1545 the RTL8139C+ chips. If you have one of those, say Y and read 1546 the Ethernet-HOWTO, available from 1547 <http://www.tldp.org/docs.html#howto>. 1548 1549 To compile this driver as a module, choose M here: the module 1550 will be called 8139cp. This is recommended. 1551 1552config 8139TOO 1553 tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support" 1554 depends on NET_PCI && PCI 1555 select CRC32 1556 select MII 1557 ---help--- 1558 This is a driver for the Fast Ethernet PCI network cards based on 1559 the RTL 8129/8130/8139 chips. If you have one of those, say Y and 1560 read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>. 1561 1562 To compile this driver as a module, choose M here: the module 1563 will be called 8139too. This is recommended. 1564 1565config 8139TOO_PIO 1566 bool "Use PIO instead of MMIO" 1567 default y 1568 depends on 8139TOO 1569 help 1570 This instructs the driver to use programmed I/O ports (PIO) instead 1571 of PCI shared memory (MMIO). This can possibly solve some problems 1572 in case your mainboard has memory consistency issues. If unsure, 1573 say N. 1574 1575config 8139TOO_TUNE_TWISTER 1576 bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)" 1577 depends on 8139TOO 1578 help 1579 This implements a function which might come in handy in case you 1580 are using low quality on long cabling. It is required for RealTek 1581 RTL-8139 revision K boards, and totally unused otherwise. It tries 1582 to match the transceiver to the cable characteristics. This is 1583 experimental since hardly documented by the manufacturer. 1584 If unsure, say Y. 1585 1586config 8139TOO_8129 1587 bool "Support for older RTL-8129/8130 boards" 1588 depends on 8139TOO 1589 help 1590 This enables support for the older and uncommon RTL-8129 and 1591 RTL-8130 chips, which support MII via an external transceiver, 1592 instead of an internal one. Disabling this option will save some 1593 memory by making the code size smaller. If unsure, say Y. 1594 1595config 8139_OLD_RX_RESET 1596 bool "Use older RX-reset method" 1597 depends on 8139TOO 1598 help 1599 The 8139too driver was recently updated to contain a more rapid 1600 reset sequence, in the face of severe receive errors. This "new" 1601 RX-reset method should be adequate for all boards. But if you 1602 experience problems, you can enable this option to restore the 1603 old RX-reset behavior. If unsure, say N. 1604 1605config R6040 1606 tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)" 1607 depends on NET_PCI && PCI 1608 select CRC32 1609 select MII 1610 help 1611 This is a driver for the R6040 Fast Ethernet MACs found in the 1612 the RDC R-321x System-on-chips. 1613 1614 To compile this driver as a module, choose M here: the module 1615 will be called r6040. This is recommended. 1616 1617config SIS900 1618 tristate "SiS 900/7016 PCI Fast Ethernet Adapter support" 1619 depends on NET_PCI && PCI 1620 select CRC32 1621 select MII 1622 ---help--- 1623 This is a driver for the Fast Ethernet PCI network cards based on 1624 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in 1625 SiS 630 and SiS 540 chipsets. 1626 1627 This driver also supports AMD 79C901 HomePNA so that you can use 1628 your phone line as a network cable. 1629 1630 To compile this driver as a module, choose M here: the module 1631 will be called sis900. This is recommended. 1632 1633config EPIC100 1634 tristate "SMC EtherPower II" 1635 depends on NET_PCI && PCI 1636 select CRC32 1637 select MII 1638 help 1639 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC, 1640 which is based on the SMC83c17x (EPIC/100). 1641 More specific information and updates are available from 1642 <http://www.scyld.com/network/epic100.html>. 1643 1644config SUNDANCE 1645 tristate "Sundance Alta support" 1646 depends on NET_PCI && PCI 1647 select CRC32 1648 select MII 1649 help 1650 This driver is for the Sundance "Alta" chip. 1651 More specific information and updates are available from 1652 <http://www.scyld.com/network/sundance.html>. 1653 1654config SUNDANCE_MMIO 1655 bool "Use MMIO instead of PIO" 1656 depends on SUNDANCE 1657 help 1658 Enable memory-mapped I/O for interaction with Sundance NIC registers. 1659 Do NOT enable this by default, PIO (enabled when MMIO is disabled) 1660 is known to solve bugs on certain chips. 1661 1662 If unsure, say N. 1663 1664config TLAN 1665 tristate "TI ThunderLAN support" 1666 depends on NET_PCI && (PCI || EISA) && !64BIT 1667 ---help--- 1668 If you have a PCI Ethernet network card based on the ThunderLAN chip 1669 which is supported by this driver, say Y and read the 1670 Ethernet-HOWTO, available from 1671 <http://www.tldp.org/docs.html#howto>. 1672 1673 Devices currently supported by this driver are Compaq Netelligent, 1674 Compaq NetFlex and Olicom cards. Please read the file 1675 <file:Documentation/networking/tlan.txt> for more details. 1676 1677 To compile this driver as a module, choose M here. The module 1678 will be called tlan. 1679 1680 Please email feedback to <torben.mathiasen@compaq.com>. 1681 1682config VIA_RHINE 1683 tristate "VIA Rhine support" 1684 depends on NET_PCI && PCI 1685 select CRC32 1686 select MII 1687 help 1688 If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A), 1689 Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type 1690 Ethernet functions can also be found integrated on South Bridges 1691 (e.g. VT8235). 1692 1693 To compile this driver as a module, choose M here. The module 1694 will be called via-rhine. 1695 1696config VIA_RHINE_MMIO 1697 bool "Use MMIO instead of PIO" 1698 depends on VIA_RHINE 1699 help 1700 This instructs the driver to use PCI shared memory (MMIO) instead of 1701 programmed I/O ports (PIO). Enabling this gives an improvement in 1702 processing time in parts of the driver. 1703 1704 If unsure, say Y. 1705 1706config VIA_RHINE_NAPI 1707 bool "Use Rx Polling (NAPI)" 1708 depends on VIA_RHINE 1709 help 1710 NAPI is a new driver API designed to reduce CPU and interrupt load 1711 when the driver is receiving lots of packets from the card. 1712 1713 If your estimated Rx load is 10kpps or more, or if the card will be 1714 deployed on potentially unfriendly networks (e.g. in a firewall), 1715 then say Y here. 1716 1717config LAN_SAA9730 1718 bool "Philips SAA9730 Ethernet support" 1719 depends on NET_PCI && PCI && MIPS_ATLAS 1720 help 1721 The SAA9730 is a combined multimedia and peripheral controller used 1722 in thin clients, Internet access terminals, and diskless 1723 workstations. 1724 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>. 1725 1726config SC92031 1727 tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)" 1728 depends on NET_PCI && PCI && EXPERIMENTAL 1729 select CRC32 1730 ---help--- 1731 This is a driver for the Fast Ethernet PCI network cards based on 1732 the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you 1733 have one of these, say Y here. 1734 1735 To compile this driver as a module, choose M here: the module 1736 will be called sc92031. This is recommended. 1737 1738config CPMAC 1739 tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)" 1740 depends on NET_ETHERNET && EXPERIMENTAL && AR7 1741 select PHYLIB 1742 select FIXED_PHY 1743 select FIXED_MII_100_FDX 1744 help 1745 TI AR7 CPMAC Ethernet support 1746 1747config NET_POCKET 1748 bool "Pocket and portable adapters" 1749 depends on PARPORT 1750 ---help--- 1751 Cute little network (Ethernet) devices which attach to the parallel 1752 port ("pocket adapters"), commonly used with laptops. If you have 1753 one of those, say Y and read the Ethernet-HOWTO, available from 1754 <http://www.tldp.org/docs.html#howto>. 1755 1756 If you want to plug a network (or some other) card into the PCMCIA 1757 (or PC-card) slot of your laptop instead (PCMCIA is the standard for 1758 credit card size extension cards used by all modern laptops), you 1759 need the pcmcia-cs package (location contained in the file 1760 <file:Documentation/Changes>) and you can say N here. 1761 1762 Laptop users should read the Linux Laptop home page at 1763 <http://www.linux-on-laptops.com/> or 1764 Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>. 1765 1766 Note that the answer to this question doesn't directly affect the 1767 kernel: saying N will just cause the configurator to skip all 1768 the questions about this class of network devices. If you say Y, you 1769 will be asked for your specific device in the following questions. 1770 1771config ATP 1772 tristate "AT-LAN-TEC/RealTek pocket adapter support" 1773 depends on NET_POCKET && PARPORT && X86 1774 select CRC32 1775 ---help--- 1776 This is a network (Ethernet) device which attaches to your parallel 1777 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO, 1778 available from <http://www.tldp.org/docs.html#howto>, if you 1779 want to use this. If you intend to use this driver, you should have 1780 said N to the "Parallel printer support", because the two drivers 1781 don't like each other. 1782 1783 To compile this driver as a module, choose M here: the module 1784 will be called atp. 1785 1786config DE600 1787 tristate "D-Link DE600 pocket adapter support" 1788 depends on NET_POCKET && PARPORT 1789 ---help--- 1790 This is a network (Ethernet) device which attaches to your parallel 1791 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1792 Ethernet-HOWTO, available from 1793 <http://www.tldp.org/docs.html#howto>, if you want to use 1794 this. It is possible to have several devices share a single parallel 1795 port and it is safe to compile the corresponding drivers into the 1796 kernel. 1797 1798 To compile this driver as a module, choose M here: the module 1799 will be called de600. 1800 1801config DE620 1802 tristate "D-Link DE620 pocket adapter support" 1803 depends on NET_POCKET && PARPORT 1804 ---help--- 1805 This is a network (Ethernet) device which attaches to your parallel 1806 port. Read <file:Documentation/networking/DLINK.txt> as well as the 1807 Ethernet-HOWTO, available from 1808 <http://www.tldp.org/docs.html#howto>, if you want to use 1809 this. It is possible to have several devices share a single parallel 1810 port and it is safe to compile the corresponding drivers into the 1811 kernel. 1812 1813 To compile this driver as a module, choose M here: the module 1814 will be called de620. 1815 1816config SGISEEQ 1817 tristate "SGI Seeq ethernet controller support" 1818 depends on SGI_HAS_SEEQ 1819 help 1820 Say Y here if you have an Seeq based Ethernet network card. This is 1821 used in many Silicon Graphics machines. 1822 1823config DECLANCE 1824 tristate "DEC LANCE ethernet controller support" 1825 depends on MACH_DECSTATION 1826 select CRC32 1827 help 1828 This driver is for the series of Ethernet controllers produced by 1829 DEC (now Compaq) based on the AMD Lance chipset, including the 1830 DEPCA series. (This chipset is better known via the NE2100 cards.) 1831 1832config 68360_ENET 1833 bool "Motorola 68360 ethernet controller" 1834 depends on M68360 1835 help 1836 Say Y here if you want to use the built-in ethernet controller of 1837 the Motorola 68360 processor. 1838 1839config FEC 1840 bool "FEC ethernet controller (of ColdFire CPUs)" 1841 depends on M523x || M527x || M5272 || M528x || M520x 1842 help 1843 Say Y here if you want to use the built-in 10/100 Fast ethernet 1844 controller on some Motorola ColdFire processors. 1845 1846config FEC2 1847 bool "Second FEC ethernet controller (on some ColdFire CPUs)" 1848 depends on FEC 1849 help 1850 Say Y here if you want to use the second built-in 10/100 Fast 1851 ethernet controller on some Motorola ColdFire processors. 1852 1853config FEC_MPC52xx 1854 tristate "MPC52xx FEC driver" 1855 depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC 1856 select CRC32 1857 select PHYLIB 1858 ---help--- 1859 This option enables support for the MPC5200's on-chip 1860 Fast Ethernet Controller 1861 If compiled as module, it will be called 'fec_mpc52xx.ko'. 1862 1863config FEC_MPC52xx_MDIO 1864 bool "MPC52xx FEC MDIO bus driver" 1865 depends on FEC_MPC52xx 1866 default y 1867 ---help--- 1868 The MPC5200's FEC can connect to the Ethernet either with 1869 an external MII PHY chip or 10 Mbps 7-wire interface 1870 (Motorola? industry standard). 1871 If your board uses an external PHY connected to FEC, enable this. 1872 If not sure, enable. 1873 If compiled as module, it will be called 'fec_mpc52xx_phy.ko'. 1874 1875config NE_H8300 1876 tristate "NE2000 compatible support for H8/300" 1877 depends on H8300 1878 help 1879 Say Y here if you want to use the NE2000 compatible 1880 controller on the Renesas H8/300 processor. 1881 1882source "drivers/net/fec_8xx/Kconfig" 1883source "drivers/net/fs_enet/Kconfig" 1884 1885endif # NET_ETHERNET 1886 1887# 1888# Gigabit Ethernet 1889# 1890 1891menuconfig NETDEV_1000 1892 bool "Ethernet (1000 Mbit)" 1893 depends on !UML 1894 default y 1895 ---help--- 1896 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common 1897 type of Local Area Network (LAN) in universities and companies. 1898 1899 Say Y here to get to see options for Gigabit Ethernet drivers. 1900 This option alone does not add any kernel code. 1901 Note that drivers supporting both 100 and 1000 MBit may be listed 1902 under "Ethernet (10 or 100MBit)" instead. 1903 1904 If you say N, all options in this submenu will be skipped and disabled. 1905 1906if NETDEV_1000 1907 1908config ACENIC 1909 tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support" 1910 depends on PCI 1911 ---help--- 1912 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear 1913 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet 1914 adapter. The driver allows for using the Jumbo Frame option (9000 1915 bytes/frame) however it requires that your switches can handle this 1916 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig 1917 line. 1918 1919 To compile this driver as a module, choose M here: the 1920 module will be called acenic. 1921 1922config ACENIC_OMIT_TIGON_I 1923 bool "Omit support for old Tigon I based AceNICs" 1924 depends on ACENIC 1925 help 1926 Say Y here if you only have Tigon II based AceNICs and want to leave 1927 out support for the older Tigon I based cards which are no longer 1928 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B 1929 version)). This will reduce the size of the driver object by 1930 app. 100KB. If you are not sure whether your card is a Tigon I or a 1931 Tigon II, say N here. 1932 1933 The safe and default value for this is N. 1934 1935config DL2K 1936 tristate "DL2000/TC902x-based Gigabit Ethernet support" 1937 depends on PCI 1938 select CRC32 1939 help 1940 This driver supports DL2000/TC902x-based Gigabit ethernet cards, 1941 which includes 1942 D-Link DGE-550T Gigabit Ethernet Adapter. 1943 D-Link DL2000-based Gigabit Ethernet Adapter. 1944 Sundance/Tamarack TC902x Gigabit Ethernet Adapter. 1945 1946 To compile this driver as a module, choose M here: the 1947 module will be called dl2k. 1948 1949config E1000 1950 tristate "Intel(R) PRO/1000 Gigabit Ethernet support" 1951 depends on PCI 1952 ---help--- 1953 This driver supports Intel(R) PRO/1000 gigabit ethernet family of 1954 adapters. For more information on how to identify your adapter, go 1955 to the Adapter & Driver ID Guide at: 1956 1957 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 1958 1959 For general information and support, go to the Intel support 1960 website at: 1961 1962 <http://support.intel.com> 1963 1964 More specific information on configuring the driver is in 1965 <file:Documentation/networking/e1000.txt>. 1966 1967 To compile this driver as a module, choose M here. The module 1968 will be called e1000. 1969 1970config E1000_NAPI 1971 bool "Use Rx Polling (NAPI)" 1972 depends on E1000 1973 help 1974 NAPI is a new driver API designed to reduce CPU and interrupt load 1975 when the driver is receiving lots of packets from the card. It is 1976 still somewhat experimental and thus not yet enabled by default. 1977 1978 If your estimated Rx load is 10kpps or more, or if the card will be 1979 deployed on potentially unfriendly networks (e.g. in a firewall), 1980 then say Y here. 1981 1982 If in doubt, say N. 1983 1984config E1000_DISABLE_PACKET_SPLIT 1985 bool "Disable Packet Split for PCI express adapters" 1986 depends on E1000 1987 help 1988 Say Y here if you want to use the legacy receive path for PCI express 1989 hardware. 1990 1991 If in doubt, say N. 1992 1993config E1000E 1994 tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support" 1995 depends on PCI && EXPERIMENTAL 1996 ---help--- 1997 This driver supports the PCI-Express Intel(R) PRO/1000 gigabit 1998 ethernet family of adapters. For PCI or PCI-X e1000 adapters, 1999 use the regular e1000 driver For more information on how to 2000 identify your adapter, go to the Adapter & Driver ID Guide at: 2001 2002 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2003 2004 For general information and support, go to the Intel support 2005 website at: 2006 2007 <http://support.intel.com> 2008 2009 To compile this driver as a module, choose M here. The module 2010 will be called e1000e. 2011 2012config IP1000 2013 tristate "IP1000 Gigabit Ethernet support" 2014 depends on PCI && EXPERIMENTAL 2015 select MII 2016 ---help--- 2017 This driver supports IP1000 gigabit Ethernet cards. 2018 2019 To compile this driver as a module, choose M here: the module 2020 will be called ipg. This is recommended. 2021 2022config IGB 2023 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support" 2024 depends on PCI 2025 ---help--- 2026 This driver supports Intel(R) 82575 gigabit ethernet family of 2027 adapters. For more information on how to identify your adapter, go 2028 to the Adapter & Driver ID Guide at: 2029 2030 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2031 2032 For general information and support, go to the Intel support 2033 website at: 2034 2035 <http://support.intel.com> 2036 2037 More specific information on configuring the driver is in 2038 <file:Documentation/networking/e1000.txt>. 2039 2040 To compile this driver as a module, choose M here and read 2041 <file:Documentation/networking/net-modules.txt>. The module 2042 will be called igb. 2043 2044source "drivers/net/ixp2000/Kconfig" 2045 2046config MYRI_SBUS 2047 tristate "MyriCOM Gigabit Ethernet support" 2048 depends on SBUS 2049 help 2050 This driver supports MyriCOM Sbus gigabit Ethernet cards. 2051 2052 To compile this driver as a module, choose M here: the module 2053 will be called myri_sbus. This is recommended. 2054 2055config NS83820 2056 tristate "National Semiconductor DP83820 support" 2057 depends on PCI 2058 help 2059 This is a driver for the National Semiconductor DP83820 series 2060 of gigabit ethernet MACs. Cards using this chipset include 2061 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, 2062 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of 2063 zero copy. 2064 2065config HAMACHI 2066 tristate "Packet Engines Hamachi GNIC-II support" 2067 depends on PCI 2068 select MII 2069 help 2070 If you have a Gigabit Ethernet card of this type, say Y and read 2071 the Ethernet-HOWTO, available from 2072 <http://www.tldp.org/docs.html#howto>. 2073 2074 To compile this driver as a module, choose M here. The module will be 2075 called hamachi. 2076 2077config YELLOWFIN 2078 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 2079 depends on PCI && EXPERIMENTAL 2080 select CRC32 2081 ---help--- 2082 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 2083 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 2084 used by the Beowulf Linux cluster project. See 2085 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 2086 information about this driver in particular and Beowulf in general. 2087 2088 To compile this driver as a module, choose M here: the module 2089 will be called yellowfin. This is recommended. 2090 2091config R8169 2092 tristate "Realtek 8169 gigabit ethernet support" 2093 depends on PCI 2094 select CRC32 2095 ---help--- 2096 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. 2097 2098 To compile this driver as a module, choose M here: the module 2099 will be called r8169. This is recommended. 2100 2101config R8169_NAPI 2102 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 2103 depends on R8169 && EXPERIMENTAL 2104 help 2105 NAPI is a new driver API designed to reduce CPU and interrupt load 2106 when the driver is receiving lots of packets from the card. It is 2107 still somewhat experimental and thus not yet enabled by default. 2108 2109 If your estimated Rx load is 10kpps or more, or if the card will be 2110 deployed on potentially unfriendly networks (e.g. in a firewall), 2111 then say Y here. 2112 2113 If in doubt, say N. 2114 2115config R8169_VLAN 2116 bool "VLAN support" 2117 depends on R8169 && VLAN_8021Q 2118 ---help--- 2119 Say Y here for the r8169 driver to support the functions required 2120 by the kernel 802.1Q code. 2121 2122 If in doubt, say Y. 2123 2124config SB1250_MAC 2125 tristate "SB1250 Gigabit Ethernet support" 2126 depends on SIBYTE_SB1xxx_SOC 2127 select PHYLIB 2128 ---help--- 2129 This driver supports Gigabit Ethernet interfaces based on the 2130 Broadcom SiByte family of System-On-a-Chip parts. They include 2131 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 2132 and BCM1480 chips. 2133 2134 To compile this driver as a module, choose M here: the module 2135 will be called sb1250-mac. 2136 2137config SIS190 2138 tristate "SiS190/SiS191 gigabit ethernet support" 2139 depends on PCI 2140 select CRC32 2141 select MII 2142 ---help--- 2143 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or 2144 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to 2145 appear in lan on motherboard designs which are based on SiS 965 2146 and SiS 966 south bridge. 2147 2148 To compile this driver as a module, choose M here: the module 2149 will be called sis190. This is recommended. 2150 2151config SKGE 2152 tristate "New SysKonnect GigaEthernet support" 2153 depends on PCI 2154 select CRC32 2155 ---help--- 2156 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2157 and related Gigabit Ethernet adapters. It is a new smaller driver 2158 with better performance and more complete ethtool support. 2159 2160 It does not support the link failover and network management 2161 features that "portable" vendor supplied sk98lin driver does. 2162 2163 This driver supports adapters based on the original Yukon chipset: 2164 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, 2165 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. 2166 2167 It does not support the newer Yukon2 chipset: a separate driver, 2168 sky2, is provided for Yukon2-based adapters. 2169 2170 To compile this driver as a module, choose M here: the module 2171 will be called skge. This is recommended. 2172 2173config SKGE_DEBUG 2174 bool "Debugging interface" 2175 depends on SKGE && DEBUG_FS 2176 help 2177 This option adds the ability to dump driver state for debugging. 2178 The file debugfs/skge/ethX displays the state of the internal 2179 transmit and receive rings. 2180 2181 If unsure, say N. 2182 2183config SKY2 2184 tristate "SysKonnect Yukon2 support" 2185 depends on PCI 2186 select CRC32 2187 ---help--- 2188 This driver supports Gigabit Ethernet adapters based on the 2189 Marvell Yukon 2 chipset: 2190 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 2191 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 2192 2193 There is companion driver for the older Marvell Yukon and 2194 Genesis based adapters: skge. 2195 2196 To compile this driver as a module, choose M here: the module 2197 will be called sky2. This is recommended. 2198 2199config SKY2_DEBUG 2200 bool "Debugging interface" 2201 depends on SKY2 && DEBUG_FS 2202 help 2203 This option adds the ability to dump driver state for debugging. 2204 The file debugfs/sky2/ethX displays the state of the internal 2205 transmit and receive rings. 2206 2207 If unsure, say N. 2208 2209config SK98LIN 2210 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)" 2211 depends on PCI 2212 ---help--- 2213 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2214 compliant Gigabit Ethernet Adapter. 2215 2216 This driver supports the original Yukon chipset. This driver is 2217 deprecated and will be removed from the kernel in the near future, 2218 it has been replaced by the skge driver. skge is cleaner and 2219 seems to work better. 2220 2221 This driver does not support the newer Yukon2 chipset. A separate 2222 driver, sky2, is provided to support Yukon2-based adapters. 2223 2224 The following adapters are supported by this driver: 2225 - 3Com 3C940 Gigabit LOM Ethernet Adapter 2226 - 3Com 3C941 Gigabit LOM Ethernet Adapter 2227 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter 2228 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter 2229 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter 2230 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter 2231 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter 2232 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter 2233 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter 2234 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter 2235 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45 2236 - EG1032 v2 Instant Gigabit Network Adapter 2237 - EG1064 v2 Instant Gigabit Network Adapter 2238 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit) 2239 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron) 2240 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus) 2241 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS) 2242 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox) 2243 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn) 2244 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte) 2245 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill) 2246 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel) 2247 - Marvell RDK-8001 Adapter 2248 - Marvell RDK-8002 Adapter 2249 - Marvell RDK-8003 Adapter 2250 - Marvell RDK-8004 Adapter 2251 - Marvell RDK-8006 Adapter 2252 - Marvell RDK-8007 Adapter 2253 - Marvell RDK-8008 Adapter 2254 - Marvell RDK-8009 Adapter 2255 - Marvell RDK-8010 Adapter 2256 - Marvell RDK-8011 Adapter 2257 - Marvell RDK-8012 Adapter 2258 - Marvell RDK-8052 Adapter 2259 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit) 2260 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit) 2261 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L) 2262 - SK-9521 10/100/1000Base-T Adapter 2263 - SK-9521 V2.0 10/100/1000Base-T Adapter 2264 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T) 2265 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter 2266 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link) 2267 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX) 2268 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter 2269 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link) 2270 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX) 2271 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter 2272 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link) 2273 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter 2274 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition) 2275 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter 2276 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link) 2277 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX) 2278 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter 2279 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link) 2280 - SMC EZ Card 1000 (SMC9452TXV.2) 2281 2282 The adapters support Jumbo Frames. 2283 The dual link adapters support link-failover and dual port features. 2284 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support 2285 the scatter-gather functionality with sendfile(). Please refer to 2286 <file:Documentation/networking/sk98lin.txt> for more information about 2287 optional driver parameters. 2288 Questions concerning this driver may be addressed to: 2289 <linux@syskonnect.de> 2290 2291 If you want to compile this driver as a module ( = code which can be 2292 inserted in and removed from the running kernel whenever you want), 2293 say M here and read <file:Documentation/kbuild/modules.txt>. The module will 2294 be called sk98lin. This is recommended. 2295 2296config VIA_VELOCITY 2297 tristate "VIA Velocity support" 2298 depends on PCI 2299 select CRC32 2300 select CRC_CCITT 2301 select MII 2302 help 2303 If you have a VIA "Velocity" based network card say Y here. 2304 2305 To compile this driver as a module, choose M here. The module 2306 will be called via-velocity. 2307 2308config TIGON3 2309 tristate "Broadcom Tigon3 support" 2310 depends on PCI 2311 help 2312 This driver supports Broadcom Tigon3 based gigabit Ethernet cards. 2313 2314 To compile this driver as a module, choose M here: the module 2315 will be called tg3. This is recommended. 2316 2317config BNX2 2318 tristate "Broadcom NetXtremeII support" 2319 depends on PCI 2320 select CRC32 2321 select ZLIB_INFLATE 2322 help 2323 This driver supports Broadcom NetXtremeII gigabit Ethernet cards. 2324 2325 To compile this driver as a module, choose M here: the module 2326 will be called bnx2. This is recommended. 2327 2328config SPIDER_NET 2329 tristate "Spider Gigabit Ethernet driver" 2330 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 2331 select FW_LOADER 2332 help 2333 This driver supports the Gigabit Ethernet chips present on the 2334 Cell Processor-Based Blades from IBM. 2335 2336config TSI108_ETH 2337 tristate "Tundra TSI108 gigabit Ethernet support" 2338 depends on TSI108_BRIDGE 2339 help 2340 This driver supports Tundra TSI108 gigabit Ethernet ports. 2341 To compile this driver as a module, choose M here: the module 2342 will be called tsi108_eth. 2343 2344config GELIC_NET 2345 tristate "PS3 Gigabit Ethernet driver" 2346 depends on PPC_PS3 2347 help 2348 This driver supports the network device on the PS3 game 2349 console. This driver has built-in support for Ethernet. 2350 2351 To compile this driver as a module, choose M here: the 2352 module will be called ps3_gelic. 2353 2354config GIANFAR 2355 tristate "Gianfar Ethernet" 2356 depends on 85xx || 83xx || PPC_86xx 2357 select PHYLIB 2358 select CRC32 2359 help 2360 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, 2361 and MPC86xx family of chips, and the FEC on the 8540. 2362 2363config GFAR_NAPI 2364 bool "Use Rx Polling (NAPI)" 2365 depends on GIANFAR 2366 2367config UCC_GETH 2368 tristate "Freescale QE Gigabit Ethernet" 2369 depends on QUICC_ENGINE 2370 select PHYLIB 2371 help 2372 This driver supports the Gigabit Ethernet mode of the QUICC Engine, 2373 which is available on some Freescale SOCs. 2374 2375config UGETH_NAPI 2376 bool "Use Rx Polling (NAPI)" 2377 depends on UCC_GETH 2378 2379config UGETH_MAGIC_PACKET 2380 bool "Magic Packet detection support" 2381 depends on UCC_GETH 2382 2383config UGETH_FILTERING 2384 bool "Mac address filtering support" 2385 depends on UCC_GETH 2386 2387config UGETH_TX_ON_DEMAND 2388 bool "Transmit on Demand support" 2389 depends on UCC_GETH 2390 2391config MV643XX_ETH 2392 tristate "Marvell Discovery (643XX) and Orion ethernet support" 2393 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || ARCH_ORION 2394 select MII 2395 help 2396 This driver supports the gigabit ethernet MACs in the 2397 Marvell Discovery PPC/MIPS chipset family (MV643XX) and 2398 in the Marvell Orion ARM SoC family. 2399 2400 Some boards that use the Discovery chipset are the Momenco 2401 Ocelot C and Jaguar ATX and Pegasos II. 2402 2403config QLA3XXX 2404 tristate "QLogic QLA3XXX Network Driver Support" 2405 depends on PCI 2406 help 2407 This driver supports QLogic ISP3XXX gigabit Ethernet cards. 2408 2409 To compile this driver as a module, choose M here: the module 2410 will be called qla3xxx. 2411 2412config ATL1 2413 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)" 2414 depends on PCI && EXPERIMENTAL 2415 select CRC32 2416 select MII 2417 help 2418 This driver supports the Attansic L1 gigabit ethernet adapter. 2419 2420 To compile this driver as a module, choose M here. The module 2421 will be called atl1. 2422 2423endif # NETDEV_1000 2424 2425# 2426# 10 Gigabit Ethernet 2427# 2428 2429menuconfig NETDEV_10000 2430 bool "Ethernet (10000 Mbit)" 2431 depends on !UML 2432 default y 2433 ---help--- 2434 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 2435 This option alone does not add any kernel code. 2436 2437 If you say N, all options in this submenu will be skipped and disabled. 2438 2439if NETDEV_10000 2440 2441config CHELSIO_T1 2442 tristate "Chelsio 10Gb Ethernet support" 2443 depends on PCI 2444 select CRC32 2445 help 2446 This driver supports Chelsio gigabit and 10-gigabit 2447 Ethernet cards. More information about adapter features and 2448 performance tuning is in <file:Documentation/networking/cxgb.txt>. 2449 2450 For general information about Chelsio and our products, visit 2451 our website at <http://www.chelsio.com>. 2452 2453 For customer support, please visit our customer support page at 2454 <http://www.chelsio.com/support.htm>. 2455 2456 Please send feedback to <linux-bugs@chelsio.com>. 2457 2458 To compile this driver as a module, choose M here: the module 2459 will be called cxgb. 2460 2461config CHELSIO_T1_1G 2462 bool "Chelsio gigabit Ethernet support" 2463 depends on CHELSIO_T1 2464 help 2465 Enables support for Chelsio's gigabit Ethernet PCI cards. If you 2466 are using only 10G cards say 'N' here. 2467 2468config CHELSIO_T1_NAPI 2469 bool "Use Rx Polling (NAPI)" 2470 depends on CHELSIO_T1 2471 default y 2472 help 2473 NAPI is a driver API designed to reduce CPU and interrupt load 2474 when the driver is receiving lots of packets from the card. 2475 2476config CHELSIO_T3 2477 tristate "Chelsio Communications T3 10Gb Ethernet support" 2478 depends on PCI 2479 select FW_LOADER 2480 help 2481 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet 2482 adapters. 2483 2484 For general information about Chelsio and our products, visit 2485 our website at <http://www.chelsio.com>. 2486 2487 For customer support, please visit our customer support page at 2488 <http://www.chelsio.com/support.htm>. 2489 2490 Please send feedback to <linux-bugs@chelsio.com>. 2491 2492 To compile this driver as a module, choose M here: the module 2493 will be called cxgb3. 2494 2495config EHEA 2496 tristate "eHEA Ethernet support" 2497 depends on IBMEBUS && INET 2498 select INET_LRO 2499 ---help--- 2500 This driver supports the IBM pSeries eHEA ethernet adapter. 2501 2502 To compile the driver as a module, choose M here. The module 2503 will be called ehea. 2504 2505config IXGBE 2506 tristate "Intel(R) 10GbE PCI Express adapters support" 2507 depends on PCI 2508 ---help--- 2509 This driver supports Intel(R) 10GbE PCI Express family of 2510 adapters. For more information on how to identify your adapter, go 2511 to the Adapter & Driver ID Guide at: 2512 2513 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2514 2515 For general information and support, go to the Intel support 2516 website at: 2517 2518 <http://support.intel.com> 2519 2520 To compile this driver as a module, choose M here. The module 2521 will be called ixgbe. 2522 2523config IXGB 2524 tristate "Intel(R) PRO/10GbE support" 2525 depends on PCI 2526 ---help--- 2527 This driver supports Intel(R) PRO/10GbE family of adapters for 2528 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 2529 instead. For more information on how to identify your adapter, go 2530 to the Adapter & Driver ID Guide at: 2531 2532 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2533 2534 For general information and support, go to the Intel support 2535 website at: 2536 2537 <http://support.intel.com> 2538 2539 More specific information on configuring the driver is in 2540 <file:Documentation/networking/ixgb.txt>. 2541 2542 To compile this driver as a module, choose M here. The module 2543 will be called ixgb. 2544 2545config IXGB_NAPI 2546 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 2547 depends on IXGB && EXPERIMENTAL 2548 help 2549 NAPI is a new driver API designed to reduce CPU and interrupt load 2550 when the driver is receiving lots of packets from the card. It is 2551 still somewhat experimental and thus not yet enabled by default. 2552 2553 If your estimated Rx load is 10kpps or more, or if the card will be 2554 deployed on potentially unfriendly networks (e.g. in a firewall), 2555 then say Y here. 2556 2557 If in doubt, say N. 2558 2559config S2IO 2560 tristate "S2IO 10Gbe XFrame NIC" 2561 depends on PCI 2562 ---help--- 2563 This driver supports the 10Gbe XFrame NIC of S2IO. 2564 More specific information on configuring the driver is in 2565 <file:Documentation/networking/s2io.txt>. 2566 2567config S2IO_NAPI 2568 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 2569 depends on S2IO && EXPERIMENTAL 2570 help 2571 NAPI is a new driver API designed to reduce CPU and interrupt load 2572 when the driver is receiving lots of packets from the card. It is 2573 still somewhat experimental and thus not yet enabled by default. 2574 2575 If your estimated Rx load is 10kpps or more, or if the card will be 2576 deployed on potentially unfriendly networks (e.g. in a firewall), 2577 then say Y here. 2578 2579 If in doubt, say N. 2580 2581config MYRI10GE 2582 tristate "Myricom Myri-10G Ethernet support" 2583 depends on PCI && INET 2584 select FW_LOADER 2585 select CRC32 2586 select INET_LRO 2587 ---help--- 2588 This driver supports Myricom Myri-10G Dual Protocol interface in 2589 Ethernet mode. If the eeprom on your board is not recent enough, 2590 you will need a newer firmware image. 2591 You may get this image or more information, at: 2592 2593 <http://www.myri.com/scs/download-Myri10GE.html> 2594 2595 To compile this driver as a module, choose M here. The module 2596 will be called myri10ge. 2597 2598config NETXEN_NIC 2599 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" 2600 depends on PCI 2601 help 2602 This enables the support for NetXen's Gigabit Ethernet card. 2603 2604config NIU 2605 tristate "Sun Neptune 10Gbit Ethernet support" 2606 depends on PCI 2607 help 2608 This enables support for cards based upon Sun's 2609 Neptune chipset. 2610 2611config PASEMI_MAC 2612 tristate "PA Semi 1/10Gbit MAC" 2613 depends on PPC64 && PCI 2614 select PHYLIB 2615 select INET_LRO 2616 help 2617 This driver supports the on-chip 1/10Gbit Ethernet controller on 2618 PA Semi's PWRficient line of chips. 2619 2620config MLX4_CORE 2621 tristate 2622 depends on PCI 2623 default n 2624 2625config MLX4_DEBUG 2626 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED) 2627 depends on MLX4_CORE 2628 default y 2629 ---help--- 2630 This option causes debugging code to be compiled into the 2631 mlx4_core driver. The output can be turned on via the 2632 debug_level module parameter (which can also be set after 2633 the driver is loaded through sysfs). 2634 2635config TEHUTI 2636 tristate "Tehuti Networks 10G Ethernet" 2637 depends on PCI 2638 help 2639 Tehuti Networks 10G Ethernet NIC 2640 2641config BNX2X 2642 tristate "Broadcom NetXtremeII 10Gb support" 2643 depends on PCI 2644 select ZLIB_INFLATE 2645 help 2646 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. 2647 To compile this driver as a module, choose M here: the module 2648 will be called bnx2x. This is recommended. 2649 2650 2651endif # NETDEV_10000 2652 2653source "drivers/net/tokenring/Kconfig" 2654 2655source "drivers/net/wireless/Kconfig" 2656 2657source "drivers/net/usb/Kconfig" 2658 2659source "drivers/net/pcmcia/Kconfig" 2660 2661source "drivers/net/wan/Kconfig" 2662 2663source "drivers/atm/Kconfig" 2664 2665source "drivers/s390/net/Kconfig" 2666 2667config XEN_NETDEV_FRONTEND 2668 tristate "Xen network device frontend driver" 2669 depends on XEN 2670 default y 2671 help 2672 The network device frontend driver allows the kernel to 2673 access network devices exported exported by a virtual 2674 machine containing a physical network device driver. The 2675 frontend driver is intended for unprivileged guest domains; 2676 if you are compiling a kernel for a Xen guest, you almost 2677 certainly want to enable this. 2678 2679config ISERIES_VETH 2680 tristate "iSeries Virtual Ethernet driver support" 2681 depends on PPC_ISERIES 2682 2683config RIONET 2684 tristate "RapidIO Ethernet over messaging driver support" 2685 depends on RAPIDIO 2686 2687config RIONET_TX_SIZE 2688 int "Number of outbound queue entries" 2689 depends on RIONET 2690 default "128" 2691 2692config RIONET_RX_SIZE 2693 int "Number of inbound queue entries" 2694 depends on RIONET 2695 default "128" 2696 2697config FDDI 2698 bool "FDDI driver support" 2699 depends on (PCI || EISA || TC) 2700 help 2701 Fiber Distributed Data Interface is a high speed local area network 2702 design; essentially a replacement for high speed Ethernet. FDDI can 2703 run over copper or fiber. If you are connected to such a network and 2704 want a driver for the FDDI card in your computer, say Y here (and 2705 then also Y to the driver for your FDDI card, below). Most people 2706 will say N. 2707 2708config DEFXX 2709 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 2710 depends on FDDI && (PCI || EISA || TC) 2711 ---help--- 2712 This is support for the DIGITAL series of TURBOchannel (DEFTA), 2713 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 2714 to a local FDDI network. 2715 2716 To compile this driver as a module, choose M here: the module 2717 will be called defxx. If unsure, say N. 2718 2719config DEFXX_MMIO 2720 bool 2721 prompt "Use MMIO instead of PIO" if PCI || EISA 2722 depends on DEFXX 2723 default n if PCI || EISA 2724 default y 2725 ---help--- 2726 This instructs the driver to use EISA or PCI memory-mapped I/O 2727 (MMIO) as appropriate instead of programmed I/O ports (PIO). 2728 Enabling this gives an improvement in processing time in parts 2729 of the driver, but it may cause problems with EISA (DEFEA) 2730 adapters. TURBOchannel does not have the concept of I/O ports, 2731 so MMIO is always used for these (DEFTA) adapters. 2732 2733 If unsure, say N. 2734 2735config SKFP 2736 tristate "SysKonnect FDDI PCI support" 2737 depends on FDDI && PCI 2738 select BITREVERSE 2739 ---help--- 2740 Say Y here if you have a SysKonnect FDDI PCI adapter. 2741 The following adapters are supported by this driver: 2742 - SK-5521 (SK-NET FDDI-UP) 2743 - SK-5522 (SK-NET FDDI-UP DAS) 2744 - SK-5541 (SK-NET FDDI-FP) 2745 - SK-5543 (SK-NET FDDI-LP) 2746 - SK-5544 (SK-NET FDDI-LP DAS) 2747 - SK-5821 (SK-NET FDDI-UP64) 2748 - SK-5822 (SK-NET FDDI-UP64 DAS) 2749 - SK-5841 (SK-NET FDDI-FP64) 2750 - SK-5843 (SK-NET FDDI-LP64) 2751 - SK-5844 (SK-NET FDDI-LP64 DAS) 2752 - Netelligent 100 FDDI DAS Fibre SC 2753 - Netelligent 100 FDDI SAS Fibre SC 2754 - Netelligent 100 FDDI DAS UTP 2755 - Netelligent 100 FDDI SAS UTP 2756 - Netelligent 100 FDDI SAS Fibre MIC 2757 2758 Read <file:Documentation/networking/skfp.txt> for information about 2759 the driver. 2760 2761 Questions concerning this driver can be addressed to: 2762 <linux@syskonnect.de> 2763 2764 To compile this driver as a module, choose M here: the module 2765 will be called skfp. This is recommended. 2766 2767config HIPPI 2768 bool "HIPPI driver support (EXPERIMENTAL)" 2769 depends on EXPERIMENTAL && INET && PCI 2770 help 2771 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 2772 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 2773 can run over copper (25m) or fiber (300m on multi-mode or 10km on 2774 single-mode). HIPPI networks are commonly used for clusters and to 2775 connect to super computers. If you are connected to a HIPPI network 2776 and have a HIPPI network card in your computer that you want to use 2777 under Linux, say Y here (you must also remember to enable the driver 2778 for your HIPPI card below). Most people will say N here. 2779 2780config ROADRUNNER 2781 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 2782 depends on HIPPI && PCI 2783 help 2784 Say Y here if this is your PCI HIPPI network card. 2785 2786 To compile this driver as a module, choose M here: the module 2787 will be called rrunner. If unsure, say N. 2788 2789config ROADRUNNER_LARGE_RINGS 2790 bool "Use large TX/RX rings (EXPERIMENTAL)" 2791 depends on ROADRUNNER 2792 help 2793 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 2794 of additional memory to allow for fastest operation, both for 2795 transmitting and receiving. This memory cannot be used by any other 2796 kernel code or by user space programs. Say Y here only if you have 2797 the memory. 2798 2799config PLIP 2800 tristate "PLIP (parallel port) support" 2801 depends on PARPORT 2802 ---help--- 2803 PLIP (Parallel Line Internet Protocol) is used to create a 2804 reasonably fast mini network consisting of two (or, rarely, more) 2805 local machines. A PLIP link from a Linux box is a popular means to 2806 install a Linux distribution on a machine which doesn't have a 2807 CD-ROM drive (a minimal system has to be transferred with floppies 2808 first). The kernels on both machines need to have this PLIP option 2809 enabled for this to work. 2810 2811 The PLIP driver has two modes, mode 0 and mode 1. The parallel 2812 ports (the connectors at the computers with 25 holes) are connected 2813 with "null printer" or "Turbo Laplink" cables which can transmit 4 2814 bits at a time (mode 0) or with special PLIP cables, to be used on 2815 bidirectional parallel ports only, which can transmit 8 bits at a 2816 time (mode 1); you can find the wiring of these cables in 2817 <file:Documentation/networking/PLIP.txt>. The cables can be up to 2818 15m long. Mode 0 works also if one of the machines runs DOS/Windows 2819 and has some PLIP software installed, e.g. the Crynwr PLIP packet 2820 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 2821 and winsock or NCSA's telnet. 2822 2823 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 2824 as the NET-3-HOWTO, both available from 2825 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 2826 protocol has been changed and this PLIP driver won't work together 2827 with the PLIP support in Linux versions 1.0.x. This option enlarges 2828 your kernel by about 8 KB. 2829 2830 To compile this driver as a module, choose M here. The module 2831 will be called plip. If unsure, say Y or M, in case you buy 2832 a laptop later. 2833 2834config PPP 2835 tristate "PPP (point-to-point protocol) support" 2836 select SLHC 2837 ---help--- 2838 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 2839 the same purpose: sending Internet traffic over telephone (and other 2840 serial) lines. Ask your access provider if they support it, because 2841 otherwise you can't use it; most Internet access providers these 2842 days support PPP rather than SLIP. 2843 2844 To use PPP, you need an additional program called pppd as described 2845 in the PPP-HOWTO, available at 2846 <http://www.tldp.org/docs.html#howto>. Make sure that you have 2847 the version of pppd recommended in <file:Documentation/Changes>. 2848 The PPP option enlarges your kernel by about 16 KB. 2849 2850 There are actually two versions of PPP: the traditional PPP for 2851 asynchronous lines, such as regular analog phone lines, and 2852 synchronous PPP which can be used over digital ISDN lines for 2853 example. If you want to use PPP over phone lines or other 2854 asynchronous serial lines, you need to say Y (or M) here and also to 2855 the next option, "PPP support for async serial ports". For PPP over 2856 synchronous lines, you should say Y (or M) here and to "Support 2857 synchronous PPP", below. 2858 2859 If you said Y to "Version information on all symbols" above, then 2860 you cannot compile the PPP driver into the kernel; you can then only 2861 compile it as a module. To compile this driver as a module, choose M 2862 here. The module will be called ppp_generic. 2863 2864config PPP_MULTILINK 2865 bool "PPP multilink support (EXPERIMENTAL)" 2866 depends on PPP && EXPERIMENTAL 2867 help 2868 PPP multilink is a protocol (defined in RFC 1990) which allows you 2869 to combine several (logical or physical) lines into one logical PPP 2870 connection, so that you can utilize your full bandwidth. 2871 2872 This has to be supported at the other end as well and you need a 2873 version of the pppd daemon which understands the multilink protocol. 2874 2875 If unsure, say N. 2876 2877config PPP_FILTER 2878 bool "PPP filtering" 2879 depends on PPP 2880 help 2881 Say Y here if you want to be able to filter the packets passing over 2882 PPP interfaces. This allows you to control which packets count as 2883 activity (i.e. which packets will reset the idle timer or bring up 2884 a demand-dialed link) and which packets are to be dropped entirely. 2885 You need to say Y here if you wish to use the pass-filter and 2886 active-filter options to pppd. 2887 2888 If unsure, say N. 2889 2890config PPP_ASYNC 2891 tristate "PPP support for async serial ports" 2892 depends on PPP 2893 select CRC_CCITT 2894 ---help--- 2895 Say Y (or M) here if you want to be able to use PPP over standard 2896 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 2897 a modem (not a synchronous or ISDN modem) to contact your ISP, you 2898 need this option. 2899 2900 To compile this driver as a module, choose M here. 2901 2902 If unsure, say Y. 2903 2904config PPP_SYNC_TTY 2905 tristate "PPP support for sync tty ports" 2906 depends on PPP 2907 help 2908 Say Y (or M) here if you want to be able to use PPP over synchronous 2909 (HDLC) tty devices, such as the SyncLink adapter. These devices 2910 are often used for high-speed leased lines like T1/E1. 2911 2912 To compile this driver as a module, choose M here. 2913 2914config PPP_DEFLATE 2915 tristate "PPP Deflate compression" 2916 depends on PPP 2917 select ZLIB_INFLATE 2918 select ZLIB_DEFLATE 2919 ---help--- 2920 Support for the Deflate compression method for PPP, which uses the 2921 Deflate algorithm (the same algorithm that gzip uses) to compress 2922 each PPP packet before it is sent over the wire. The machine at the 2923 other end of the PPP link (usually your ISP) has to support the 2924 Deflate compression method as well for this to be useful. Even if 2925 they don't support it, it is safe to say Y here. 2926 2927 To compile this driver as a module, choose M here. 2928 2929config PPP_BSDCOMP 2930 tristate "PPP BSD-Compress compression" 2931 depends on PPP 2932 ---help--- 2933 Support for the BSD-Compress compression method for PPP, which uses 2934 the LZW compression method to compress each PPP packet before it is 2935 sent over the wire. The machine at the other end of the PPP link 2936 (usually your ISP) has to support the BSD-Compress compression 2937 method as well for this to be useful. Even if they don't support it, 2938 it is safe to say Y here. 2939 2940 The PPP Deflate compression method ("PPP Deflate compression", 2941 above) is preferable to BSD-Compress, because it compresses better 2942 and is patent-free. 2943 2944 Note that the BSD compression code will always be compiled as a 2945 module; it is called bsd_comp and will show up in the directory 2946 modules once you have said "make modules". If unsure, say N. 2947 2948config PPP_MPPE 2949 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 2950 depends on PPP && EXPERIMENTAL 2951 select CRYPTO 2952 select CRYPTO_SHA1 2953 select CRYPTO_ARC4 2954 select CRYPTO_ECB 2955 ---help--- 2956 Support for the MPPE Encryption protocol, as employed by the 2957 Microsoft Point-to-Point Tunneling Protocol. 2958 2959 See http://pptpclient.sourceforge.net/ for information on 2960 configuring PPTP clients and servers to utilize this method. 2961 2962config PPPOE 2963 tristate "PPP over Ethernet (EXPERIMENTAL)" 2964 depends on EXPERIMENTAL && PPP 2965 help 2966 Support for PPP over Ethernet. 2967 2968 This driver requires the latest version of pppd from the CVS 2969 repository at cvs.samba.org. Alternatively, see the 2970 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 2971 which contains instruction on how to use this driver (under 2972 the heading "Kernel mode PPPoE"). 2973 2974config PPPOATM 2975 tristate "PPP over ATM" 2976 depends on ATM && PPP 2977 help 2978 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 2979 This implementation does not yet comply with section 8 of RFC2364, 2980 which can lead to bad results if the ATM peer loses state and 2981 changes its encapsulation unilaterally. 2982 2983config PPPOL2TP 2984 tristate "PPP over L2TP (EXPERIMENTAL)" 2985 depends on EXPERIMENTAL && PPP && INET 2986 help 2987 Support for PPP-over-L2TP socket family. L2TP is a protocol 2988 used by ISPs and enterprises to tunnel PPP traffic over UDP 2989 tunnels. L2TP is replacing PPTP for VPN uses. 2990 2991 This kernel component handles only L2TP data packets: a 2992 userland daemon handles L2TP the control protocol (tunnel 2993 and session setup). One such daemon is OpenL2TP 2994 (http://openl2tp.sourceforge.net/). 2995 2996config SLIP 2997 tristate "SLIP (serial line) support" 2998 ---help--- 2999 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 3000 connect to your Internet service provider or to connect to some 3001 other local Unix box or if you want to configure your Linux box as a 3002 Slip/CSlip server for other people to dial in. SLIP (Serial Line 3003 Internet Protocol) is a protocol used to send Internet traffic over 3004 serial connections such as telephone lines or null modem cables; 3005 nowadays, the protocol PPP is more commonly used for this same 3006 purpose. 3007 3008 Normally, your access provider has to support SLIP in order for you 3009 to be able to use it, but there is now a SLIP emulator called SLiRP 3010 around (available from 3011 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3012 allows you to use SLIP over a regular dial up shell connection. If 3013 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 3014 NET-3-HOWTO, available from 3015 <http://www.tldp.org/docs.html#howto>, explains how to 3016 configure SLIP. Note that you don't need this option if you just 3017 want to run term (term is a program which gives you almost full 3018 Internet connectivity if you have a regular dial up shell account on 3019 some Internet connected Unix computer. Read 3020 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 3021 support will enlarge your kernel by about 4 KB. If unsure, say N. 3022 3023 To compile this driver as a module, choose M here. The module 3024 will be called slip. 3025 3026config SLIP_COMPRESSED 3027 bool "CSLIP compressed headers" 3028 depends on SLIP 3029 select SLHC 3030 ---help--- 3031 This protocol is faster than SLIP because it uses compression on the 3032 TCP/IP headers (not on the data itself), but it has to be supported 3033 on both ends. Ask your access provider if you are not sure and 3034 answer Y, just in case. You will still be able to use plain SLIP. If 3035 you plan to use SLiRP, the SLIP emulator (available from 3036 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3037 allows you to use SLIP over a regular dial up shell connection, you 3038 definitely want to say Y here. The NET-3-HOWTO, available from 3039 <http://www.tldp.org/docs.html#howto>, explains how to configure 3040 CSLIP. This won't enlarge your kernel. 3041 3042config SLHC 3043 tristate 3044 help 3045 This option enables Van Jacobsen serial line header compression 3046 routines. 3047 3048config SLIP_SMART 3049 bool "Keepalive and linefill" 3050 depends on SLIP 3051 help 3052 Adds additional capabilities to the SLIP driver to support the 3053 RELCOM line fill and keepalive monitoring. Ideal on poor quality 3054 analogue lines. 3055 3056config SLIP_MODE_SLIP6 3057 bool "Six bit SLIP encapsulation" 3058 depends on SLIP 3059 help 3060 Just occasionally you may need to run IP over hostile serial 3061 networks that don't pass all control characters or are only seven 3062 bit. Saying Y here adds an extra mode you can use with SLIP: 3063 "slip6". In this mode, SLIP will only send normal ASCII symbols over 3064 the serial device. Naturally, this has to be supported at the other 3065 end of the link as well. It's good enough, for example, to run IP 3066 over the async ports of a Camtec JNT Pad. If unsure, say N. 3067 3068config NET_FC 3069 bool "Fibre Channel driver support" 3070 depends on SCSI && PCI 3071 help 3072 Fibre Channel is a high speed serial protocol mainly used to connect 3073 large storage devices to the computer; it is compatible with and 3074 intended to replace SCSI. 3075 3076 If you intend to use Fibre Channel, you need to have a Fibre channel 3077 adaptor card in your computer; say Y here and to the driver for your 3078 adaptor below. You also should have said Y to "SCSI support" and 3079 "SCSI generic support". 3080 3081config NETCONSOLE 3082 tristate "Network console logging support (EXPERIMENTAL)" 3083 depends on EXPERIMENTAL 3084 ---help--- 3085 If you want to log kernel messages over the network, enable this. 3086 See <file:Documentation/networking/netconsole.txt> for details. 3087 3088config NETCONSOLE_DYNAMIC 3089 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)" 3090 depends on NETCONSOLE && SYSFS && EXPERIMENTAL 3091 select CONFIGFS_FS 3092 help 3093 This option enables the ability to dynamically reconfigure target 3094 parameters (interface, IP addresses, port numbers, MAC addresses) 3095 at runtime through a userspace interface exported using configfs. 3096 See <file:Documentation/networking/netconsole.txt> for details. 3097 3098config NETPOLL 3099 def_bool NETCONSOLE 3100 3101config NETPOLL_TRAP 3102 bool "Netpoll traffic trapping" 3103 default n 3104 depends on NETPOLL 3105 3106config NET_POLL_CONTROLLER 3107 def_bool NETPOLL 3108 3109config VIRTIO_NET 3110 tristate "Virtio network driver (EXPERIMENTAL)" 3111 depends on EXPERIMENTAL && VIRTIO 3112 ---help--- 3113 This is the virtual network driver for lguest. Say Y or M. 3114 3115endif # NETDEVICES 3116