Kconfig 81 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145114611471148114911501151115211531154115511561157115811591160116111621163116411651166116711681169117011711172117311741175117611771178117911801181118211831184118511861187118811891190119111921193119411951196119711981199120012011202120312041205120612071208120912101211121212131214121512161217121812191220122112221223122412251226122712281229123012311232123312341235123612371238123912401241124212431244124512461247124812491250125112521253125412551256125712581259126012611262126312641265126612671268126912701271127212731274127512761277127812791280128112821283128412851286128712881289129012911292129312941295129612971298129913001301130213031304130513061307130813091310131113121313131413151316131713181319132013211322132313241325132613271328132913301331133213331334133513361337133813391340134113421343134413451346134713481349135013511352135313541355135613571358135913601361136213631364136513661367136813691370137113721373137413751376137713781379138013811382138313841385138613871388138913901391139213931394139513961397139813991400140114021403140414051406140714081409141014111412141314141415141614171418141914201421142214231424142514261427142814291430143114321433143414351436143714381439144014411442144314441445144614471448144914501451145214531454145514561457145814591460146114621463146414651466146714681469147014711472147314741475147614771478147914801481148214831484148514861487148814891490149114921493149414951496149714981499150015011502150315041505150615071508150915101511151215131514151515161517151815191520152115221523152415251526152715281529153015311532153315341535153615371538153915401541154215431544154515461547154815491550155115521553155415551556155715581559156015611562156315641565156615671568156915701571157215731574157515761577157815791580158115821583158415851586158715881589159015911592159315941595159615971598159916001601160216031604160516061607160816091610161116121613161416151616161716181619162016211622162316241625162616271628162916301631163216331634163516361637163816391640164116421643164416451646164716481649165016511652165316541655165616571658165916601661166216631664166516661667166816691670167116721673167416751676167716781679168016811682168316841685168616871688168916901691169216931694169516961697169816991700170117021703170417051706170717081709171017111712171317141715171617171718171917201721172217231724172517261727172817291730173117321733173417351736173717381739174017411742174317441745174617471748174917501751175217531754175517561757175817591760176117621763176417651766176717681769177017711772177317741775177617771778177917801781178217831784178517861787178817891790179117921793179417951796179717981799180018011802180318041805180618071808180918101811181218131814181518161817181818191820182118221823182418251826182718281829183018311832183318341835183618371838183918401841184218431844184518461847184818491850185118521853185418551856185718581859186018611862186318641865186618671868186918701871187218731874187518761877187818791880188118821883188418851886188718881889189018911892189318941895189618971898189919001901190219031904190519061907190819091910191119121913191419151916191719181919192019211922192319241925192619271928192919301931193219331934193519361937193819391940194119421943194419451946194719481949195019511952195319541955195619571958195919601961196219631964196519661967196819691970197119721973197419751976197719781979198019811982198319841985198619871988198919901991199219931994199519961997199819992000200120022003200420052006200720082009201020112012201320142015201620172018201920202021202220232024202520262027202820292030203120322033203420352036203720382039204020412042204320442045204620472048204920502051205220532054205520562057205820592060206120622063206420652066206720682069207020712072207320742075207620772078207920802081208220832084208520862087208820892090209120922093209420952096209720982099210021012102210321042105210621072108210921102111211221132114211521162117211821192120212121222123212421252126212721282129213021312132213321342135213621372138213921402141214221432144214521462147214821492150215121522153215421552156215721582159216021612162216321642165216621672168216921702171217221732174217521762177217821792180218121822183218421852186218721882189219021912192219321942195219621972198219922002201220222032204220522062207220822092210221122122213221422152216221722182219222022212222222322242225222622272228222922302231223222332234223522362237223822392240224122422243224422452246224722482249225022512252225322542255225622572258225922602261226222632264226522662267226822692270227122722273227422752276227722782279228022812282228322842285228622872288228922902291229222932294229522962297229822992300230123022303230423052306230723082309231023112312231323142315231623172318231923202321232223232324232523262327232823292330233123322333233423352336233723382339234023412342234323442345234623472348234923502351235223532354235523562357235823592360236123622363236423652366236723682369237023712372237323742375237623772378237923802381238223832384238523862387238823892390239123922393239423952396239723982399240024012402240324042405240624072408240924102411241224132414241524162417241824192420242124222423242424252426242724282429243024312432243324342435243624372438243924402441244224432444244524462447244824492450245124522453245424552456245724582459246024612462246324642465246624672468246924702471247224732474247524762477247824792480248124822483248424852486248724882489
  1. #
  2. # Network device configuration
  3. #
  4. config HAVE_NET_MACB
  5. bool
  6. menuconfig NETDEVICES
  7. default y if UML
  8. depends on NET
  9. bool "Network device support"
  10. ---help---
  11. You can say N here if you don't intend to connect your Linux box to
  12. any other computer at all.
  13. 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. See also "The Linux Network Administrator's Guide" by Olaf Kirch and
  19. Terry Dawson. Available at <http://www.tldp.org/guides.html>.
  20. If unsure, say Y.
  21. # All the following symbols are dependent on NETDEVICES - do not repeat
  22. # that for each of the symbols.
  23. if NETDEVICES
  24. config IFB
  25. tristate "Intermediate Functional Block support"
  26. depends on NET_CLS_ACT
  27. ---help---
  28. This is an intermediate driver that allows sharing of
  29. resources.
  30. To compile this driver as a module, choose M here: the module
  31. will be called ifb. If you want to use more than one ifb
  32. device at a time, you need to compile this driver as a module.
  33. Instead of 'ifb', the devices will then be called 'ifb0',
  34. 'ifb1' etc.
  35. Look at the iproute2 documentation directory for usage etc
  36. config DUMMY
  37. tristate "Dummy net driver support"
  38. ---help---
  39. This is essentially a bit-bucket device (i.e. traffic you send to
  40. this device is consigned into oblivion) with a configurable IP
  41. address. It is most commonly used in order to make your currently
  42. inactive SLIP address seem like a real address for local programs.
  43. If you use SLIP or PPP, you might want to say Y here. Since this
  44. thing often comes in handy, the default is Y. It won't enlarge your
  45. kernel either. What a deal. Read about it in the Network
  46. Administrator's Guide, available from
  47. <http://www.tldp.org/docs.html#guide>.
  48. To compile this driver as a module, choose M here: the module
  49. will be called dummy. If you want to use more than one dummy
  50. device at a time, you need to compile this driver as a module.
  51. Instead of 'dummy', the devices will then be called 'dummy0',
  52. 'dummy1' etc.
  53. config BONDING
  54. tristate "Bonding driver support"
  55. depends on INET
  56. depends on IPV6 || IPV6=n
  57. ---help---
  58. Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
  59. Channels together. This is called 'Etherchannel' by Cisco,
  60. 'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
  61. The driver supports multiple bonding modes to allow for both high
  62. performance and high availability operation.
  63. Refer to <file:Documentation/networking/bonding.txt> for more
  64. information.
  65. To compile this driver as a module, choose M here: the module
  66. will be called bonding.
  67. config MACVLAN
  68. tristate "MAC-VLAN support (EXPERIMENTAL)"
  69. depends on EXPERIMENTAL
  70. ---help---
  71. This allows one to create virtual interfaces that map packets to
  72. or from specific MAC addresses to a particular interface.
  73. Macvlan devices can be added using the "ip" command from the
  74. iproute2 package starting with the iproute2-2.6.23 release:
  75. "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
  76. To compile this driver as a module, choose M here: the module
  77. will be called macvlan.
  78. config MACVTAP
  79. tristate "MAC-VLAN based tap driver (EXPERIMENTAL)"
  80. depends on MACVLAN
  81. help
  82. This adds a specialized tap character device driver that is based
  83. on the MAC-VLAN network interface, called macvtap. A macvtap device
  84. can be added in the same way as a macvlan device, using 'type
  85. macvlan', and then be accessed through the tap user space interface.
  86. To compile this driver as a module, choose M here: the module
  87. will be called macvtap.
  88. config EQUALIZER
  89. tristate "EQL (serial line load balancing) support"
  90. ---help---
  91. If you have two serial connections to some other computer (this
  92. usually requires two modems and two telephone lines) and you use
  93. SLIP (the protocol for sending Internet traffic over telephone
  94. lines) or PPP (a better SLIP) on them, you can make them behave like
  95. one double speed connection using this driver. Naturally, this has
  96. to be supported at the other end as well, either with a similar EQL
  97. Linux driver or with a Livingston Portmaster 2e.
  98. Say Y if you want this and read
  99. <file:Documentation/networking/eql.txt>. You may also want to read
  100. section 6.2 of the NET-3-HOWTO, available from
  101. <http://www.tldp.org/docs.html#howto>.
  102. To compile this driver as a module, choose M here: the module
  103. will be called eql. If unsure, say N.
  104. config TUN
  105. tristate "Universal TUN/TAP device driver support"
  106. select CRC32
  107. ---help---
  108. TUN/TAP provides packet reception and transmission for user space
  109. programs. It can be viewed as a simple Point-to-Point or Ethernet
  110. device, which instead of receiving packets from a physical media,
  111. receives them from user space program and instead of sending packets
  112. via physical media writes them to the user space program.
  113. When a program opens /dev/net/tun, driver creates and registers
  114. corresponding net device tunX or tapX. After a program closed above
  115. devices, driver will automatically delete tunXX or tapXX device and
  116. all routes corresponding to it.
  117. Please read <file:Documentation/networking/tuntap.txt> for more
  118. information.
  119. To compile this driver as a module, choose M here: the module
  120. will be called tun.
  121. If you don't know what to use this for, you don't need it.
  122. config VETH
  123. tristate "Virtual ethernet pair device"
  124. ---help---
  125. This device is a local ethernet tunnel. Devices are created in pairs.
  126. When one end receives the packet it appears on its pair and vice
  127. versa.
  128. config NET_SB1000
  129. tristate "General Instruments Surfboard 1000"
  130. depends on PNP
  131. ---help---
  132. This is a driver for the General Instrument (also known as
  133. NextLevel) SURFboard 1000 internal
  134. cable modem. This is an ISA card which is used by a number of cable
  135. TV companies to provide cable modem access. It's a one-way
  136. downstream-only cable modem, meaning that your upstream net link is
  137. provided by your regular phone modem.
  138. At present this driver only compiles as a module, so say M here if
  139. you have this card. The module will be called sb1000. Then read
  140. <file:Documentation/networking/README.sb1000> for information on how
  141. to use this module, as it needs special ppp scripts for establishing
  142. a connection. Further documentation and the necessary scripts can be
  143. found at:
  144. <http://www.jacksonville.net/~fventuri/>
  145. <http://home.adelphia.net/~siglercm/sb1000.html>
  146. <http://linuxpower.cx/~cable/>
  147. If you don't have this card, of course say N.
  148. source "drivers/net/arcnet/Kconfig"
  149. config MII
  150. tristate "Generic Media Independent Interface device support"
  151. help
  152. Most ethernet controllers have MII transceiver either as an external
  153. or internal device. It is safe to say Y or M here even if your
  154. ethernet card lacks MII.
  155. source "drivers/net/phy/Kconfig"
  156. #
  157. # Ethernet
  158. #
  159. source "drivers/net/ethernet/Kconfig"
  160. menuconfig NET_ETHERNET
  161. bool "Ethernet (10 or 100Mbit)"
  162. depends on !UML
  163. ---help---
  164. Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
  165. type of Local Area Network (LAN) in universities and companies.
  166. Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
  167. coaxial cable, linking computers in a chain), 10BASE-T or twisted
  168. pair (10 Mbps over twisted pair cable, linking computers to central
  169. hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
  170. 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
  171. 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
  172. cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
  173. [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
  174. Ethernet (1 Gbps over optical fiber or short copper links).
  175. If your Linux machine will be connected to an Ethernet and you have
  176. an Ethernet network interface card (NIC) installed in your computer,
  177. say Y here and read the Ethernet-HOWTO, available from
  178. <http://www.tldp.org/docs.html#howto>. You will then also have
  179. to say Y to the driver for your particular NIC.
  180. Note that the answer to this question won't directly affect the
  181. kernel: saying N will just cause the configurator to skip all
  182. the questions about Ethernet network cards. If unsure, say N.
  183. if NET_ETHERNET
  184. config MACB
  185. tristate "Atmel MACB support"
  186. depends on HAVE_NET_MACB
  187. select PHYLIB
  188. help
  189. The Atmel MACB ethernet interface is found on many AT32 and AT91
  190. parts. Say Y to include support for the MACB chip.
  191. To compile this driver as a module, choose M here: the module
  192. will be called macb.
  193. source "drivers/net/arm/Kconfig"
  194. config MACE
  195. tristate "MACE (Power Mac ethernet) support"
  196. depends on PPC_PMAC && PPC32
  197. select CRC32
  198. help
  199. Power Macintoshes and clones with Ethernet built-in on the
  200. motherboard will usually use a MACE (Medium Access Control for
  201. Ethernet) interface. Say Y to include support for the MACE chip.
  202. To compile this driver as a module, choose M here: the module
  203. will be called mace.
  204. config MACE_AAUI_PORT
  205. bool "Use AAUI port instead of TP by default"
  206. depends on MACE
  207. help
  208. Some Apple machines (notably the Apple Network Server) which use the
  209. MACE ethernet chip have an Apple AUI port (small 15-pin connector),
  210. instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
  211. Y here if you have such a machine. If unsure, say N.
  212. The driver will default to AAUI on ANS anyway, and if you use it as
  213. a module, you can provide the port_aaui=0|1 to force the driver.
  214. config BMAC
  215. tristate "BMAC (G3 ethernet) support"
  216. depends on PPC_PMAC && PPC32
  217. select CRC32
  218. help
  219. Say Y for support of BMAC Ethernet interfaces. These are used on G3
  220. computers.
  221. To compile this driver as a module, choose M here: the module
  222. will be called bmac.
  223. config MAC89x0
  224. tristate "Macintosh CS89x0 based ethernet cards"
  225. depends on MAC
  226. ---help---
  227. Support for CS89x0 chipset based Ethernet cards. If you have a
  228. Nubus or LC-PDS network (Ethernet) card of this type, say Y and
  229. read the Ethernet-HOWTO, available from
  230. <http://www.tldp.org/docs.html#howto>.
  231. To compile this driver as a module, choose M here. This module will
  232. be called mac89x0.
  233. config MACSONIC
  234. tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
  235. depends on MAC
  236. ---help---
  237. Support for NatSemi SONIC based Ethernet devices. This includes
  238. the onboard Ethernet in many Quadras as well as some LC-PDS,
  239. a few Nubus and all known Comm Slot Ethernet cards. If you have
  240. one of these say Y and read the Ethernet-HOWTO, available from
  241. <http://www.tldp.org/docs.html#howto>.
  242. To compile this driver as a module, choose M here. This module will
  243. be called macsonic.
  244. config MACMACE
  245. bool "Macintosh (AV) onboard MACE ethernet"
  246. depends on MAC
  247. select CRC32
  248. help
  249. Support for the onboard AMD 79C940 MACE Ethernet controller used in
  250. the 660AV and 840AV Macintosh. If you have one of these Macintoshes
  251. say Y and read the Ethernet-HOWTO, available from
  252. <http://www.tldp.org/docs.html#howto>.
  253. config MVME16x_NET
  254. tristate "MVME16x Ethernet support"
  255. depends on MVME16x
  256. help
  257. This is the driver for the Ethernet interface on the Motorola
  258. MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
  259. driver for this chip in your kernel.
  260. To compile this driver as a module, choose M here.
  261. config BVME6000_NET
  262. tristate "BVME6000 Ethernet support"
  263. depends on BVME6000
  264. help
  265. This is the driver for the Ethernet interface on BVME4000 and
  266. BVME6000 VME boards. Say Y here to include the driver for this chip
  267. in your kernel.
  268. To compile this driver as a module, choose M here.
  269. config SUN3_82586
  270. bool "Sun3 on-board Intel 82586 support"
  271. depends on SUN3
  272. help
  273. This driver enables support for the on-board Intel 82586 based
  274. Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
  275. that this driver does not support 82586-based adapters on additional
  276. VME boards.
  277. config LASI_82596
  278. tristate "Lasi ethernet"
  279. depends on GSC
  280. help
  281. Say Y here to support the builtin Intel 82596 ethernet controller
  282. found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
  283. config SNI_82596
  284. tristate "SNI RM ethernet"
  285. depends on NET_ETHERNET && SNI_RM
  286. help
  287. Say Y here to support the on-board Intel 82596 ethernet controller
  288. built into SNI RM machines.
  289. config KORINA
  290. tristate "Korina (IDT RC32434) Ethernet support"
  291. depends on NET_ETHERNET && MIKROTIK_RB532
  292. help
  293. If you have a Mikrotik RouterBoard 500 or IDT RC32434
  294. based system say Y. Otherwise say N.
  295. config MIPS_JAZZ_SONIC
  296. tristate "MIPS JAZZ onboard SONIC Ethernet support"
  297. depends on MACH_JAZZ
  298. help
  299. This is the driver for the onboard card of MIPS Magnum 4000,
  300. Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
  301. config XTENSA_XT2000_SONIC
  302. tristate "Xtensa XT2000 onboard SONIC Ethernet support"
  303. depends on XTENSA_PLATFORM_XT2000
  304. help
  305. This is the driver for the onboard card of the Xtensa XT2000 board.
  306. config SGI_IOC3_ETH
  307. bool "SGI IOC3 Ethernet"
  308. depends on PCI && SGI_IP27
  309. select CRC32
  310. select MII
  311. help
  312. If you have a network (Ethernet) card of this type, say Y and read
  313. the Ethernet-HOWTO, available from
  314. <http://www.tldp.org/docs.html#howto>.
  315. config MIPS_SIM_NET
  316. tristate "MIPS simulator Network device"
  317. depends on MIPS_SIM
  318. help
  319. The MIPSNET device is a simple Ethernet network device which is
  320. emulated by the MIPS Simulator.
  321. If you are not using a MIPSsim or are unsure, say N.
  322. config SGI_O2MACE_ETH
  323. tristate "SGI O2 MACE Fast Ethernet support"
  324. depends on SGI_IP32=y
  325. config SH_ETH
  326. tristate "Renesas SuperH Ethernet support"
  327. depends on SUPERH && \
  328. (CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712 || \
  329. CPU_SUBTYPE_SH7763 || CPU_SUBTYPE_SH7619 || \
  330. CPU_SUBTYPE_SH7724 || CPU_SUBTYPE_SH7757)
  331. select CRC32
  332. select MII
  333. select MDIO_BITBANG
  334. select PHYLIB
  335. help
  336. Renesas SuperH Ethernet device driver.
  337. This driver supporting CPUs are:
  338. - SH7710, SH7712, SH7763, SH7619, SH7724, and SH7757.
  339. config HAPPYMEAL
  340. tristate "Sun Happy Meal 10/100baseT support"
  341. depends on SBUS || PCI
  342. select CRC32
  343. help
  344. This driver supports the "hme" interface present on most Ultra
  345. systems and as an option on older Sbus systems. This driver supports
  346. both PCI and Sbus devices. This driver also supports the "qfe" quad
  347. 100baseT device available in both PCI and Sbus configurations.
  348. To compile this driver as a module, choose M here: the module
  349. will be called sunhme.
  350. config SUNBMAC
  351. tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
  352. depends on SBUS && EXPERIMENTAL
  353. select CRC32
  354. help
  355. This driver supports the "be" interface available as an Sbus option.
  356. This is Sun's older 100baseT Ethernet device.
  357. To compile this driver as a module, choose M here: the module
  358. will be called sunbmac.
  359. config SUNQE
  360. tristate "Sun QuadEthernet support"
  361. depends on SBUS
  362. select CRC32
  363. help
  364. This driver supports the "qe" 10baseT Ethernet device, available as
  365. an Sbus option. Note that this is not the same as Quad FastEthernet
  366. "qfe" which is supported by the Happy Meal driver instead.
  367. To compile this driver as a module, choose M here: the module
  368. will be called sunqe.
  369. config SUNGEM
  370. tristate "Sun GEM support"
  371. depends on PCI
  372. select CRC32
  373. help
  374. Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
  375. <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
  376. config CASSINI
  377. tristate "Sun Cassini support"
  378. depends on PCI
  379. select CRC32
  380. help
  381. Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
  382. <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
  383. config SUNVNET
  384. tristate "Sun Virtual Network support"
  385. depends on SUN_LDOMS
  386. help
  387. Support for virtual network devices under Sun Logical Domains.
  388. config EL2
  389. tristate "3c503 \"EtherLink II\" support"
  390. depends on ISA
  391. select CRC32
  392. ---help---
  393. If you have a network (Ethernet) card of this type, say Y and read
  394. the Ethernet-HOWTO, available from
  395. <http://www.tldp.org/docs.html#howto>.
  396. To compile this driver as a module, choose M here. The module
  397. will be called 3c503.
  398. config ELPLUS
  399. tristate "3c505 \"EtherLink Plus\" support"
  400. depends on ISA && ISA_DMA_API
  401. ---help---
  402. Information about this network (Ethernet) card can be found in
  403. <file:Documentation/networking/3c505.txt>. If you have a card of
  404. this type, say Y and read the Ethernet-HOWTO, available from
  405. <http://www.tldp.org/docs.html#howto>.
  406. To compile this driver as a module, choose M here. The module
  407. will be called 3c505.
  408. config EL16
  409. tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
  410. depends on ISA && EXPERIMENTAL
  411. ---help---
  412. If you have a network (Ethernet) card of this type, say Y and read
  413. the Ethernet-HOWTO, available from
  414. <http://www.tldp.org/docs.html#howto>.
  415. To compile this driver as a module, choose M here. The module
  416. will be called 3c507.
  417. config ELMC
  418. tristate "3c523 \"EtherLink/MC\" support"
  419. depends on MCA_LEGACY
  420. ---help---
  421. If you have a network (Ethernet) card of this type, say Y and read
  422. the Ethernet-HOWTO, available from
  423. <http://www.tldp.org/docs.html#howto>.
  424. To compile this driver as a module, choose M here. The module
  425. will be called 3c523.
  426. config ELMC_II
  427. tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
  428. depends on MCA && MCA_LEGACY
  429. ---help---
  430. If you have a network (Ethernet) card of this type, say Y and read
  431. the Ethernet-HOWTO, available from
  432. <http://www.tldp.org/docs.html#howto>.
  433. To compile this driver as a module, choose M here. The module
  434. will be called 3c527.
  435. config BFIN_MAC
  436. tristate "Blackfin on-chip MAC support"
  437. depends on NET_ETHERNET && (BF516 || BF518 || BF526 || BF527 || BF536 || BF537)
  438. select CRC32
  439. select MII
  440. select PHYLIB
  441. select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
  442. help
  443. This is the driver for Blackfin on-chip mac device. Say Y if you want it
  444. compiled into the kernel. This driver is also available as a module
  445. ( = code which can be inserted in and removed from the running kernel
  446. whenever you want). The module will be called bfin_mac.
  447. config BFIN_MAC_USE_L1
  448. bool "Use L1 memory for rx/tx packets"
  449. depends on BFIN_MAC && (BF527 || BF537)
  450. default y
  451. help
  452. To get maximum network performance, you should use L1 memory as rx/tx buffers.
  453. Say N here if you want to reserve L1 memory for other uses.
  454. config BFIN_TX_DESC_NUM
  455. int "Number of transmit buffer packets"
  456. depends on BFIN_MAC
  457. range 6 10 if BFIN_MAC_USE_L1
  458. range 10 100
  459. default "10"
  460. help
  461. Set the number of buffer packets used in driver.
  462. config BFIN_RX_DESC_NUM
  463. int "Number of receive buffer packets"
  464. depends on BFIN_MAC
  465. range 20 100 if BFIN_MAC_USE_L1
  466. range 20 800
  467. default "20"
  468. help
  469. Set the number of buffer packets used in driver.
  470. config BFIN_MAC_USE_HWSTAMP
  471. bool "Use IEEE 1588 hwstamp"
  472. depends on BFIN_MAC && BF518
  473. default y
  474. help
  475. To support the IEEE 1588 Precision Time Protocol (PTP), select y here
  476. config SMC9194
  477. tristate "SMC 9194 support"
  478. depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
  479. select CRC32
  480. ---help---
  481. This is support for the SMC9xxx based Ethernet cards. Choose this
  482. option if you have a DELL laptop with the docking station, or
  483. another SMC9192/9194 based chipset. Say Y if you want it compiled
  484. into the kernel, and read the file
  485. <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
  486. available from <http://www.tldp.org/docs.html#howto>.
  487. To compile this driver as a module, choose M here. The module
  488. will be called smc9194.
  489. config SMC91X
  490. tristate "SMC 91C9x/91C1xxx support"
  491. select CRC32
  492. select MII
  493. depends on ARM || M32R || SUPERH || \
  494. MIPS || BLACKFIN || MN10300 || COLDFIRE
  495. help
  496. This is a driver for SMC's 91x series of Ethernet chipsets,
  497. including the SMC91C94 and the SMC91C111. Say Y if you want it
  498. compiled into the kernel, and read the file
  499. <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
  500. available from <http://www.tldp.org/docs.html#howto>.
  501. This driver is also available as a module ( = code which can be
  502. inserted in and removed from the running kernel whenever you want).
  503. The module will be called smc91x. If you want to compile it as a
  504. module, say M here and read <file:Documentation/kbuild/modules.txt>.
  505. config PXA168_ETH
  506. tristate "Marvell pxa168 ethernet support"
  507. depends on CPU_PXA168
  508. select PHYLIB
  509. help
  510. This driver supports the pxa168 Ethernet ports.
  511. To compile this driver as a module, choose M here. The module
  512. will be called pxa168_eth.
  513. config NET_NETX
  514. tristate "NetX Ethernet support"
  515. select MII
  516. depends on ARCH_NETX
  517. help
  518. This is support for the Hilscher netX builtin Ethernet ports
  519. To compile this driver as a module, choose M here. The module
  520. will be called netx-eth.
  521. config TI_DAVINCI_EMAC
  522. tristate "TI DaVinci EMAC Support"
  523. depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
  524. select TI_DAVINCI_MDIO
  525. select TI_DAVINCI_CPDMA
  526. select PHYLIB
  527. help
  528. This driver supports TI's DaVinci Ethernet .
  529. To compile this driver as a module, choose M here: the module
  530. will be called davinci_emac_driver. This is recommended.
  531. config TI_DAVINCI_MDIO
  532. tristate "TI DaVinci MDIO Support"
  533. depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
  534. select PHYLIB
  535. help
  536. This driver supports TI's DaVinci MDIO module.
  537. To compile this driver as a module, choose M here: the module
  538. will be called davinci_mdio. This is recommended.
  539. config TI_DAVINCI_CPDMA
  540. tristate "TI DaVinci CPDMA Support"
  541. depends on ARM && ( ARCH_DAVINCI || ARCH_OMAP3 )
  542. help
  543. This driver supports TI's DaVinci CPDMA dma engine.
  544. To compile this driver as a module, choose M here: the module
  545. will be called davinci_cpdma. This is recommended.
  546. config DM9000
  547. tristate "DM9000 support"
  548. depends on ARM || BLACKFIN || MIPS
  549. select CRC32
  550. select MII
  551. ---help---
  552. Support for DM9000 chipset.
  553. To compile this driver as a module, choose M here. The module
  554. will be called dm9000.
  555. config DM9000_DEBUGLEVEL
  556. int "DM9000 maximum debug level"
  557. depends on DM9000
  558. default 4
  559. help
  560. The maximum level of debugging code compiled into the DM9000
  561. driver.
  562. config DM9000_FORCE_SIMPLE_PHY_POLL
  563. bool "Force simple NSR based PHY polling"
  564. depends on DM9000
  565. ---help---
  566. This configuration forces the DM9000 to use the NSR's LinkStatus
  567. bit to determine if the link is up or down instead of the more
  568. costly MII PHY reads. Note, this will not work if the chip is
  569. operating with an external PHY.
  570. config ENC28J60
  571. tristate "ENC28J60 support"
  572. depends on EXPERIMENTAL && SPI && NET_ETHERNET
  573. select CRC32
  574. ---help---
  575. Support for the Microchip EN28J60 ethernet chip.
  576. To compile this driver as a module, choose M here. The module will be
  577. called enc28j60.
  578. config ENC28J60_WRITEVERIFY
  579. bool "Enable write verify"
  580. depends on ENC28J60
  581. ---help---
  582. Enable the verify after the buffer write useful for debugging purpose.
  583. If unsure, say N.
  584. config ETHOC
  585. tristate "OpenCores 10/100 Mbps Ethernet MAC support"
  586. depends on NET_ETHERNET && HAS_IOMEM && HAS_DMA
  587. select MII
  588. select PHYLIB
  589. select CRC32
  590. select BITREVERSE
  591. help
  592. Say Y here if you want to use the OpenCores 10/100 Mbps Ethernet MAC.
  593. config GRETH
  594. tristate "Aeroflex Gaisler GRETH Ethernet MAC support"
  595. depends on SPARC
  596. select PHYLIB
  597. select CRC32
  598. help
  599. Say Y here if you want to use the Aeroflex Gaisler GRETH Ethernet MAC.
  600. config SMC911X
  601. tristate "SMSC LAN911[5678] support"
  602. select CRC32
  603. select MII
  604. depends on ARM || SUPERH || MN10300
  605. help
  606. This is a driver for SMSC's LAN911x series of Ethernet chipsets
  607. including the new LAN9115, LAN9116, LAN9117, and LAN9118.
  608. Say Y if you want it compiled into the kernel,
  609. and read the Ethernet-HOWTO, available from
  610. <http://www.tldp.org/docs.html#howto>.
  611. This driver is also available as a module. The module will be
  612. called smc911x. If you want to compile it as a module, say M
  613. here and read <file:Documentation/kbuild/modules.txt>
  614. config SMSC911X
  615. tristate "SMSC LAN911x/LAN921x families embedded ethernet support"
  616. depends on ARM || SUPERH || BLACKFIN || MIPS || MN10300
  617. select CRC32
  618. select MII
  619. select PHYLIB
  620. ---help---
  621. Say Y here if you want support for SMSC LAN911x and LAN921x families
  622. of ethernet controllers.
  623. To compile this driver as a module, choose M here and read
  624. <file:Documentation/networking/net-modules.txt>. The module
  625. will be called smsc911x.
  626. config SMSC911X_ARCH_HOOKS
  627. def_bool n
  628. depends on SMSC911X
  629. help
  630. If the arch enables this, it allows the arch to implement various
  631. hooks for more comprehensive interrupt control and also to override
  632. the source of the MAC address.
  633. config NET_VENDOR_RACAL
  634. bool "Racal-Interlan (Micom) NI cards"
  635. depends on ISA
  636. help
  637. If you have a network (Ethernet) card belonging to this class, such
  638. as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
  639. available from <http://www.tldp.org/docs.html#howto>.
  640. Note that the answer to this question doesn't directly affect the
  641. kernel: saying N will just cause the configurator to skip all
  642. the questions about NI cards. If you say Y, you will be asked for
  643. your specific card in the following questions.
  644. config NI5010
  645. tristate "NI5010 support (EXPERIMENTAL)"
  646. depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
  647. ---help---
  648. If you have a network (Ethernet) card of this type, say Y and read
  649. the Ethernet-HOWTO, available from
  650. <http://www.tldp.org/docs.html#howto>. Note that this is still
  651. experimental code.
  652. To compile this driver as a module, choose M here. The module
  653. will be called ni5010.
  654. config NI52
  655. tristate "NI5210 support"
  656. depends on NET_VENDOR_RACAL && ISA
  657. help
  658. If you have a network (Ethernet) card of this type, say Y and read
  659. the Ethernet-HOWTO, available from
  660. <http://www.tldp.org/docs.html#howto>.
  661. To compile this driver as a module, choose M here. The module
  662. will be called ni52.
  663. config DNET
  664. tristate "Dave ethernet support (DNET)"
  665. depends on NET_ETHERNET && HAS_IOMEM
  666. select PHYLIB
  667. help
  668. The Dave ethernet interface (DNET) is found on Qong Board FPGA.
  669. Say Y to include support for the DNET chip.
  670. To compile this driver as a module, choose M here: the module
  671. will be called dnet.
  672. source "drivers/net/tulip/Kconfig"
  673. config AT1700
  674. tristate "AT1700/1720 support (EXPERIMENTAL)"
  675. depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
  676. select CRC32
  677. ---help---
  678. If you have a network (Ethernet) card of this type, say Y and read
  679. the Ethernet-HOWTO, available from
  680. <http://www.tldp.org/docs.html#howto>.
  681. To compile this driver as a module, choose M here. The module
  682. will be called at1700.
  683. config HP100
  684. tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
  685. depends on ISA || EISA || PCI
  686. help
  687. If you have a network (Ethernet) card of this type, say Y and read
  688. the Ethernet-HOWTO, available from
  689. <http://www.tldp.org/docs.html#howto>.
  690. To compile this driver as a module, choose M here. The module
  691. will be called hp100.
  692. config NET_ISA
  693. bool "Other ISA cards"
  694. depends on ISA
  695. ---help---
  696. If your network (Ethernet) card hasn't been mentioned yet and its
  697. bus system (that's the way the cards talks to the other components
  698. of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
  699. Make sure you know the name of your card. Read the Ethernet-HOWTO,
  700. available from <http://www.tldp.org/docs.html#howto>.
  701. If unsure, say Y.
  702. Note that the answer to this question doesn't directly affect the
  703. kernel: saying N will just cause the configurator to skip all
  704. the remaining ISA network card questions. If you say Y, you will be
  705. asked for your specific card in the following questions.
  706. config EWRK3
  707. tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
  708. depends on NET_ISA
  709. select CRC32
  710. ---help---
  711. This driver supports the DE203, DE204 and DE205 network (Ethernet)
  712. cards. If this is for you, say Y and read
  713. <file:Documentation/networking/ewrk3.txt> in the kernel source as
  714. well as the Ethernet-HOWTO, available from
  715. <http://www.tldp.org/docs.html#howto>.
  716. To compile this driver as a module, choose M here. The module
  717. will be called ewrk3.
  718. config EEXPRESS
  719. tristate "EtherExpress 16 support"
  720. depends on NET_ISA
  721. ---help---
  722. If you have an EtherExpress16 network (Ethernet) card, say Y and
  723. read the Ethernet-HOWTO, available from
  724. <http://www.tldp.org/docs.html#howto>. Note that the Intel
  725. EtherExpress16 card used to be regarded as a very poor choice
  726. because the driver was very unreliable. We now have a new driver
  727. that should do better.
  728. To compile this driver as a module, choose M here. The module
  729. will be called eexpress.
  730. config EEXPRESS_PRO
  731. tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
  732. depends on NET_ISA
  733. ---help---
  734. If you have a network (Ethernet) card of this type, say Y. This
  735. driver supports Intel i82595{FX,TX} based boards. Note however
  736. that the EtherExpress PRO/100 Ethernet card has its own separate
  737. driver. Please read the Ethernet-HOWTO, available from
  738. <http://www.tldp.org/docs.html#howto>.
  739. To compile this driver as a module, choose M here. The module
  740. will be called eepro.
  741. config LP486E
  742. tristate "LP486E on board Ethernet"
  743. depends on NET_ISA
  744. help
  745. Say Y here to support the 82596-based on-board Ethernet controller
  746. for the Panther motherboard, which is one of the two shipped in the
  747. Intel Professional Workstation.
  748. config ETH16I
  749. tristate "ICL EtherTeam 16i/32 support"
  750. depends on NET_ISA
  751. help
  752. If you have a network (Ethernet) card of this type, say Y and read
  753. the Ethernet-HOWTO, available from
  754. <http://www.tldp.org/docs.html#howto>.
  755. To compile this driver as a module, choose M here. The module
  756. will be called eth16i.
  757. config ZNET
  758. tristate "Zenith Z-Note support (EXPERIMENTAL)"
  759. depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
  760. help
  761. The Zenith Z-Note notebook computer has a built-in network
  762. (Ethernet) card, and this is the Linux driver for it. Note that the
  763. IBM Thinkpad 300 is compatible with the Z-Note and is also supported
  764. by this driver. Read the Ethernet-HOWTO, available from
  765. <http://www.tldp.org/docs.html#howto>.
  766. config SEEQ8005
  767. tristate "SEEQ8005 support (EXPERIMENTAL)"
  768. depends on NET_ISA && EXPERIMENTAL
  769. help
  770. This is a driver for the SEEQ 8005 network (Ethernet) card. If this
  771. is for you, read the Ethernet-HOWTO, available from
  772. <http://www.tldp.org/docs.html#howto>.
  773. To compile this driver as a module, choose M here. The module
  774. will be called seeq8005.
  775. config IBMLANA
  776. tristate "IBM LAN Adapter/A support"
  777. depends on MCA
  778. ---help---
  779. This is a Micro Channel Ethernet adapter. You need to set
  780. CONFIG_MCA to use this driver. It is both available as an in-kernel
  781. driver and as a module.
  782. To compile this driver as a module, choose M here. The only
  783. currently supported card is the IBM LAN Adapter/A for Ethernet. It
  784. will both support 16K and 32K memory windows, however a 32K window
  785. gives a better security against packet losses. Usage of multiple
  786. boards with this driver should be possible, but has not been tested
  787. up to now due to lack of hardware.
  788. config IBMVETH
  789. tristate "IBM LAN Virtual Ethernet support"
  790. depends on PPC_PSERIES
  791. ---help---
  792. This driver supports virtual ethernet adapters on newer IBM iSeries
  793. and pSeries systems.
  794. To compile this driver as a module, choose M here. The module will
  795. be called ibmveth.
  796. source "drivers/net/ibm_newemac/Kconfig"
  797. config NET_PCI
  798. bool "EISA, VLB, PCI and on board controllers"
  799. depends on ISA || EISA || PCI
  800. help
  801. This is another class of network cards which attach directly to the
  802. bus. If you have one of those, say Y and read the Ethernet-HOWTO,
  803. available from <http://www.tldp.org/docs.html#howto>.
  804. Note that the answer to this question doesn't directly affect the
  805. kernel: saying N will just cause the configurator to skip all
  806. the questions about this class of network cards. If you say Y, you
  807. will be asked for your specific card in the following questions. If
  808. you are unsure, say Y.
  809. config ADAPTEC_STARFIRE
  810. tristate "Adaptec Starfire/DuraLAN support"
  811. depends on NET_PCI && PCI
  812. select CRC32
  813. select MII
  814. help
  815. Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
  816. adapter. The DuraLAN chip is used on the 64 bit PCI boards from
  817. Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
  818. driver.
  819. To compile this driver as a module, choose M here: the module
  820. will be called starfire. This is recommended.
  821. config KSZ884X_PCI
  822. tristate "Micrel KSZ8841/2 PCI"
  823. depends on NET_PCI && PCI
  824. select MII
  825. select CRC32
  826. help
  827. This PCI driver is for Micrel KSZ8841/KSZ8842 PCI Ethernet chip.
  828. To compile this driver as a module, choose M here. The module
  829. will be called ksz884x.
  830. config APRICOT
  831. tristate "Apricot Xen-II on board Ethernet"
  832. depends on NET_PCI && ISA
  833. help
  834. If you have a network (Ethernet) controller of this type, say Y and
  835. read the Ethernet-HOWTO, available from
  836. <http://www.tldp.org/docs.html#howto>.
  837. To compile this driver as a module, choose M here. The module
  838. will be called apricot.
  839. config FORCEDETH
  840. tristate "nForce Ethernet support"
  841. depends on NET_PCI && PCI
  842. help
  843. If you have a network (Ethernet) controller of this type, say Y and
  844. read the Ethernet-HOWTO, available from
  845. <http://www.tldp.org/docs.html#howto>.
  846. To compile this driver as a module, choose M here. The module
  847. will be called forcedeth.
  848. config CS89x0
  849. tristate "CS89x0 support"
  850. depends on NET_ETHERNET && (ISA || EISA || MACH_IXDP2351 \
  851. || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440)
  852. ---help---
  853. Support for CS89x0 chipset based Ethernet cards. If you have a
  854. network (Ethernet) card of this type, say Y and read the
  855. Ethernet-HOWTO, available from
  856. <http://www.tldp.org/docs.html#howto> as well as
  857. <file:Documentation/networking/cs89x0.txt>.
  858. To compile this driver as a module, choose M here. The module
  859. will be called cs89x0.
  860. config CS89x0_NONISA_IRQ
  861. def_bool y
  862. depends on CS89x0 != n
  863. depends on MACH_IXDP2351 || ARCH_IXDP2X01 || MACH_MX31ADS || MACH_QQ2440
  864. config TC35815
  865. tristate "TOSHIBA TC35815 Ethernet support"
  866. depends on NET_PCI && PCI && MIPS
  867. select PHYLIB
  868. config FEALNX
  869. tristate "Myson MTD-8xx PCI Ethernet support"
  870. depends on NET_PCI && PCI
  871. select CRC32
  872. select MII
  873. help
  874. Say Y here to support the Myson MTD-800 family of PCI-based Ethernet
  875. cards. <http://www.myson.com.tw/>
  876. config NATSEMI
  877. tristate "National Semiconductor DP8381x series PCI Ethernet support"
  878. depends on NET_PCI && PCI
  879. select CRC32
  880. help
  881. This driver is for the National Semiconductor DP83810 series,
  882. which is used in cards from PureData, NetGear, Linksys
  883. and others, including the 83815 chip.
  884. More specific information and updates are available from
  885. <http://www.scyld.com/network/natsemi.html>.
  886. config 8139CP
  887. tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
  888. depends on NET_PCI && PCI && EXPERIMENTAL
  889. select CRC32
  890. select MII
  891. help
  892. This is a driver for the Fast Ethernet PCI network cards based on
  893. the RTL8139C+ chips. If you have one of those, say Y and read
  894. the Ethernet-HOWTO, available from
  895. <http://www.tldp.org/docs.html#howto>.
  896. To compile this driver as a module, choose M here: the module
  897. will be called 8139cp. This is recommended.
  898. config 8139TOO
  899. tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
  900. depends on NET_PCI && PCI
  901. select CRC32
  902. select MII
  903. ---help---
  904. This is a driver for the Fast Ethernet PCI network cards based on
  905. the RTL 8129/8130/8139 chips. If you have one of those, say Y and
  906. read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
  907. To compile this driver as a module, choose M here: the module
  908. will be called 8139too. This is recommended.
  909. config 8139TOO_PIO
  910. bool "Use PIO instead of MMIO"
  911. default y
  912. depends on 8139TOO
  913. help
  914. This instructs the driver to use programmed I/O ports (PIO) instead
  915. of PCI shared memory (MMIO). This can possibly solve some problems
  916. in case your mainboard has memory consistency issues. If unsure,
  917. say N.
  918. config 8139TOO_TUNE_TWISTER
  919. bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
  920. depends on 8139TOO
  921. help
  922. This implements a function which might come in handy in case you
  923. are using low quality on long cabling. It is required for RealTek
  924. RTL-8139 revision K boards, and totally unused otherwise. It tries
  925. to match the transceiver to the cable characteristics. This is
  926. experimental since hardly documented by the manufacturer.
  927. If unsure, say Y.
  928. config 8139TOO_8129
  929. bool "Support for older RTL-8129/8130 boards"
  930. depends on 8139TOO
  931. help
  932. This enables support for the older and uncommon RTL-8129 and
  933. RTL-8130 chips, which support MII via an external transceiver,
  934. instead of an internal one. Disabling this option will save some
  935. memory by making the code size smaller. If unsure, say Y.
  936. config 8139_OLD_RX_RESET
  937. bool "Use older RX-reset method"
  938. depends on 8139TOO
  939. help
  940. The 8139too driver was recently updated to contain a more rapid
  941. reset sequence, in the face of severe receive errors. This "new"
  942. RX-reset method should be adequate for all boards. But if you
  943. experience problems, you can enable this option to restore the
  944. old RX-reset behavior. If unsure, say N.
  945. config R6040
  946. tristate "RDC R6040 Fast Ethernet Adapter support"
  947. depends on NET_PCI && PCI
  948. select CRC32
  949. select MII
  950. select PHYLIB
  951. help
  952. This is a driver for the R6040 Fast Ethernet MACs found in the
  953. the RDC R-321x System-on-chips.
  954. To compile this driver as a module, choose M here: the module
  955. will be called r6040. This is recommended.
  956. config SIS900
  957. tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
  958. depends on NET_PCI && PCI
  959. select CRC32
  960. select MII
  961. ---help---
  962. This is a driver for the Fast Ethernet PCI network cards based on
  963. the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
  964. SiS 630 and SiS 540 chipsets.
  965. This driver also supports AMD 79C901 HomePNA so that you can use
  966. your phone line as a network cable.
  967. To compile this driver as a module, choose M here: the module
  968. will be called sis900. This is recommended.
  969. config EPIC100
  970. tristate "SMC EtherPower II"
  971. depends on NET_PCI && PCI
  972. select CRC32
  973. select MII
  974. help
  975. This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
  976. which is based on the SMC83c17x (EPIC/100).
  977. More specific information and updates are available from
  978. <http://www.scyld.com/network/epic100.html>.
  979. config SMSC9420
  980. tristate "SMSC LAN9420 PCI ethernet adapter support"
  981. depends on NET_PCI && PCI
  982. select CRC32
  983. select PHYLIB
  984. select SMSC_PHY
  985. help
  986. This is a driver for SMSC's LAN9420 PCI ethernet adapter.
  987. Say Y if you want it compiled into the kernel,
  988. and read the Ethernet-HOWTO, available from
  989. <http://www.tldp.org/docs.html#howto>.
  990. This driver is also available as a module. The module will be
  991. called smsc9420. If you want to compile it as a module, say M
  992. here and read <file:Documentation/kbuild/modules.txt>
  993. config SUNDANCE
  994. tristate "Sundance Alta support"
  995. depends on NET_PCI && PCI
  996. select CRC32
  997. select MII
  998. help
  999. This driver is for the Sundance "Alta" chip.
  1000. More specific information and updates are available from
  1001. <http://www.scyld.com/network/sundance.html>.
  1002. config SUNDANCE_MMIO
  1003. bool "Use MMIO instead of PIO"
  1004. depends on SUNDANCE
  1005. help
  1006. Enable memory-mapped I/O for interaction with Sundance NIC registers.
  1007. Do NOT enable this by default, PIO (enabled when MMIO is disabled)
  1008. is known to solve bugs on certain chips.
  1009. If unsure, say N.
  1010. config TLAN
  1011. tristate "TI ThunderLAN support"
  1012. depends on NET_PCI && (PCI || EISA)
  1013. ---help---
  1014. If you have a PCI Ethernet network card based on the ThunderLAN chip
  1015. which is supported by this driver, say Y and read the
  1016. Ethernet-HOWTO, available from
  1017. <http://www.tldp.org/docs.html#howto>.
  1018. Devices currently supported by this driver are Compaq Netelligent,
  1019. Compaq NetFlex and Olicom cards. Please read the file
  1020. <file:Documentation/networking/tlan.txt> for more details.
  1021. To compile this driver as a module, choose M here. The module
  1022. will be called tlan.
  1023. Please email feedback to <torben.mathiasen@compaq.com>.
  1024. config KS8842
  1025. tristate "Micrel KSZ8841/42 with generic bus interface"
  1026. depends on HAS_IOMEM && DMA_ENGINE
  1027. help
  1028. This platform driver is for KSZ8841(1-port) / KS8842(2-port)
  1029. ethernet switch chip (managed, VLAN, QoS) from Micrel or
  1030. Timberdale(FPGA).
  1031. config KS8851
  1032. tristate "Micrel KS8851 SPI"
  1033. depends on SPI
  1034. select MII
  1035. select CRC32
  1036. help
  1037. SPI driver for Micrel KS8851 SPI attached network chip.
  1038. config KS8851_MLL
  1039. tristate "Micrel KS8851 MLL"
  1040. depends on HAS_IOMEM
  1041. select MII
  1042. help
  1043. This platform driver is for Micrel KS8851 Address/data bus
  1044. multiplexed network chip.
  1045. config VIA_RHINE
  1046. tristate "VIA Rhine support"
  1047. depends on NET_PCI && PCI
  1048. select CRC32
  1049. select MII
  1050. help
  1051. If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
  1052. Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
  1053. Ethernet functions can also be found integrated on South Bridges
  1054. (e.g. VT8235).
  1055. To compile this driver as a module, choose M here. The module
  1056. will be called via-rhine.
  1057. config VIA_RHINE_MMIO
  1058. bool "Use MMIO instead of PIO"
  1059. depends on VIA_RHINE
  1060. help
  1061. This instructs the driver to use PCI shared memory (MMIO) instead of
  1062. programmed I/O ports (PIO). Enabling this gives an improvement in
  1063. processing time in parts of the driver.
  1064. If unsure, say Y.
  1065. config SC92031
  1066. tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
  1067. depends on NET_PCI && PCI && EXPERIMENTAL
  1068. select CRC32
  1069. ---help---
  1070. This is a driver for the Fast Ethernet PCI network cards based on
  1071. the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
  1072. have one of these, say Y here.
  1073. To compile this driver as a module, choose M here: the module
  1074. will be called sc92031. This is recommended.
  1075. config CPMAC
  1076. tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
  1077. depends on NET_ETHERNET && EXPERIMENTAL && AR7
  1078. select PHYLIB
  1079. help
  1080. TI AR7 CPMAC Ethernet support
  1081. config NET_POCKET
  1082. bool "Pocket and portable adapters"
  1083. depends on PARPORT
  1084. ---help---
  1085. Cute little network (Ethernet) devices which attach to the parallel
  1086. port ("pocket adapters"), commonly used with laptops. If you have
  1087. one of those, say Y and read the Ethernet-HOWTO, available from
  1088. <http://www.tldp.org/docs.html#howto>.
  1089. If you want to plug a network (or some other) card into the PCMCIA
  1090. (or PC-card) slot of your laptop instead (PCMCIA is the standard for
  1091. credit card size extension cards used by all modern laptops), you
  1092. need the pcmcia-cs package (location contained in the file
  1093. <file:Documentation/Changes>) and you can say N here.
  1094. Laptop users should read the Linux Laptop home page at
  1095. <http://www.linux-on-laptops.com/> or
  1096. Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
  1097. Note that the answer to this question doesn't directly affect the
  1098. kernel: saying N will just cause the configurator to skip all
  1099. the questions about this class of network devices. If you say Y, you
  1100. will be asked for your specific device in the following questions.
  1101. config ATP
  1102. tristate "AT-LAN-TEC/RealTek pocket adapter support"
  1103. depends on NET_POCKET && PARPORT && X86
  1104. select CRC32
  1105. ---help---
  1106. This is a network (Ethernet) device which attaches to your parallel
  1107. port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
  1108. available from <http://www.tldp.org/docs.html#howto>, if you
  1109. want to use this. If you intend to use this driver, you should have
  1110. said N to the "Parallel printer support", because the two drivers
  1111. don't like each other.
  1112. To compile this driver as a module, choose M here: the module
  1113. will be called atp.
  1114. config DE600
  1115. tristate "D-Link DE600 pocket adapter support"
  1116. depends on NET_POCKET && PARPORT
  1117. ---help---
  1118. This is a network (Ethernet) device which attaches to your parallel
  1119. port. Read <file:Documentation/networking/DLINK.txt> as well as the
  1120. Ethernet-HOWTO, available from
  1121. <http://www.tldp.org/docs.html#howto>, if you want to use
  1122. this. It is possible to have several devices share a single parallel
  1123. port and it is safe to compile the corresponding drivers into the
  1124. kernel.
  1125. To compile this driver as a module, choose M here: the module
  1126. will be called de600.
  1127. config DE620
  1128. tristate "D-Link DE620 pocket adapter support"
  1129. depends on NET_POCKET && PARPORT
  1130. ---help---
  1131. This is a network (Ethernet) device which attaches to your parallel
  1132. port. Read <file:Documentation/networking/DLINK.txt> as well as the
  1133. Ethernet-HOWTO, available from
  1134. <http://www.tldp.org/docs.html#howto>, if you want to use
  1135. this. It is possible to have several devices share a single parallel
  1136. port and it is safe to compile the corresponding drivers into the
  1137. kernel.
  1138. To compile this driver as a module, choose M here: the module
  1139. will be called de620.
  1140. config SGISEEQ
  1141. tristate "SGI Seeq ethernet controller support"
  1142. depends on SGI_HAS_SEEQ
  1143. help
  1144. Say Y here if you have an Seeq based Ethernet network card. This is
  1145. used in many Silicon Graphics machines.
  1146. config FEC
  1147. bool "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
  1148. depends on M523x || M527x || M5272 || M528x || M520x || M532x || \
  1149. IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC
  1150. default IMX_HAVE_PLATFORM_FEC || MXS_HAVE_PLATFORM_FEC if ARM
  1151. select PHYLIB
  1152. help
  1153. Say Y here if you want to use the built-in 10/100 Fast ethernet
  1154. controller on some Motorola ColdFire and Freescale i.MX processors.
  1155. config FEC_MPC52xx
  1156. tristate "MPC52xx FEC driver"
  1157. depends on PPC_MPC52xx && PPC_BESTCOMM
  1158. select CRC32
  1159. select PHYLIB
  1160. select PPC_BESTCOMM_FEC
  1161. ---help---
  1162. This option enables support for the MPC5200's on-chip
  1163. Fast Ethernet Controller
  1164. If compiled as module, it will be called fec_mpc52xx.
  1165. config FEC_MPC52xx_MDIO
  1166. bool "MPC52xx FEC MDIO bus driver"
  1167. depends on FEC_MPC52xx
  1168. default y
  1169. ---help---
  1170. The MPC5200's FEC can connect to the Ethernet either with
  1171. an external MII PHY chip or 10 Mbps 7-wire interface
  1172. (Motorola? industry standard).
  1173. If your board uses an external PHY connected to FEC, enable this.
  1174. If not sure, enable.
  1175. If compiled as module, it will be called fec_mpc52xx_phy.
  1176. config ATL2
  1177. tristate "Atheros L2 Fast Ethernet support"
  1178. depends on PCI
  1179. select CRC32
  1180. select MII
  1181. help
  1182. This driver supports the Atheros L2 fast ethernet adapter.
  1183. To compile this driver as a module, choose M here. The module
  1184. will be called atl2.
  1185. config XILINX_EMACLITE
  1186. tristate "Xilinx 10/100 Ethernet Lite support"
  1187. depends on PPC32 || MICROBLAZE
  1188. select PHYLIB
  1189. help
  1190. This driver supports the 10/100 Ethernet Lite from Xilinx.
  1191. config FTMAC100
  1192. tristate "Faraday FTMAC100 10/100 Ethernet support"
  1193. depends on ARM
  1194. select MII
  1195. help
  1196. This driver supports the FTMAC100 10/100 Ethernet controller
  1197. from Faraday. It is used on Faraday A320, Andes AG101 and some
  1198. other ARM/NDS32 SoC's.
  1199. config LANTIQ_ETOP
  1200. tristate "Lantiq SoC ETOP driver"
  1201. depends on SOC_TYPE_XWAY
  1202. help
  1203. Support for the MII0 inside the Lantiq SoC
  1204. source "drivers/net/fs_enet/Kconfig"
  1205. source "drivers/net/octeon/Kconfig"
  1206. endif # NET_ETHERNET
  1207. #
  1208. # Gigabit Ethernet
  1209. #
  1210. menuconfig NETDEV_1000
  1211. bool "Ethernet (1000 Mbit)"
  1212. depends on !UML
  1213. default y
  1214. ---help---
  1215. Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
  1216. type of Local Area Network (LAN) in universities and companies.
  1217. Say Y here to get to see options for Gigabit Ethernet drivers.
  1218. This option alone does not add any kernel code.
  1219. Note that drivers supporting both 100 and 1000 MBit may be listed
  1220. under "Ethernet (10 or 100MBit)" instead.
  1221. If you say N, all options in this submenu will be skipped and disabled.
  1222. if NETDEV_1000
  1223. config DL2K
  1224. tristate "DL2000/TC902x-based Gigabit Ethernet support"
  1225. depends on PCI
  1226. select CRC32
  1227. help
  1228. This driver supports DL2000/TC902x-based Gigabit ethernet cards,
  1229. which includes
  1230. D-Link DGE-550T Gigabit Ethernet Adapter.
  1231. D-Link DL2000-based Gigabit Ethernet Adapter.
  1232. Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
  1233. To compile this driver as a module, choose M here: the
  1234. module will be called dl2k.
  1235. config IP1000
  1236. tristate "IP1000 Gigabit Ethernet support"
  1237. depends on PCI && EXPERIMENTAL
  1238. select MII
  1239. ---help---
  1240. This driver supports IP1000 gigabit Ethernet cards.
  1241. To compile this driver as a module, choose M here: the module
  1242. will be called ipg. This is recommended.
  1243. source "drivers/net/ixp2000/Kconfig"
  1244. config NS83820
  1245. tristate "National Semiconductor DP83820 support"
  1246. depends on PCI
  1247. help
  1248. This is a driver for the National Semiconductor DP83820 series
  1249. of gigabit ethernet MACs. Cards using this chipset include
  1250. the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
  1251. SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of
  1252. zero copy.
  1253. config HAMACHI
  1254. tristate "Packet Engines Hamachi GNIC-II support"
  1255. depends on PCI
  1256. select MII
  1257. help
  1258. If you have a Gigabit Ethernet card of this type, say Y and read
  1259. the Ethernet-HOWTO, available from
  1260. <http://www.tldp.org/docs.html#howto>.
  1261. To compile this driver as a module, choose M here. The module will be
  1262. called hamachi.
  1263. config YELLOWFIN
  1264. tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
  1265. depends on PCI && EXPERIMENTAL
  1266. select CRC32
  1267. ---help---
  1268. Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
  1269. adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
  1270. used by the Beowulf Linux cluster project. See
  1271. <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
  1272. information about this driver in particular and Beowulf in general.
  1273. To compile this driver as a module, choose M here: the module
  1274. will be called yellowfin. This is recommended.
  1275. config R8169
  1276. tristate "Realtek 8169 gigabit ethernet support"
  1277. depends on PCI
  1278. select FW_LOADER
  1279. select CRC32
  1280. select MII
  1281. ---help---
  1282. Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
  1283. To compile this driver as a module, choose M here: the module
  1284. will be called r8169. This is recommended.
  1285. config SIS190
  1286. tristate "SiS190/SiS191 gigabit ethernet support"
  1287. depends on PCI
  1288. select CRC32
  1289. select MII
  1290. ---help---
  1291. Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
  1292. a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
  1293. appear in lan on motherboard designs which are based on SiS 965
  1294. and SiS 966 south bridge.
  1295. To compile this driver as a module, choose M here: the module
  1296. will be called sis190. This is recommended.
  1297. config SKGE
  1298. tristate "Marvell Yukon Gigabit Ethernet support"
  1299. depends on PCI
  1300. select CRC32
  1301. ---help---
  1302. This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
  1303. and related Gigabit Ethernet adapters. It is a new smaller driver
  1304. with better performance and more complete ethtool support.
  1305. It does not support the link failover and network management
  1306. features that "portable" vendor supplied sk98lin driver does.
  1307. This driver supports adapters based on the original Yukon chipset:
  1308. Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
  1309. Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
  1310. It does not support the newer Yukon2 chipset: a separate driver,
  1311. sky2, is provided for these adapters.
  1312. To compile this driver as a module, choose M here: the module
  1313. will be called skge. This is recommended.
  1314. config SKGE_DEBUG
  1315. bool "Debugging interface"
  1316. depends on SKGE && DEBUG_FS
  1317. help
  1318. This option adds the ability to dump driver state for debugging.
  1319. The file /sys/kernel/debug/skge/ethX displays the state of the internal
  1320. transmit and receive rings.
  1321. If unsure, say N.
  1322. config SKGE_GENESIS
  1323. bool "Support for older SysKonnect Genesis boards"
  1324. depends on SKGE
  1325. help
  1326. This enables support for the older and uncommon SysKonnect Genesis
  1327. chips, which support MII via an external transceiver, instead of
  1328. an internal one. Disabling this option will save some memory
  1329. by making code smaller. If unsure say Y.
  1330. config SKY2
  1331. tristate "Marvell Yukon 2 support"
  1332. depends on PCI
  1333. select CRC32
  1334. ---help---
  1335. This driver supports Gigabit Ethernet adapters based on the
  1336. Marvell Yukon 2 chipset:
  1337. Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
  1338. 88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
  1339. There is companion driver for the older Marvell Yukon and
  1340. SysKonnect Genesis based adapters: skge.
  1341. To compile this driver as a module, choose M here: the module
  1342. will be called sky2. This is recommended.
  1343. config SKY2_DEBUG
  1344. bool "Debugging interface"
  1345. depends on SKY2 && DEBUG_FS
  1346. help
  1347. This option adds the ability to dump driver state for debugging.
  1348. The file /sys/kernel/debug/sky2/ethX displays the state of the internal
  1349. transmit and receive rings.
  1350. If unsure, say N.
  1351. config VIA_VELOCITY
  1352. tristate "VIA Velocity support"
  1353. depends on PCI
  1354. select CRC32
  1355. select CRC_CCITT
  1356. select MII
  1357. help
  1358. If you have a VIA "Velocity" based network card say Y here.
  1359. To compile this driver as a module, choose M here. The module
  1360. will be called via-velocity.
  1361. config SPIDER_NET
  1362. tristate "Spider Gigabit Ethernet driver"
  1363. depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
  1364. select FW_LOADER
  1365. help
  1366. This driver supports the Gigabit Ethernet chips present on the
  1367. Cell Processor-Based Blades from IBM.
  1368. config TSI108_ETH
  1369. tristate "Tundra TSI108 gigabit Ethernet support"
  1370. depends on TSI108_BRIDGE
  1371. help
  1372. This driver supports Tundra TSI108 gigabit Ethernet ports.
  1373. To compile this driver as a module, choose M here: the module
  1374. will be called tsi108_eth.
  1375. config GELIC_NET
  1376. tristate "PS3 Gigabit Ethernet driver"
  1377. depends on PPC_PS3
  1378. select PS3_SYS_MANAGER
  1379. help
  1380. This driver supports the network device on the PS3 game
  1381. console. This driver has built-in support for Ethernet.
  1382. To compile this driver as a module, choose M here: the
  1383. module will be called ps3_gelic.
  1384. config GELIC_WIRELESS
  1385. bool "PS3 Wireless support"
  1386. depends on WLAN
  1387. depends on GELIC_NET
  1388. select WIRELESS_EXT
  1389. help
  1390. This option adds the support for the wireless feature of PS3.
  1391. If you have the wireless-less model of PS3 or have no plan to
  1392. use wireless feature, disabling this option saves memory. As
  1393. the driver automatically distinguishes the models, you can
  1394. safely enable this option even if you have a wireless-less model.
  1395. config FSL_PQ_MDIO
  1396. tristate "Freescale PQ MDIO"
  1397. depends on FSL_SOC
  1398. select PHYLIB
  1399. help
  1400. This driver supports the MDIO bus used by the gianfar and UCC drivers.
  1401. config GIANFAR
  1402. tristate "Gianfar Ethernet"
  1403. depends on FSL_SOC
  1404. select FSL_PQ_MDIO
  1405. select PHYLIB
  1406. select CRC32
  1407. help
  1408. This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
  1409. and MPC86xx family of chips, and the FEC on the 8540.
  1410. config UCC_GETH
  1411. tristate "Freescale QE Gigabit Ethernet"
  1412. depends on QUICC_ENGINE
  1413. select FSL_PQ_MDIO
  1414. select PHYLIB
  1415. help
  1416. This driver supports the Gigabit Ethernet mode of the QUICC Engine,
  1417. which is available on some Freescale SOCs.
  1418. config UGETH_TX_ON_DEMAND
  1419. bool "Transmit on Demand support"
  1420. depends on UCC_GETH
  1421. config MV643XX_ETH
  1422. tristate "Marvell Discovery (643XX) and Orion ethernet support"
  1423. depends on (MV64X60 || PPC32 || PLAT_ORION) && INET
  1424. select INET_LRO
  1425. select PHYLIB
  1426. help
  1427. This driver supports the gigabit ethernet MACs in the
  1428. Marvell Discovery PPC/MIPS chipset family (MV643XX) and
  1429. in the Marvell Orion ARM SoC family.
  1430. Some boards that use the Discovery chipset are the Momenco
  1431. Ocelot C and Jaguar ATX and Pegasos II.
  1432. config XILINX_LL_TEMAC
  1433. tristate "Xilinx LL TEMAC (LocalLink Tri-mode Ethernet MAC) driver"
  1434. depends on PPC || MICROBLAZE
  1435. select PHYLIB
  1436. help
  1437. This driver supports the Xilinx 10/100/1000 LocalLink TEMAC
  1438. core used in Xilinx Spartan and Virtex FPGAs
  1439. config ATL1
  1440. tristate "Atheros/Attansic L1 Gigabit Ethernet support"
  1441. depends on PCI
  1442. select CRC32
  1443. select MII
  1444. help
  1445. This driver supports the Atheros/Attansic L1 gigabit ethernet
  1446. adapter.
  1447. To compile this driver as a module, choose M here. The module
  1448. will be called atl1.
  1449. config ATL1E
  1450. tristate "Atheros L1E Gigabit Ethernet support (EXPERIMENTAL)"
  1451. depends on PCI && EXPERIMENTAL
  1452. select CRC32
  1453. select MII
  1454. help
  1455. This driver supports the Atheros L1E gigabit ethernet adapter.
  1456. To compile this driver as a module, choose M here. The module
  1457. will be called atl1e.
  1458. config ATL1C
  1459. tristate "Atheros L1C Gigabit Ethernet support (EXPERIMENTAL)"
  1460. depends on PCI && EXPERIMENTAL
  1461. select CRC32
  1462. select MII
  1463. help
  1464. This driver supports the Atheros L1C gigabit ethernet adapter.
  1465. To compile this driver as a module, choose M here. The module
  1466. will be called atl1c.
  1467. config JME
  1468. tristate "JMicron(R) PCI-Express Gigabit Ethernet support"
  1469. depends on PCI
  1470. select CRC32
  1471. select MII
  1472. ---help---
  1473. This driver supports the PCI-Express gigabit ethernet adapters
  1474. based on JMicron JMC250 chipset.
  1475. To compile this driver as a module, choose M here. The module
  1476. will be called jme.
  1477. config S6GMAC
  1478. tristate "S6105 GMAC ethernet support"
  1479. depends on XTENSA_VARIANT_S6000
  1480. select PHYLIB
  1481. help
  1482. This driver supports the on chip ethernet device on the
  1483. S6105 xtensa processor.
  1484. To compile this driver as a module, choose M here. The module
  1485. will be called s6gmac.
  1486. source "drivers/net/stmmac/Kconfig"
  1487. config PCH_GBE
  1488. tristate "Intel EG20T PCH / OKI SEMICONDUCTOR ML7223 IOH GbE"
  1489. depends on PCI
  1490. select MII
  1491. ---help---
  1492. This is a gigabit ethernet driver for EG20T PCH.
  1493. EG20T PCH is the platform controller hub that is used in Intel's
  1494. general embedded platform.
  1495. EG20T PCH has Gigabit Ethernet interface.
  1496. Using this interface, it is able to access system devices connected
  1497. to Gigabit Ethernet.
  1498. This driver enables Gigabit Ethernet function.
  1499. This driver also can be used for OKI SEMICONDUCTOR IOH(Input/
  1500. Output Hub), ML7223.
  1501. ML7223 IOH is for MP(Media Phone) use.
  1502. ML7223 is companion chip for Intel Atom E6xx series.
  1503. ML7223 is completely compatible for Intel EG20T PCH.
  1504. config FTGMAC100
  1505. tristate "Faraday FTGMAC100 Gigabit Ethernet support"
  1506. depends on ARM
  1507. select PHYLIB
  1508. help
  1509. This driver supports the FTGMAC100 Gigabit Ethernet controller
  1510. from Faraday. It is used on Faraday A369, Andes AG102 and some
  1511. other ARM/NDS32 SoC's.
  1512. endif # NETDEV_1000
  1513. #
  1514. # 10 Gigabit Ethernet
  1515. #
  1516. menuconfig NETDEV_10000
  1517. bool "Ethernet (10000 Mbit)"
  1518. depends on !UML
  1519. default y
  1520. ---help---
  1521. Say Y here to get to see options for 10 Gigabit Ethernet drivers.
  1522. This option alone does not add any kernel code.
  1523. If you say N, all options in this submenu will be skipped and disabled.
  1524. if NETDEV_10000
  1525. config MDIO
  1526. tristate
  1527. config EHEA
  1528. tristate "eHEA Ethernet support"
  1529. depends on IBMEBUS && INET && SPARSEMEM
  1530. select INET_LRO
  1531. ---help---
  1532. This driver supports the IBM pSeries eHEA ethernet adapter.
  1533. To compile the driver as a module, choose M here. The module
  1534. will be called ehea.
  1535. config ENIC
  1536. tristate "Cisco VIC Ethernet NIC Support"
  1537. depends on PCI && INET
  1538. help
  1539. This enables the support for the Cisco VIC Ethernet card.
  1540. config S2IO
  1541. tristate "Exar Xframe 10Gb Ethernet Adapter"
  1542. depends on PCI
  1543. ---help---
  1544. This driver supports Exar Corp's Xframe Series 10Gb Ethernet Adapters.
  1545. More specific information on configuring the driver is in
  1546. <file:Documentation/networking/s2io.txt>.
  1547. To compile this driver as a module, choose M here. The module
  1548. will be called s2io.
  1549. config VXGE
  1550. tristate "Exar X3100 Series 10GbE PCIe Server Adapter"
  1551. depends on PCI && INET
  1552. ---help---
  1553. This driver supports Exar Corp's X3100 Series 10 GbE PCIe
  1554. I/O Virtualized Server Adapter.
  1555. More specific information on configuring the driver is in
  1556. <file:Documentation/networking/vxge.txt>.
  1557. To compile this driver as a module, choose M here. The module
  1558. will be called vxge.
  1559. config VXGE_DEBUG_TRACE_ALL
  1560. bool "Enabling All Debug trace statments in driver"
  1561. default n
  1562. depends on VXGE
  1563. ---help---
  1564. Say Y here if you want to enabling all the debug trace statements in
  1565. the vxge driver. By default only few debug trace statements are
  1566. enabled.
  1567. config MYRI10GE
  1568. tristate "Myricom Myri-10G Ethernet support"
  1569. depends on PCI && INET
  1570. select FW_LOADER
  1571. select CRC32
  1572. select INET_LRO
  1573. ---help---
  1574. This driver supports Myricom Myri-10G Dual Protocol interface in
  1575. Ethernet mode. If the eeprom on your board is not recent enough,
  1576. you will need a newer firmware image.
  1577. You may get this image or more information, at:
  1578. <http://www.myri.com/scs/download-Myri10GE.html>
  1579. To compile this driver as a module, choose M here. The module
  1580. will be called myri10ge.
  1581. config MYRI10GE_DCA
  1582. bool "Direct Cache Access (DCA) Support"
  1583. default y
  1584. depends on MYRI10GE && DCA && !(MYRI10GE=y && DCA=m)
  1585. ---help---
  1586. Say Y here if you want to use Direct Cache Access (DCA) in the
  1587. driver. DCA is a method for warming the CPU cache before data
  1588. is used, with the intent of lessening the impact of cache misses.
  1589. config NETXEN_NIC
  1590. tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
  1591. depends on PCI
  1592. select FW_LOADER
  1593. help
  1594. This enables the support for NetXen's Gigabit Ethernet card.
  1595. config NIU
  1596. tristate "Sun Neptune 10Gbit Ethernet support"
  1597. depends on PCI
  1598. select CRC32
  1599. help
  1600. This enables support for cards based upon Sun's
  1601. Neptune chipset.
  1602. config PASEMI_MAC
  1603. tristate "PA Semi 1/10Gbit MAC"
  1604. depends on PPC_PASEMI && PCI && INET
  1605. select PHYLIB
  1606. select INET_LRO
  1607. help
  1608. This driver supports the on-chip 1/10Gbit Ethernet controller on
  1609. PA Semi's PWRficient line of chips.
  1610. config MLX4_EN
  1611. tristate "Mellanox Technologies 10Gbit Ethernet support"
  1612. depends on PCI && INET
  1613. select MLX4_CORE
  1614. select INET_LRO
  1615. help
  1616. This driver supports Mellanox Technologies ConnectX Ethernet
  1617. devices.
  1618. config MLX4_CORE
  1619. tristate
  1620. depends on PCI
  1621. default n
  1622. config MLX4_DEBUG
  1623. bool "Verbose debugging output" if (MLX4_CORE && EXPERT)
  1624. depends on MLX4_CORE
  1625. default y
  1626. ---help---
  1627. This option causes debugging code to be compiled into the
  1628. mlx4_core driver. The output can be turned on via the
  1629. debug_level module parameter (which can also be set after
  1630. the driver is loaded through sysfs).
  1631. config TEHUTI
  1632. tristate "Tehuti Networks 10G Ethernet"
  1633. depends on PCI
  1634. help
  1635. Tehuti Networks 10G Ethernet NIC
  1636. config BNA
  1637. tristate "Brocade 1010/1020 10Gb Ethernet Driver support"
  1638. depends on PCI
  1639. ---help---
  1640. This driver supports Brocade 1010/1020 10Gb CEE capable Ethernet
  1641. cards.
  1642. To compile this driver as a module, choose M here: the module
  1643. will be called bna.
  1644. For general information and support, go to the Brocade support
  1645. website at:
  1646. <http://support.brocade.com>
  1647. source "drivers/net/sfc/Kconfig"
  1648. source "drivers/net/benet/Kconfig"
  1649. endif # NETDEV_10000
  1650. source "drivers/net/tokenring/Kconfig"
  1651. source "drivers/net/wireless/Kconfig"
  1652. source "drivers/net/wimax/Kconfig"
  1653. source "drivers/net/usb/Kconfig"
  1654. source "drivers/net/pcmcia/Kconfig"
  1655. source "drivers/net/wan/Kconfig"
  1656. source "drivers/atm/Kconfig"
  1657. source "drivers/ieee802154/Kconfig"
  1658. source "drivers/s390/net/Kconfig"
  1659. source "drivers/net/caif/Kconfig"
  1660. config TILE_NET
  1661. tristate "Tilera GBE/XGBE network driver support"
  1662. depends on TILE
  1663. default y
  1664. select CRC32
  1665. help
  1666. This is a standard Linux network device driver for the
  1667. on-chip Tilera Gigabit Ethernet and XAUI interfaces.
  1668. To compile this driver as a module, choose M here: the module
  1669. will be called tile_net.
  1670. config XEN_NETDEV_FRONTEND
  1671. tristate "Xen network device frontend driver"
  1672. depends on XEN
  1673. select XEN_XENBUS_FRONTEND
  1674. default y
  1675. help
  1676. This driver provides support for Xen paravirtual network
  1677. devices exported by a Xen network driver domain (often
  1678. domain 0).
  1679. The corresponding Linux backend driver is enabled by the
  1680. CONFIG_XEN_NETDEV_BACKEND option.
  1681. If you are compiling a kernel for use as Xen guest, you
  1682. should say Y here. To compile this driver as a module, chose
  1683. M here: the module will be called xen-netfront.
  1684. config XEN_NETDEV_BACKEND
  1685. tristate "Xen backend network device"
  1686. depends on XEN_BACKEND
  1687. help
  1688. This driver allows the kernel to act as a Xen network driver
  1689. domain which exports paravirtual network devices to other
  1690. Xen domains. These devices can be accessed by any operating
  1691. system that implements a compatible front end.
  1692. The corresponding Linux frontend driver is enabled by the
  1693. CONFIG_XEN_NETDEV_FRONTEND configuration option.
  1694. The backend driver presents a standard network device
  1695. endpoint for each paravirtual network device to the driver
  1696. domain network stack. These can then be bridged or routed
  1697. etc in order to provide full network connectivity.
  1698. If you are compiling a kernel to run in a Xen network driver
  1699. domain (often this is domain 0) you should say Y here. To
  1700. compile this driver as a module, chose M here: the module
  1701. will be called xen-netback.
  1702. config ISERIES_VETH
  1703. tristate "iSeries Virtual Ethernet driver support"
  1704. depends on PPC_ISERIES
  1705. config RIONET
  1706. tristate "RapidIO Ethernet over messaging driver support"
  1707. depends on RAPIDIO
  1708. config RIONET_TX_SIZE
  1709. int "Number of outbound queue entries"
  1710. depends on RIONET
  1711. default "128"
  1712. config RIONET_RX_SIZE
  1713. int "Number of inbound queue entries"
  1714. depends on RIONET
  1715. default "128"
  1716. config FDDI
  1717. tristate "FDDI driver support"
  1718. depends on (PCI || EISA || TC)
  1719. help
  1720. Fiber Distributed Data Interface is a high speed local area network
  1721. design; essentially a replacement for high speed Ethernet. FDDI can
  1722. run over copper or fiber. If you are connected to such a network and
  1723. want a driver for the FDDI card in your computer, say Y here (and
  1724. then also Y to the driver for your FDDI card, below). Most people
  1725. will say N.
  1726. config DEFXX
  1727. tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
  1728. depends on FDDI && (PCI || EISA || TC)
  1729. ---help---
  1730. This is support for the DIGITAL series of TURBOchannel (DEFTA),
  1731. EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
  1732. to a local FDDI network.
  1733. To compile this driver as a module, choose M here: the module
  1734. will be called defxx. If unsure, say N.
  1735. config DEFXX_MMIO
  1736. bool
  1737. prompt "Use MMIO instead of PIO" if PCI || EISA
  1738. depends on DEFXX
  1739. default n if PCI || EISA
  1740. default y
  1741. ---help---
  1742. This instructs the driver to use EISA or PCI memory-mapped I/O
  1743. (MMIO) as appropriate instead of programmed I/O ports (PIO).
  1744. Enabling this gives an improvement in processing time in parts
  1745. of the driver, but it may cause problems with EISA (DEFEA)
  1746. adapters. TURBOchannel does not have the concept of I/O ports,
  1747. so MMIO is always used for these (DEFTA) adapters.
  1748. If unsure, say N.
  1749. config SKFP
  1750. tristate "SysKonnect FDDI PCI support"
  1751. depends on FDDI && PCI
  1752. select BITREVERSE
  1753. ---help---
  1754. Say Y here if you have a SysKonnect FDDI PCI adapter.
  1755. The following adapters are supported by this driver:
  1756. - SK-5521 (SK-NET FDDI-UP)
  1757. - SK-5522 (SK-NET FDDI-UP DAS)
  1758. - SK-5541 (SK-NET FDDI-FP)
  1759. - SK-5543 (SK-NET FDDI-LP)
  1760. - SK-5544 (SK-NET FDDI-LP DAS)
  1761. - SK-5821 (SK-NET FDDI-UP64)
  1762. - SK-5822 (SK-NET FDDI-UP64 DAS)
  1763. - SK-5841 (SK-NET FDDI-FP64)
  1764. - SK-5843 (SK-NET FDDI-LP64)
  1765. - SK-5844 (SK-NET FDDI-LP64 DAS)
  1766. - Netelligent 100 FDDI DAS Fibre SC
  1767. - Netelligent 100 FDDI SAS Fibre SC
  1768. - Netelligent 100 FDDI DAS UTP
  1769. - Netelligent 100 FDDI SAS UTP
  1770. - Netelligent 100 FDDI SAS Fibre MIC
  1771. Read <file:Documentation/networking/skfp.txt> for information about
  1772. the driver.
  1773. Questions concerning this driver can be addressed to:
  1774. <linux@syskonnect.de>
  1775. To compile this driver as a module, choose M here: the module
  1776. will be called skfp. This is recommended.
  1777. config HIPPI
  1778. bool "HIPPI driver support (EXPERIMENTAL)"
  1779. depends on EXPERIMENTAL && INET && PCI
  1780. help
  1781. HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
  1782. 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
  1783. can run over copper (25m) or fiber (300m on multi-mode or 10km on
  1784. single-mode). HIPPI networks are commonly used for clusters and to
  1785. connect to super computers. If you are connected to a HIPPI network
  1786. and have a HIPPI network card in your computer that you want to use
  1787. under Linux, say Y here (you must also remember to enable the driver
  1788. for your HIPPI card below). Most people will say N here.
  1789. config ROADRUNNER
  1790. tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
  1791. depends on HIPPI && PCI
  1792. help
  1793. Say Y here if this is your PCI HIPPI network card.
  1794. To compile this driver as a module, choose M here: the module
  1795. will be called rrunner. If unsure, say N.
  1796. config ROADRUNNER_LARGE_RINGS
  1797. bool "Use large TX/RX rings (EXPERIMENTAL)"
  1798. depends on ROADRUNNER
  1799. help
  1800. If you say Y here, the RoadRunner driver will preallocate up to 2 MB
  1801. of additional memory to allow for fastest operation, both for
  1802. transmitting and receiving. This memory cannot be used by any other
  1803. kernel code or by user space programs. Say Y here only if you have
  1804. the memory.
  1805. config PLIP
  1806. tristate "PLIP (parallel port) support"
  1807. depends on PARPORT
  1808. ---help---
  1809. PLIP (Parallel Line Internet Protocol) is used to create a
  1810. reasonably fast mini network consisting of two (or, rarely, more)
  1811. local machines. A PLIP link from a Linux box is a popular means to
  1812. install a Linux distribution on a machine which doesn't have a
  1813. CD-ROM drive (a minimal system has to be transferred with floppies
  1814. first). The kernels on both machines need to have this PLIP option
  1815. enabled for this to work.
  1816. The PLIP driver has two modes, mode 0 and mode 1. The parallel
  1817. ports (the connectors at the computers with 25 holes) are connected
  1818. with "null printer" or "Turbo Laplink" cables which can transmit 4
  1819. bits at a time (mode 0) or with special PLIP cables, to be used on
  1820. bidirectional parallel ports only, which can transmit 8 bits at a
  1821. time (mode 1); you can find the wiring of these cables in
  1822. <file:Documentation/networking/PLIP.txt>. The cables can be up to
  1823. 15m long. Mode 0 works also if one of the machines runs DOS/Windows
  1824. and has some PLIP software installed, e.g. the Crynwr PLIP packet
  1825. driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
  1826. and winsock or NCSA's telnet.
  1827. If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
  1828. as the NET-3-HOWTO, both available from
  1829. <http://www.tldp.org/docs.html#howto>. Note that the PLIP
  1830. protocol has been changed and this PLIP driver won't work together
  1831. with the PLIP support in Linux versions 1.0.x. This option enlarges
  1832. your kernel by about 8 KB.
  1833. To compile this driver as a module, choose M here. The module
  1834. will be called plip. If unsure, say Y or M, in case you buy
  1835. a laptop later.
  1836. config PPP
  1837. tristate "PPP (point-to-point protocol) support"
  1838. select SLHC
  1839. ---help---
  1840. PPP (Point to Point Protocol) is a newer and better SLIP. It serves
  1841. the same purpose: sending Internet traffic over telephone (and other
  1842. serial) lines. Ask your access provider if they support it, because
  1843. otherwise you can't use it; most Internet access providers these
  1844. days support PPP rather than SLIP.
  1845. To use PPP, you need an additional program called pppd as described
  1846. in the PPP-HOWTO, available at
  1847. <http://www.tldp.org/docs.html#howto>. Make sure that you have
  1848. the version of pppd recommended in <file:Documentation/Changes>.
  1849. The PPP option enlarges your kernel by about 16 KB.
  1850. There are actually two versions of PPP: the traditional PPP for
  1851. asynchronous lines, such as regular analog phone lines, and
  1852. synchronous PPP which can be used over digital ISDN lines for
  1853. example. If you want to use PPP over phone lines or other
  1854. asynchronous serial lines, you need to say Y (or M) here and also to
  1855. the next option, "PPP support for async serial ports". For PPP over
  1856. synchronous lines, you should say Y (or M) here and to "Support
  1857. synchronous PPP", below.
  1858. If you said Y to "Version information on all symbols" above, then
  1859. you cannot compile the PPP driver into the kernel; you can then only
  1860. compile it as a module. To compile this driver as a module, choose M
  1861. here. The module will be called ppp_generic.
  1862. config PPP_MULTILINK
  1863. bool "PPP multilink support (EXPERIMENTAL)"
  1864. depends on PPP && EXPERIMENTAL
  1865. help
  1866. PPP multilink is a protocol (defined in RFC 1990) which allows you
  1867. to combine several (logical or physical) lines into one logical PPP
  1868. connection, so that you can utilize your full bandwidth.
  1869. This has to be supported at the other end as well and you need a
  1870. version of the pppd daemon which understands the multilink protocol.
  1871. If unsure, say N.
  1872. config PPP_FILTER
  1873. bool "PPP filtering"
  1874. depends on PPP
  1875. help
  1876. Say Y here if you want to be able to filter the packets passing over
  1877. PPP interfaces. This allows you to control which packets count as
  1878. activity (i.e. which packets will reset the idle timer or bring up
  1879. a demand-dialed link) and which packets are to be dropped entirely.
  1880. You need to say Y here if you wish to use the pass-filter and
  1881. active-filter options to pppd.
  1882. If unsure, say N.
  1883. config PPP_ASYNC
  1884. tristate "PPP support for async serial ports"
  1885. depends on PPP
  1886. select CRC_CCITT
  1887. ---help---
  1888. Say Y (or M) here if you want to be able to use PPP over standard
  1889. asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
  1890. a modem (not a synchronous or ISDN modem) to contact your ISP, you
  1891. need this option.
  1892. To compile this driver as a module, choose M here.
  1893. If unsure, say Y.
  1894. config PPP_SYNC_TTY
  1895. tristate "PPP support for sync tty ports"
  1896. depends on PPP
  1897. help
  1898. Say Y (or M) here if you want to be able to use PPP over synchronous
  1899. (HDLC) tty devices, such as the SyncLink adapter. These devices
  1900. are often used for high-speed leased lines like T1/E1.
  1901. To compile this driver as a module, choose M here.
  1902. config PPP_DEFLATE
  1903. tristate "PPP Deflate compression"
  1904. depends on PPP
  1905. select ZLIB_INFLATE
  1906. select ZLIB_DEFLATE
  1907. ---help---
  1908. Support for the Deflate compression method for PPP, which uses the
  1909. Deflate algorithm (the same algorithm that gzip uses) to compress
  1910. each PPP packet before it is sent over the wire. The machine at the
  1911. other end of the PPP link (usually your ISP) has to support the
  1912. Deflate compression method as well for this to be useful. Even if
  1913. they don't support it, it is safe to say Y here.
  1914. To compile this driver as a module, choose M here.
  1915. config PPP_BSDCOMP
  1916. tristate "PPP BSD-Compress compression"
  1917. depends on PPP
  1918. ---help---
  1919. Support for the BSD-Compress compression method for PPP, which uses
  1920. the LZW compression method to compress each PPP packet before it is
  1921. sent over the wire. The machine at the other end of the PPP link
  1922. (usually your ISP) has to support the BSD-Compress compression
  1923. method as well for this to be useful. Even if they don't support it,
  1924. it is safe to say Y here.
  1925. The PPP Deflate compression method ("PPP Deflate compression",
  1926. above) is preferable to BSD-Compress, because it compresses better
  1927. and is patent-free.
  1928. Note that the BSD compression code will always be compiled as a
  1929. module; it is called bsd_comp and will show up in the directory
  1930. modules once you have said "make modules". If unsure, say N.
  1931. config PPP_MPPE
  1932. tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
  1933. depends on PPP && EXPERIMENTAL
  1934. select CRYPTO
  1935. select CRYPTO_SHA1
  1936. select CRYPTO_ARC4
  1937. select CRYPTO_ECB
  1938. ---help---
  1939. Support for the MPPE Encryption protocol, as employed by the
  1940. Microsoft Point-to-Point Tunneling Protocol.
  1941. See http://pptpclient.sourceforge.net/ for information on
  1942. configuring PPTP clients and servers to utilize this method.
  1943. config PPPOE
  1944. tristate "PPP over Ethernet (EXPERIMENTAL)"
  1945. depends on EXPERIMENTAL && PPP
  1946. help
  1947. Support for PPP over Ethernet.
  1948. This driver requires the latest version of pppd from the CVS
  1949. repository at cvs.samba.org. Alternatively, see the
  1950. RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
  1951. which contains instruction on how to use this driver (under
  1952. the heading "Kernel mode PPPoE").
  1953. config PPTP
  1954. tristate "PPP over IPv4 (PPTP) (EXPERIMENTAL)"
  1955. depends on EXPERIMENTAL && PPP && NET_IPGRE_DEMUX
  1956. help
  1957. Support for PPP over IPv4.(Point-to-Point Tunneling Protocol)
  1958. This driver requires pppd plugin to work in client mode or
  1959. modified pptpd (poptop) to work in server mode.
  1960. See http://accel-pptp.sourceforge.net/ for information how to
  1961. utilize this module.
  1962. config PPPOATM
  1963. tristate "PPP over ATM"
  1964. depends on ATM && PPP
  1965. help
  1966. Support PPP (Point to Point Protocol) encapsulated in ATM frames.
  1967. This implementation does not yet comply with section 8 of RFC2364,
  1968. which can lead to bad results if the ATM peer loses state and
  1969. changes its encapsulation unilaterally.
  1970. config PPPOL2TP
  1971. tristate "PPP over L2TP (EXPERIMENTAL)"
  1972. depends on EXPERIMENTAL && L2TP && PPP
  1973. help
  1974. Support for PPP-over-L2TP socket family. L2TP is a protocol
  1975. used by ISPs and enterprises to tunnel PPP traffic over UDP
  1976. tunnels. L2TP is replacing PPTP for VPN uses.
  1977. config SLIP
  1978. tristate "SLIP (serial line) support"
  1979. ---help---
  1980. Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
  1981. connect to your Internet service provider or to connect to some
  1982. other local Unix box or if you want to configure your Linux box as a
  1983. Slip/CSlip server for other people to dial in. SLIP (Serial Line
  1984. Internet Protocol) is a protocol used to send Internet traffic over
  1985. serial connections such as telephone lines or null modem cables;
  1986. nowadays, the protocol PPP is more commonly used for this same
  1987. purpose.
  1988. Normally, your access provider has to support SLIP in order for you
  1989. to be able to use it, but there is now a SLIP emulator called SLiRP
  1990. around (available from
  1991. <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
  1992. allows you to use SLIP over a regular dial up shell connection. If
  1993. you plan to use SLiRP, make sure to say Y to CSLIP, below. The
  1994. NET-3-HOWTO, available from
  1995. <http://www.tldp.org/docs.html#howto>, explains how to
  1996. configure SLIP. Note that you don't need this option if you just
  1997. want to run term (term is a program which gives you almost full
  1998. Internet connectivity if you have a regular dial up shell account on
  1999. some Internet connected Unix computer. Read
  2000. <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
  2001. support will enlarge your kernel by about 4 KB. If unsure, say N.
  2002. To compile this driver as a module, choose M here. The module
  2003. will be called slip.
  2004. config SLIP_COMPRESSED
  2005. bool "CSLIP compressed headers"
  2006. depends on SLIP
  2007. select SLHC
  2008. ---help---
  2009. This protocol is faster than SLIP because it uses compression on the
  2010. TCP/IP headers (not on the data itself), but it has to be supported
  2011. on both ends. Ask your access provider if you are not sure and
  2012. answer Y, just in case. You will still be able to use plain SLIP. If
  2013. you plan to use SLiRP, the SLIP emulator (available from
  2014. <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
  2015. allows you to use SLIP over a regular dial up shell connection, you
  2016. definitely want to say Y here. The NET-3-HOWTO, available from
  2017. <http://www.tldp.org/docs.html#howto>, explains how to configure
  2018. CSLIP. This won't enlarge your kernel.
  2019. config SLHC
  2020. tristate
  2021. help
  2022. This option enables Van Jacobsen serial line header compression
  2023. routines.
  2024. config SLIP_SMART
  2025. bool "Keepalive and linefill"
  2026. depends on SLIP
  2027. help
  2028. Adds additional capabilities to the SLIP driver to support the
  2029. RELCOM line fill and keepalive monitoring. Ideal on poor quality
  2030. analogue lines.
  2031. config SLIP_MODE_SLIP6
  2032. bool "Six bit SLIP encapsulation"
  2033. depends on SLIP
  2034. help
  2035. Just occasionally you may need to run IP over hostile serial
  2036. networks that don't pass all control characters or are only seven
  2037. bit. Saying Y here adds an extra mode you can use with SLIP:
  2038. "slip6". In this mode, SLIP will only send normal ASCII symbols over
  2039. the serial device. Naturally, this has to be supported at the other
  2040. end of the link as well. It's good enough, for example, to run IP
  2041. over the async ports of a Camtec JNT Pad. If unsure, say N.
  2042. config NET_FC
  2043. bool "Fibre Channel driver support"
  2044. depends on SCSI && PCI
  2045. help
  2046. Fibre Channel is a high speed serial protocol mainly used to connect
  2047. large storage devices to the computer; it is compatible with and
  2048. intended to replace SCSI.
  2049. If you intend to use Fibre Channel, you need to have a Fibre channel
  2050. adaptor card in your computer; say Y here and to the driver for your
  2051. adaptor below. You also should have said Y to "SCSI support" and
  2052. "SCSI generic support".
  2053. config NETCONSOLE
  2054. tristate "Network console logging support"
  2055. ---help---
  2056. If you want to log kernel messages over the network, enable this.
  2057. See <file:Documentation/networking/netconsole.txt> for details.
  2058. config NETCONSOLE_DYNAMIC
  2059. bool "Dynamic reconfiguration of logging targets"
  2060. depends on NETCONSOLE && SYSFS && CONFIGFS_FS && \
  2061. !(NETCONSOLE=y && CONFIGFS_FS=m)
  2062. help
  2063. This option enables the ability to dynamically reconfigure target
  2064. parameters (interface, IP addresses, port numbers, MAC addresses)
  2065. at runtime through a userspace interface exported using configfs.
  2066. See <file:Documentation/networking/netconsole.txt> for details.
  2067. config NETPOLL
  2068. def_bool NETCONSOLE
  2069. config NETPOLL_TRAP
  2070. bool "Netpoll traffic trapping"
  2071. default n
  2072. depends on NETPOLL
  2073. config NET_POLL_CONTROLLER
  2074. def_bool NETPOLL
  2075. config VIRTIO_NET
  2076. tristate "Virtio network driver (EXPERIMENTAL)"
  2077. depends on EXPERIMENTAL && VIRTIO
  2078. ---help---
  2079. This is the virtual network driver for virtio. It can be used with
  2080. lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.
  2081. config VMXNET3
  2082. tristate "VMware VMXNET3 ethernet driver"
  2083. depends on PCI && INET
  2084. help
  2085. This driver supports VMware's vmxnet3 virtual ethernet NIC.
  2086. To compile this driver as a module, choose M here: the
  2087. module will be called vmxnet3.
  2088. endif # NETDEVICES