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