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