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