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