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