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