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