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