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