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