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