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