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