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 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 E1000E_ENABLED 2013 def_bool E1000E != n 2014 2015config IP1000 2016 tristate "IP1000 Gigabit Ethernet support" 2017 depends on PCI && EXPERIMENTAL 2018 select MII 2019 ---help--- 2020 This driver supports IP1000 gigabit Ethernet cards. 2021 2022 To compile this driver as a module, choose M here: the module 2023 will be called ipg. This is recommended. 2024 2025config IGB 2026 tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support" 2027 depends on PCI 2028 ---help--- 2029 This driver supports Intel(R) 82575 gigabit ethernet family of 2030 adapters. For more information on how to identify your adapter, go 2031 to the Adapter & Driver ID Guide at: 2032 2033 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2034 2035 For general information and support, go to the Intel support 2036 website at: 2037 2038 <http://support.intel.com> 2039 2040 More specific information on configuring the driver is in 2041 <file:Documentation/networking/e1000.txt>. 2042 2043 To compile this driver as a module, choose M here and read 2044 <file:Documentation/networking/net-modules.txt>. The module 2045 will be called igb. 2046 2047source "drivers/net/ixp2000/Kconfig" 2048 2049config MYRI_SBUS 2050 tristate "MyriCOM Gigabit Ethernet support" 2051 depends on SBUS 2052 help 2053 This driver supports MyriCOM Sbus gigabit Ethernet cards. 2054 2055 To compile this driver as a module, choose M here: the module 2056 will be called myri_sbus. This is recommended. 2057 2058config NS83820 2059 tristate "National Semiconductor DP83820 support" 2060 depends on PCI 2061 help 2062 This is a driver for the National Semiconductor DP83820 series 2063 of gigabit ethernet MACs. Cards using this chipset include 2064 the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX, 2065 SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of 2066 zero copy. 2067 2068config HAMACHI 2069 tristate "Packet Engines Hamachi GNIC-II support" 2070 depends on PCI 2071 select MII 2072 help 2073 If you have a Gigabit Ethernet card of this type, say Y and read 2074 the Ethernet-HOWTO, available from 2075 <http://www.tldp.org/docs.html#howto>. 2076 2077 To compile this driver as a module, choose M here. The module will be 2078 called hamachi. 2079 2080config YELLOWFIN 2081 tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)" 2082 depends on PCI && EXPERIMENTAL 2083 select CRC32 2084 ---help--- 2085 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet 2086 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is 2087 used by the Beowulf Linux cluster project. See 2088 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more 2089 information about this driver in particular and Beowulf in general. 2090 2091 To compile this driver as a module, choose M here: the module 2092 will be called yellowfin. This is recommended. 2093 2094config R8169 2095 tristate "Realtek 8169 gigabit ethernet support" 2096 depends on PCI 2097 select CRC32 2098 ---help--- 2099 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter. 2100 2101 To compile this driver as a module, choose M here: the module 2102 will be called r8169. This is recommended. 2103 2104config R8169_NAPI 2105 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 2106 depends on R8169 && EXPERIMENTAL 2107 help 2108 NAPI is a new driver API designed to reduce CPU and interrupt load 2109 when the driver is receiving lots of packets from the card. It is 2110 still somewhat experimental and thus not yet enabled by default. 2111 2112 If your estimated Rx load is 10kpps or more, or if the card will be 2113 deployed on potentially unfriendly networks (e.g. in a firewall), 2114 then say Y here. 2115 2116 If in doubt, say N. 2117 2118config R8169_VLAN 2119 bool "VLAN support" 2120 depends on R8169 && VLAN_8021Q 2121 ---help--- 2122 Say Y here for the r8169 driver to support the functions required 2123 by the kernel 802.1Q code. 2124 2125 If in doubt, say Y. 2126 2127config SB1250_MAC 2128 tristate "SB1250 Gigabit Ethernet support" 2129 depends on SIBYTE_SB1xxx_SOC 2130 select PHYLIB 2131 ---help--- 2132 This driver supports Gigabit Ethernet interfaces based on the 2133 Broadcom SiByte family of System-On-a-Chip parts. They include 2134 the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455 2135 and BCM1480 chips. 2136 2137 To compile this driver as a module, choose M here: the module 2138 will be called sb1250-mac. 2139 2140config SIS190 2141 tristate "SiS190/SiS191 gigabit ethernet support" 2142 depends on PCI 2143 select CRC32 2144 select MII 2145 ---help--- 2146 Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or 2147 a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to 2148 appear in lan on motherboard designs which are based on SiS 965 2149 and SiS 966 south bridge. 2150 2151 To compile this driver as a module, choose M here: the module 2152 will be called sis190. This is recommended. 2153 2154config SKGE 2155 tristate "New SysKonnect GigaEthernet support" 2156 depends on PCI 2157 select CRC32 2158 ---help--- 2159 This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2160 and related Gigabit Ethernet adapters. It is a new smaller driver 2161 with better performance and more complete ethtool support. 2162 2163 It does not support the link failover and network management 2164 features that "portable" vendor supplied sk98lin driver does. 2165 2166 This driver supports adapters based on the original Yukon chipset: 2167 Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T, 2168 Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872. 2169 2170 It does not support the newer Yukon2 chipset: a separate driver, 2171 sky2, is provided for Yukon2-based adapters. 2172 2173 To compile this driver as a module, choose M here: the module 2174 will be called skge. This is recommended. 2175 2176config SKGE_DEBUG 2177 bool "Debugging interface" 2178 depends on SKGE && DEBUG_FS 2179 help 2180 This option adds the ability to dump driver state for debugging. 2181 The file debugfs/skge/ethX displays the state of the internal 2182 transmit and receive rings. 2183 2184 If unsure, say N. 2185 2186config SKY2 2187 tristate "SysKonnect Yukon2 support" 2188 depends on PCI 2189 select CRC32 2190 ---help--- 2191 This driver supports Gigabit Ethernet adapters based on the 2192 Marvell Yukon 2 chipset: 2193 Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/ 2194 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21 2195 2196 There is companion driver for the older Marvell Yukon and 2197 Genesis based adapters: skge. 2198 2199 To compile this driver as a module, choose M here: the module 2200 will be called sky2. This is recommended. 2201 2202config SKY2_DEBUG 2203 bool "Debugging interface" 2204 depends on SKY2 && DEBUG_FS 2205 help 2206 This option adds the ability to dump driver state for debugging. 2207 The file debugfs/sky2/ethX displays the state of the internal 2208 transmit and receive rings. 2209 2210 If unsure, say N. 2211 2212config SK98LIN 2213 tristate "Marvell Yukon Chipset / SysKonnect SK-98xx Support (DEPRECATED)" 2214 depends on PCI 2215 ---help--- 2216 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx 2217 compliant Gigabit Ethernet Adapter. 2218 2219 This driver supports the original Yukon chipset. This driver is 2220 deprecated and will be removed from the kernel in the near future, 2221 it has been replaced by the skge driver. skge is cleaner and 2222 seems to work better. 2223 2224 This driver does not support the newer Yukon2 chipset. A separate 2225 driver, sky2, is provided to support Yukon2-based adapters. 2226 2227 The following adapters are supported by this driver: 2228 - 3Com 3C940 Gigabit LOM Ethernet Adapter 2229 - 3Com 3C941 Gigabit LOM Ethernet Adapter 2230 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter 2231 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter 2232 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter 2233 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter 2234 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter 2235 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter 2236 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter 2237 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter 2238 - Belkin Gigabit Desktop Card 10/100/1000Base-T Adapter, Copper RJ-45 2239 - EG1032 v2 Instant Gigabit Network Adapter 2240 - EG1064 v2 Instant Gigabit Network Adapter 2241 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit) 2242 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron) 2243 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus) 2244 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS) 2245 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox) 2246 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn) 2247 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte) 2248 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill) 2249 - Marvell 88E8050 Gigabit LOM Ethernet Adapter (Intel) 2250 - Marvell RDK-8001 Adapter 2251 - Marvell RDK-8002 Adapter 2252 - Marvell RDK-8003 Adapter 2253 - Marvell RDK-8004 Adapter 2254 - Marvell RDK-8006 Adapter 2255 - Marvell RDK-8007 Adapter 2256 - Marvell RDK-8008 Adapter 2257 - Marvell RDK-8009 Adapter 2258 - Marvell RDK-8010 Adapter 2259 - Marvell RDK-8011 Adapter 2260 - Marvell RDK-8012 Adapter 2261 - Marvell RDK-8052 Adapter 2262 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit) 2263 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit) 2264 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L) 2265 - SK-9521 10/100/1000Base-T Adapter 2266 - SK-9521 V2.0 10/100/1000Base-T Adapter 2267 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T) 2268 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter 2269 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link) 2270 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX) 2271 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter 2272 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link) 2273 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX) 2274 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter 2275 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link) 2276 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter 2277 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition) 2278 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter 2279 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link) 2280 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX) 2281 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter 2282 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link) 2283 - SMC EZ Card 1000 (SMC9452TXV.2) 2284 2285 The adapters support Jumbo Frames. 2286 The dual link adapters support link-failover and dual port features. 2287 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support 2288 the scatter-gather functionality with sendfile(). Please refer to 2289 <file:Documentation/networking/sk98lin.txt> for more information about 2290 optional driver parameters. 2291 Questions concerning this driver may be addressed to: 2292 <linux@syskonnect.de> 2293 2294 If you want to compile this driver as a module ( = code which can be 2295 inserted in and removed from the running kernel whenever you want), 2296 say M here and read <file:Documentation/kbuild/modules.txt>. The module will 2297 be called sk98lin. This is recommended. 2298 2299config VIA_VELOCITY 2300 tristate "VIA Velocity support" 2301 depends on PCI 2302 select CRC32 2303 select CRC_CCITT 2304 select MII 2305 help 2306 If you have a VIA "Velocity" based network card say Y here. 2307 2308 To compile this driver as a module, choose M here. The module 2309 will be called via-velocity. 2310 2311config TIGON3 2312 tristate "Broadcom Tigon3 support" 2313 depends on PCI 2314 help 2315 This driver supports Broadcom Tigon3 based gigabit Ethernet cards. 2316 2317 To compile this driver as a module, choose M here: the module 2318 will be called tg3. This is recommended. 2319 2320config BNX2 2321 tristate "Broadcom NetXtremeII support" 2322 depends on PCI 2323 select CRC32 2324 select ZLIB_INFLATE 2325 help 2326 This driver supports Broadcom NetXtremeII gigabit Ethernet cards. 2327 2328 To compile this driver as a module, choose M here: the module 2329 will be called bnx2. This is recommended. 2330 2331config SPIDER_NET 2332 tristate "Spider Gigabit Ethernet driver" 2333 depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB) 2334 select FW_LOADER 2335 help 2336 This driver supports the Gigabit Ethernet chips present on the 2337 Cell Processor-Based Blades from IBM. 2338 2339config TSI108_ETH 2340 tristate "Tundra TSI108 gigabit Ethernet support" 2341 depends on TSI108_BRIDGE 2342 help 2343 This driver supports Tundra TSI108 gigabit Ethernet ports. 2344 To compile this driver as a module, choose M here: the module 2345 will be called tsi108_eth. 2346 2347config GELIC_NET 2348 tristate "PS3 Gigabit Ethernet driver" 2349 depends on PPC_PS3 2350 help 2351 This driver supports the network device on the PS3 game 2352 console. This driver has built-in support for Ethernet. 2353 2354 To compile this driver as a module, choose M here: the 2355 module will be called ps3_gelic. 2356 2357config GIANFAR 2358 tristate "Gianfar Ethernet" 2359 depends on FSL_SOC 2360 select PHYLIB 2361 select CRC32 2362 help 2363 This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx, 2364 and MPC86xx family of chips, and the FEC on the 8540. 2365 2366config GFAR_NAPI 2367 bool "Use Rx Polling (NAPI)" 2368 depends on GIANFAR 2369 2370config UCC_GETH 2371 tristate "Freescale QE Gigabit Ethernet" 2372 depends on QUICC_ENGINE 2373 select PHYLIB 2374 help 2375 This driver supports the Gigabit Ethernet mode of the QUICC Engine, 2376 which is available on some Freescale SOCs. 2377 2378config UGETH_NAPI 2379 bool "Use Rx Polling (NAPI)" 2380 depends on UCC_GETH 2381 2382config UGETH_MAGIC_PACKET 2383 bool "Magic Packet detection support" 2384 depends on UCC_GETH 2385 2386config UGETH_FILTERING 2387 bool "Mac address filtering support" 2388 depends on UCC_GETH 2389 2390config UGETH_TX_ON_DEMAND 2391 bool "Transmit on Demand support" 2392 depends on UCC_GETH 2393 2394config MV643XX_ETH 2395 tristate "Marvell Discovery (643XX) and Orion ethernet support" 2396 depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || ARCH_ORION 2397 select MII 2398 help 2399 This driver supports the gigabit ethernet MACs in the 2400 Marvell Discovery PPC/MIPS chipset family (MV643XX) and 2401 in the Marvell Orion ARM SoC family. 2402 2403 Some boards that use the Discovery chipset are the Momenco 2404 Ocelot C and Jaguar ATX and Pegasos II. 2405 2406config QLA3XXX 2407 tristate "QLogic QLA3XXX Network Driver Support" 2408 depends on PCI 2409 help 2410 This driver supports QLogic ISP3XXX gigabit Ethernet cards. 2411 2412 To compile this driver as a module, choose M here: the module 2413 will be called qla3xxx. 2414 2415config ATL1 2416 tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)" 2417 depends on PCI && EXPERIMENTAL 2418 select CRC32 2419 select MII 2420 help 2421 This driver supports the Attansic L1 gigabit ethernet adapter. 2422 2423 To compile this driver as a module, choose M here. The module 2424 will be called atl1. 2425 2426endif # NETDEV_1000 2427 2428# 2429# 10 Gigabit Ethernet 2430# 2431 2432menuconfig NETDEV_10000 2433 bool "Ethernet (10000 Mbit)" 2434 depends on !UML 2435 default y 2436 ---help--- 2437 Say Y here to get to see options for 10 Gigabit Ethernet drivers. 2438 This option alone does not add any kernel code. 2439 2440 If you say N, all options in this submenu will be skipped and disabled. 2441 2442if NETDEV_10000 2443 2444config CHELSIO_T1 2445 tristate "Chelsio 10Gb Ethernet support" 2446 depends on PCI 2447 select CRC32 2448 help 2449 This driver supports Chelsio gigabit and 10-gigabit 2450 Ethernet cards. More information about adapter features and 2451 performance tuning is in <file:Documentation/networking/cxgb.txt>. 2452 2453 For general information about Chelsio and our products, visit 2454 our website at <http://www.chelsio.com>. 2455 2456 For customer support, please visit our customer support page at 2457 <http://www.chelsio.com/support.htm>. 2458 2459 Please send feedback to <linux-bugs@chelsio.com>. 2460 2461 To compile this driver as a module, choose M here: the module 2462 will be called cxgb. 2463 2464config CHELSIO_T1_1G 2465 bool "Chelsio gigabit Ethernet support" 2466 depends on CHELSIO_T1 2467 help 2468 Enables support for Chelsio's gigabit Ethernet PCI cards. If you 2469 are using only 10G cards say 'N' here. 2470 2471config CHELSIO_T1_NAPI 2472 bool "Use Rx Polling (NAPI)" 2473 depends on CHELSIO_T1 2474 default y 2475 help 2476 NAPI is a driver API designed to reduce CPU and interrupt load 2477 when the driver is receiving lots of packets from the card. 2478 2479config CHELSIO_T3 2480 tristate "Chelsio Communications T3 10Gb Ethernet support" 2481 depends on PCI 2482 select FW_LOADER 2483 help 2484 This driver supports Chelsio T3-based gigabit and 10Gb Ethernet 2485 adapters. 2486 2487 For general information about Chelsio and our products, visit 2488 our website at <http://www.chelsio.com>. 2489 2490 For customer support, please visit our customer support page at 2491 <http://www.chelsio.com/support.htm>. 2492 2493 Please send feedback to <linux-bugs@chelsio.com>. 2494 2495 To compile this driver as a module, choose M here: the module 2496 will be called cxgb3. 2497 2498config EHEA 2499 tristate "eHEA Ethernet support" 2500 depends on IBMEBUS && INET 2501 select INET_LRO 2502 ---help--- 2503 This driver supports the IBM pSeries eHEA ethernet adapter. 2504 2505 To compile the driver as a module, choose M here. The module 2506 will be called ehea. 2507 2508config IXGBE 2509 tristate "Intel(R) 10GbE PCI Express adapters support" 2510 depends on PCI 2511 ---help--- 2512 This driver supports Intel(R) 10GbE PCI Express family of 2513 adapters. For more information on how to identify your adapter, go 2514 to the Adapter & Driver ID Guide at: 2515 2516 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2517 2518 For general information and support, go to the Intel support 2519 website at: 2520 2521 <http://support.intel.com> 2522 2523 To compile this driver as a module, choose M here. The module 2524 will be called ixgbe. 2525 2526config IXGB 2527 tristate "Intel(R) PRO/10GbE support" 2528 depends on PCI 2529 ---help--- 2530 This driver supports Intel(R) PRO/10GbE family of adapters for 2531 PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver 2532 instead. For more information on how to identify your adapter, go 2533 to the Adapter & Driver ID Guide at: 2534 2535 <http://support.intel.com/support/network/adapter/pro100/21397.htm> 2536 2537 For general information and support, go to the Intel support 2538 website at: 2539 2540 <http://support.intel.com> 2541 2542 More specific information on configuring the driver is in 2543 <file:Documentation/networking/ixgb.txt>. 2544 2545 To compile this driver as a module, choose M here. The module 2546 will be called ixgb. 2547 2548config IXGB_NAPI 2549 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 2550 depends on IXGB && EXPERIMENTAL 2551 help 2552 NAPI is a new driver API designed to reduce CPU and interrupt load 2553 when the driver is receiving lots of packets from the card. It is 2554 still somewhat experimental and thus not yet enabled by default. 2555 2556 If your estimated Rx load is 10kpps or more, or if the card will be 2557 deployed on potentially unfriendly networks (e.g. in a firewall), 2558 then say Y here. 2559 2560 If in doubt, say N. 2561 2562config S2IO 2563 tristate "S2IO 10Gbe XFrame NIC" 2564 depends on PCI 2565 ---help--- 2566 This driver supports the 10Gbe XFrame NIC of S2IO. 2567 More specific information on configuring the driver is in 2568 <file:Documentation/networking/s2io.txt>. 2569 2570config S2IO_NAPI 2571 bool "Use Rx Polling (NAPI) (EXPERIMENTAL)" 2572 depends on S2IO && EXPERIMENTAL 2573 help 2574 NAPI is a new driver API designed to reduce CPU and interrupt load 2575 when the driver is receiving lots of packets from the card. It is 2576 still somewhat experimental and thus not yet enabled by default. 2577 2578 If your estimated Rx load is 10kpps or more, or if the card will be 2579 deployed on potentially unfriendly networks (e.g. in a firewall), 2580 then say Y here. 2581 2582 If in doubt, say N. 2583 2584config MYRI10GE 2585 tristate "Myricom Myri-10G Ethernet support" 2586 depends on PCI && INET 2587 select FW_LOADER 2588 select CRC32 2589 select INET_LRO 2590 ---help--- 2591 This driver supports Myricom Myri-10G Dual Protocol interface in 2592 Ethernet mode. If the eeprom on your board is not recent enough, 2593 you will need a newer firmware image. 2594 You may get this image or more information, at: 2595 2596 <http://www.myri.com/scs/download-Myri10GE.html> 2597 2598 To compile this driver as a module, choose M here. The module 2599 will be called myri10ge. 2600 2601config NETXEN_NIC 2602 tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC" 2603 depends on PCI 2604 help 2605 This enables the support for NetXen's Gigabit Ethernet card. 2606 2607config NIU 2608 tristate "Sun Neptune 10Gbit Ethernet support" 2609 depends on PCI 2610 help 2611 This enables support for cards based upon Sun's 2612 Neptune chipset. 2613 2614config PASEMI_MAC 2615 tristate "PA Semi 1/10Gbit MAC" 2616 depends on PPC64 && PCI 2617 select PHYLIB 2618 select INET_LRO 2619 help 2620 This driver supports the on-chip 1/10Gbit Ethernet controller on 2621 PA Semi's PWRficient line of chips. 2622 2623config MLX4_CORE 2624 tristate 2625 depends on PCI 2626 default n 2627 2628config MLX4_DEBUG 2629 bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED) 2630 depends on MLX4_CORE 2631 default y 2632 ---help--- 2633 This option causes debugging code to be compiled into the 2634 mlx4_core driver. The output can be turned on via the 2635 debug_level module parameter (which can also be set after 2636 the driver is loaded through sysfs). 2637 2638config TEHUTI 2639 tristate "Tehuti Networks 10G Ethernet" 2640 depends on PCI 2641 help 2642 Tehuti Networks 10G Ethernet NIC 2643 2644config BNX2X 2645 tristate "Broadcom NetXtremeII 10Gb support" 2646 depends on PCI 2647 select ZLIB_INFLATE 2648 help 2649 This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards. 2650 To compile this driver as a module, choose M here: the module 2651 will be called bnx2x. This is recommended. 2652 2653 2654endif # NETDEV_10000 2655 2656source "drivers/net/tokenring/Kconfig" 2657 2658source "drivers/net/wireless/Kconfig" 2659 2660source "drivers/net/usb/Kconfig" 2661 2662source "drivers/net/pcmcia/Kconfig" 2663 2664source "drivers/net/wan/Kconfig" 2665 2666source "drivers/atm/Kconfig" 2667 2668source "drivers/s390/net/Kconfig" 2669 2670config XEN_NETDEV_FRONTEND 2671 tristate "Xen network device frontend driver" 2672 depends on XEN 2673 default y 2674 help 2675 The network device frontend driver allows the kernel to 2676 access network devices exported exported by a virtual 2677 machine containing a physical network device driver. The 2678 frontend driver is intended for unprivileged guest domains; 2679 if you are compiling a kernel for a Xen guest, you almost 2680 certainly want to enable this. 2681 2682config ISERIES_VETH 2683 tristate "iSeries Virtual Ethernet driver support" 2684 depends on PPC_ISERIES 2685 2686config RIONET 2687 tristate "RapidIO Ethernet over messaging driver support" 2688 depends on RAPIDIO 2689 2690config RIONET_TX_SIZE 2691 int "Number of outbound queue entries" 2692 depends on RIONET 2693 default "128" 2694 2695config RIONET_RX_SIZE 2696 int "Number of inbound queue entries" 2697 depends on RIONET 2698 default "128" 2699 2700config FDDI 2701 bool "FDDI driver support" 2702 depends on (PCI || EISA || TC) 2703 help 2704 Fiber Distributed Data Interface is a high speed local area network 2705 design; essentially a replacement for high speed Ethernet. FDDI can 2706 run over copper or fiber. If you are connected to such a network and 2707 want a driver for the FDDI card in your computer, say Y here (and 2708 then also Y to the driver for your FDDI card, below). Most people 2709 will say N. 2710 2711config DEFXX 2712 tristate "Digital DEFTA/DEFEA/DEFPA adapter support" 2713 depends on FDDI && (PCI || EISA || TC) 2714 ---help--- 2715 This is support for the DIGITAL series of TURBOchannel (DEFTA), 2716 EISA (DEFEA) and PCI (DEFPA) controllers which can connect you 2717 to a local FDDI network. 2718 2719 To compile this driver as a module, choose M here: the module 2720 will be called defxx. If unsure, say N. 2721 2722config DEFXX_MMIO 2723 bool 2724 prompt "Use MMIO instead of PIO" if PCI || EISA 2725 depends on DEFXX 2726 default n if PCI || EISA 2727 default y 2728 ---help--- 2729 This instructs the driver to use EISA or PCI memory-mapped I/O 2730 (MMIO) as appropriate instead of programmed I/O ports (PIO). 2731 Enabling this gives an improvement in processing time in parts 2732 of the driver, but it may cause problems with EISA (DEFEA) 2733 adapters. TURBOchannel does not have the concept of I/O ports, 2734 so MMIO is always used for these (DEFTA) adapters. 2735 2736 If unsure, say N. 2737 2738config SKFP 2739 tristate "SysKonnect FDDI PCI support" 2740 depends on FDDI && PCI 2741 select BITREVERSE 2742 ---help--- 2743 Say Y here if you have a SysKonnect FDDI PCI adapter. 2744 The following adapters are supported by this driver: 2745 - SK-5521 (SK-NET FDDI-UP) 2746 - SK-5522 (SK-NET FDDI-UP DAS) 2747 - SK-5541 (SK-NET FDDI-FP) 2748 - SK-5543 (SK-NET FDDI-LP) 2749 - SK-5544 (SK-NET FDDI-LP DAS) 2750 - SK-5821 (SK-NET FDDI-UP64) 2751 - SK-5822 (SK-NET FDDI-UP64 DAS) 2752 - SK-5841 (SK-NET FDDI-FP64) 2753 - SK-5843 (SK-NET FDDI-LP64) 2754 - SK-5844 (SK-NET FDDI-LP64 DAS) 2755 - Netelligent 100 FDDI DAS Fibre SC 2756 - Netelligent 100 FDDI SAS Fibre SC 2757 - Netelligent 100 FDDI DAS UTP 2758 - Netelligent 100 FDDI SAS UTP 2759 - Netelligent 100 FDDI SAS Fibre MIC 2760 2761 Read <file:Documentation/networking/skfp.txt> for information about 2762 the driver. 2763 2764 Questions concerning this driver can be addressed to: 2765 <linux@syskonnect.de> 2766 2767 To compile this driver as a module, choose M here: the module 2768 will be called skfp. This is recommended. 2769 2770config HIPPI 2771 bool "HIPPI driver support (EXPERIMENTAL)" 2772 depends on EXPERIMENTAL && INET && PCI 2773 help 2774 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and 2775 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI 2776 can run over copper (25m) or fiber (300m on multi-mode or 10km on 2777 single-mode). HIPPI networks are commonly used for clusters and to 2778 connect to super computers. If you are connected to a HIPPI network 2779 and have a HIPPI network card in your computer that you want to use 2780 under Linux, say Y here (you must also remember to enable the driver 2781 for your HIPPI card below). Most people will say N here. 2782 2783config ROADRUNNER 2784 tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)" 2785 depends on HIPPI && PCI 2786 help 2787 Say Y here if this is your PCI HIPPI network card. 2788 2789 To compile this driver as a module, choose M here: the module 2790 will be called rrunner. If unsure, say N. 2791 2792config ROADRUNNER_LARGE_RINGS 2793 bool "Use large TX/RX rings (EXPERIMENTAL)" 2794 depends on ROADRUNNER 2795 help 2796 If you say Y here, the RoadRunner driver will preallocate up to 2 MB 2797 of additional memory to allow for fastest operation, both for 2798 transmitting and receiving. This memory cannot be used by any other 2799 kernel code or by user space programs. Say Y here only if you have 2800 the memory. 2801 2802config PLIP 2803 tristate "PLIP (parallel port) support" 2804 depends on PARPORT 2805 ---help--- 2806 PLIP (Parallel Line Internet Protocol) is used to create a 2807 reasonably fast mini network consisting of two (or, rarely, more) 2808 local machines. A PLIP link from a Linux box is a popular means to 2809 install a Linux distribution on a machine which doesn't have a 2810 CD-ROM drive (a minimal system has to be transferred with floppies 2811 first). The kernels on both machines need to have this PLIP option 2812 enabled for this to work. 2813 2814 The PLIP driver has two modes, mode 0 and mode 1. The parallel 2815 ports (the connectors at the computers with 25 holes) are connected 2816 with "null printer" or "Turbo Laplink" cables which can transmit 4 2817 bits at a time (mode 0) or with special PLIP cables, to be used on 2818 bidirectional parallel ports only, which can transmit 8 bits at a 2819 time (mode 1); you can find the wiring of these cables in 2820 <file:Documentation/networking/PLIP.txt>. The cables can be up to 2821 15m long. Mode 0 works also if one of the machines runs DOS/Windows 2822 and has some PLIP software installed, e.g. the Crynwr PLIP packet 2823 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>) 2824 and winsock or NCSA's telnet. 2825 2826 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well 2827 as the NET-3-HOWTO, both available from 2828 <http://www.tldp.org/docs.html#howto>. Note that the PLIP 2829 protocol has been changed and this PLIP driver won't work together 2830 with the PLIP support in Linux versions 1.0.x. This option enlarges 2831 your kernel by about 8 KB. 2832 2833 To compile this driver as a module, choose M here. The module 2834 will be called plip. If unsure, say Y or M, in case you buy 2835 a laptop later. 2836 2837config PPP 2838 tristate "PPP (point-to-point protocol) support" 2839 select SLHC 2840 ---help--- 2841 PPP (Point to Point Protocol) is a newer and better SLIP. It serves 2842 the same purpose: sending Internet traffic over telephone (and other 2843 serial) lines. Ask your access provider if they support it, because 2844 otherwise you can't use it; most Internet access providers these 2845 days support PPP rather than SLIP. 2846 2847 To use PPP, you need an additional program called pppd as described 2848 in the PPP-HOWTO, available at 2849 <http://www.tldp.org/docs.html#howto>. Make sure that you have 2850 the version of pppd recommended in <file:Documentation/Changes>. 2851 The PPP option enlarges your kernel by about 16 KB. 2852 2853 There are actually two versions of PPP: the traditional PPP for 2854 asynchronous lines, such as regular analog phone lines, and 2855 synchronous PPP which can be used over digital ISDN lines for 2856 example. If you want to use PPP over phone lines or other 2857 asynchronous serial lines, you need to say Y (or M) here and also to 2858 the next option, "PPP support for async serial ports". For PPP over 2859 synchronous lines, you should say Y (or M) here and to "Support 2860 synchronous PPP", below. 2861 2862 If you said Y to "Version information on all symbols" above, then 2863 you cannot compile the PPP driver into the kernel; you can then only 2864 compile it as a module. To compile this driver as a module, choose M 2865 here. The module will be called ppp_generic. 2866 2867config PPP_MULTILINK 2868 bool "PPP multilink support (EXPERIMENTAL)" 2869 depends on PPP && EXPERIMENTAL 2870 help 2871 PPP multilink is a protocol (defined in RFC 1990) which allows you 2872 to combine several (logical or physical) lines into one logical PPP 2873 connection, so that you can utilize your full bandwidth. 2874 2875 This has to be supported at the other end as well and you need a 2876 version of the pppd daemon which understands the multilink protocol. 2877 2878 If unsure, say N. 2879 2880config PPP_FILTER 2881 bool "PPP filtering" 2882 depends on PPP 2883 help 2884 Say Y here if you want to be able to filter the packets passing over 2885 PPP interfaces. This allows you to control which packets count as 2886 activity (i.e. which packets will reset the idle timer or bring up 2887 a demand-dialed link) and which packets are to be dropped entirely. 2888 You need to say Y here if you wish to use the pass-filter and 2889 active-filter options to pppd. 2890 2891 If unsure, say N. 2892 2893config PPP_ASYNC 2894 tristate "PPP support for async serial ports" 2895 depends on PPP 2896 select CRC_CCITT 2897 ---help--- 2898 Say Y (or M) here if you want to be able to use PPP over standard 2899 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use 2900 a modem (not a synchronous or ISDN modem) to contact your ISP, you 2901 need this option. 2902 2903 To compile this driver as a module, choose M here. 2904 2905 If unsure, say Y. 2906 2907config PPP_SYNC_TTY 2908 tristate "PPP support for sync tty ports" 2909 depends on PPP 2910 help 2911 Say Y (or M) here if you want to be able to use PPP over synchronous 2912 (HDLC) tty devices, such as the SyncLink adapter. These devices 2913 are often used for high-speed leased lines like T1/E1. 2914 2915 To compile this driver as a module, choose M here. 2916 2917config PPP_DEFLATE 2918 tristate "PPP Deflate compression" 2919 depends on PPP 2920 select ZLIB_INFLATE 2921 select ZLIB_DEFLATE 2922 ---help--- 2923 Support for the Deflate compression method for PPP, which uses the 2924 Deflate algorithm (the same algorithm that gzip uses) to compress 2925 each PPP packet before it is sent over the wire. The machine at the 2926 other end of the PPP link (usually your ISP) has to support the 2927 Deflate compression method as well for this to be useful. Even if 2928 they don't support it, it is safe to say Y here. 2929 2930 To compile this driver as a module, choose M here. 2931 2932config PPP_BSDCOMP 2933 tristate "PPP BSD-Compress compression" 2934 depends on PPP 2935 ---help--- 2936 Support for the BSD-Compress compression method for PPP, which uses 2937 the LZW compression method to compress each PPP packet before it is 2938 sent over the wire. The machine at the other end of the PPP link 2939 (usually your ISP) has to support the BSD-Compress compression 2940 method as well for this to be useful. Even if they don't support it, 2941 it is safe to say Y here. 2942 2943 The PPP Deflate compression method ("PPP Deflate compression", 2944 above) is preferable to BSD-Compress, because it compresses better 2945 and is patent-free. 2946 2947 Note that the BSD compression code will always be compiled as a 2948 module; it is called bsd_comp and will show up in the directory 2949 modules once you have said "make modules". If unsure, say N. 2950 2951config PPP_MPPE 2952 tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)" 2953 depends on PPP && EXPERIMENTAL 2954 select CRYPTO 2955 select CRYPTO_SHA1 2956 select CRYPTO_ARC4 2957 select CRYPTO_ECB 2958 ---help--- 2959 Support for the MPPE Encryption protocol, as employed by the 2960 Microsoft Point-to-Point Tunneling Protocol. 2961 2962 See http://pptpclient.sourceforge.net/ for information on 2963 configuring PPTP clients and servers to utilize this method. 2964 2965config PPPOE 2966 tristate "PPP over Ethernet (EXPERIMENTAL)" 2967 depends on EXPERIMENTAL && PPP 2968 help 2969 Support for PPP over Ethernet. 2970 2971 This driver requires the latest version of pppd from the CVS 2972 repository at cvs.samba.org. Alternatively, see the 2973 RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>) 2974 which contains instruction on how to use this driver (under 2975 the heading "Kernel mode PPPoE"). 2976 2977config PPPOATM 2978 tristate "PPP over ATM" 2979 depends on ATM && PPP 2980 help 2981 Support PPP (Point to Point Protocol) encapsulated in ATM frames. 2982 This implementation does not yet comply with section 8 of RFC2364, 2983 which can lead to bad results if the ATM peer loses state and 2984 changes its encapsulation unilaterally. 2985 2986config PPPOL2TP 2987 tristate "PPP over L2TP (EXPERIMENTAL)" 2988 depends on EXPERIMENTAL && PPP && INET 2989 help 2990 Support for PPP-over-L2TP socket family. L2TP is a protocol 2991 used by ISPs and enterprises to tunnel PPP traffic over UDP 2992 tunnels. L2TP is replacing PPTP for VPN uses. 2993 2994 This kernel component handles only L2TP data packets: a 2995 userland daemon handles L2TP the control protocol (tunnel 2996 and session setup). One such daemon is OpenL2TP 2997 (http://openl2tp.sourceforge.net/). 2998 2999config SLIP 3000 tristate "SLIP (serial line) support" 3001 ---help--- 3002 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to 3003 connect to your Internet service provider or to connect to some 3004 other local Unix box or if you want to configure your Linux box as a 3005 Slip/CSlip server for other people to dial in. SLIP (Serial Line 3006 Internet Protocol) is a protocol used to send Internet traffic over 3007 serial connections such as telephone lines or null modem cables; 3008 nowadays, the protocol PPP is more commonly used for this same 3009 purpose. 3010 3011 Normally, your access provider has to support SLIP in order for you 3012 to be able to use it, but there is now a SLIP emulator called SLiRP 3013 around (available from 3014 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3015 allows you to use SLIP over a regular dial up shell connection. If 3016 you plan to use SLiRP, make sure to say Y to CSLIP, below. The 3017 NET-3-HOWTO, available from 3018 <http://www.tldp.org/docs.html#howto>, explains how to 3019 configure SLIP. Note that you don't need this option if you just 3020 want to run term (term is a program which gives you almost full 3021 Internet connectivity if you have a regular dial up shell account on 3022 some Internet connected Unix computer. Read 3023 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP 3024 support will enlarge your kernel by about 4 KB. If unsure, say N. 3025 3026 To compile this driver as a module, choose M here. The module 3027 will be called slip. 3028 3029config SLIP_COMPRESSED 3030 bool "CSLIP compressed headers" 3031 depends on SLIP 3032 select SLHC 3033 ---help--- 3034 This protocol is faster than SLIP because it uses compression on the 3035 TCP/IP headers (not on the data itself), but it has to be supported 3036 on both ends. Ask your access provider if you are not sure and 3037 answer Y, just in case. You will still be able to use plain SLIP. If 3038 you plan to use SLiRP, the SLIP emulator (available from 3039 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which 3040 allows you to use SLIP over a regular dial up shell connection, you 3041 definitely want to say Y here. The NET-3-HOWTO, available from 3042 <http://www.tldp.org/docs.html#howto>, explains how to configure 3043 CSLIP. This won't enlarge your kernel. 3044 3045config SLHC 3046 tristate 3047 help 3048 This option enables Van Jacobsen serial line header compression 3049 routines. 3050 3051config SLIP_SMART 3052 bool "Keepalive and linefill" 3053 depends on SLIP 3054 help 3055 Adds additional capabilities to the SLIP driver to support the 3056 RELCOM line fill and keepalive monitoring. Ideal on poor quality 3057 analogue lines. 3058 3059config SLIP_MODE_SLIP6 3060 bool "Six bit SLIP encapsulation" 3061 depends on SLIP 3062 help 3063 Just occasionally you may need to run IP over hostile serial 3064 networks that don't pass all control characters or are only seven 3065 bit. Saying Y here adds an extra mode you can use with SLIP: 3066 "slip6". In this mode, SLIP will only send normal ASCII symbols over 3067 the serial device. Naturally, this has to be supported at the other 3068 end of the link as well. It's good enough, for example, to run IP 3069 over the async ports of a Camtec JNT Pad. If unsure, say N. 3070 3071config NET_FC 3072 bool "Fibre Channel driver support" 3073 depends on SCSI && PCI 3074 help 3075 Fibre Channel is a high speed serial protocol mainly used to connect 3076 large storage devices to the computer; it is compatible with and 3077 intended to replace SCSI. 3078 3079 If you intend to use Fibre Channel, you need to have a Fibre channel 3080 adaptor card in your computer; say Y here and to the driver for your 3081 adaptor below. You also should have said Y to "SCSI support" and 3082 "SCSI generic support". 3083 3084config NETCONSOLE 3085 tristate "Network console logging support (EXPERIMENTAL)" 3086 depends on EXPERIMENTAL 3087 ---help--- 3088 If you want to log kernel messages over the network, enable this. 3089 See <file:Documentation/networking/netconsole.txt> for details. 3090 3091config NETCONSOLE_DYNAMIC 3092 bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)" 3093 depends on NETCONSOLE && SYSFS && EXPERIMENTAL 3094 select CONFIGFS_FS 3095 help 3096 This option enables the ability to dynamically reconfigure target 3097 parameters (interface, IP addresses, port numbers, MAC addresses) 3098 at runtime through a userspace interface exported using configfs. 3099 See <file:Documentation/networking/netconsole.txt> for details. 3100 3101config NETPOLL 3102 def_bool NETCONSOLE 3103 3104config NETPOLL_TRAP 3105 bool "Netpoll traffic trapping" 3106 default n 3107 depends on NETPOLL 3108 3109config NET_POLL_CONTROLLER 3110 def_bool NETPOLL 3111 3112config VIRTIO_NET 3113 tristate "Virtio network driver (EXPERIMENTAL)" 3114 depends on EXPERIMENTAL && VIRTIO 3115 ---help--- 3116 This is the virtual network driver for lguest. Say Y or M. 3117 3118endif # NETDEVICES 3119