Kconfig 39 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024102510261027102810291030103110321033103410351036103710381039104010411042104310441045104610471048104910501051105210531054105510561057105810591060106110621063106410651066106710681069107010711072107310741075107610771078107910801081108210831084108510861087108810891090109110921093109410951096
  1. #
  2. # Character device configuration
  3. #
  4. menu "Character devices"
  5. config VT
  6. bool "Virtual terminal" if EMBEDDED
  7. depends on !S390
  8. select INPUT
  9. default y if !VIOCONS
  10. ---help---
  11. If you say Y here, you will get support for terminal devices with
  12. display and keyboard devices. These are called "virtual" because you
  13. can run several virtual terminals (also called virtual consoles) on
  14. one physical terminal. This is rather useful, for example one
  15. virtual terminal can collect system messages and warnings, another
  16. one can be used for a text-mode user session, and a third could run
  17. an X session, all in parallel. Switching between virtual terminals
  18. is done with certain key combinations, usually Alt-<function key>.
  19. The setterm command ("man setterm") can be used to change the
  20. properties (such as colors or beeping) of a virtual terminal. The
  21. man page console_codes(4) ("man console_codes") contains the special
  22. character sequences that can be used to change those properties
  23. directly. The fonts used on virtual terminals can be changed with
  24. the setfont ("man setfont") command and the key bindings are defined
  25. with the loadkeys ("man loadkeys") command.
  26. You need at least one virtual terminal device in order to make use
  27. of your keyboard and monitor. Therefore, only people configuring an
  28. embedded system would want to say N here in order to save some
  29. memory; the only way to log into such a system is then via a serial
  30. or network connection.
  31. If unsure, say Y, or else you won't be able to do much with your new
  32. shiny Linux system :-)
  33. config VT_CONSOLE
  34. bool "Support for console on virtual terminal" if EMBEDDED
  35. depends on VT
  36. default y
  37. ---help---
  38. The system console is the device which receives all kernel messages
  39. and warnings and which allows logins in single user mode. If you
  40. answer Y here, a virtual terminal (the device used to interact with
  41. a physical terminal) can be used as system console. This is the most
  42. common mode of operations, so you should say Y here unless you want
  43. the kernel messages be output only to a serial port (in which case
  44. you should say Y to "Console on serial port", below).
  45. If you do say Y here, by default the currently visible virtual
  46. terminal (/dev/tty0) will be used as system console. You can change
  47. that with a kernel command line option such as "console=tty3" which
  48. would use the third virtual terminal as system console. (Try "man
  49. bootparam" or see the documentation of your boot loader (lilo or
  50. loadlin) about how to pass options to the kernel at boot time.)
  51. If unsure, say Y.
  52. config HW_CONSOLE
  53. bool
  54. depends on VT && !S390 && !UML
  55. default y
  56. config VT_HW_CONSOLE_BINDING
  57. bool "Support for binding and unbinding console drivers"
  58. depends on HW_CONSOLE
  59. default n
  60. ---help---
  61. The virtual terminal is the device that interacts with the physical
  62. terminal through console drivers. On these systems, at least one
  63. console driver is loaded. In other configurations, additional console
  64. drivers may be enabled, such as the framebuffer console. If more than
  65. 1 console driver is enabled, setting this to 'y' will allow you to
  66. select the console driver that will serve as the backend for the
  67. virtual terminals.
  68. See <file:Documentation/console/console.txt> for more
  69. information. For framebuffer console users, please refer to
  70. <file:Documentation/fb/fbcon.txt>.
  71. config DEVKMEM
  72. bool "/dev/kmem virtual device support"
  73. default y
  74. help
  75. Say Y here if you want to support the /dev/kmem device. The
  76. /dev/kmem device is rarely used, but can be used for certain
  77. kind of kernel debugging operations.
  78. When in doubt, say "N".
  79. config SERIAL_NONSTANDARD
  80. bool "Non-standard serial port support"
  81. depends on HAS_IOMEM
  82. ---help---
  83. Say Y here if you have any non-standard serial boards -- boards
  84. which aren't supported using the standard "dumb" serial driver.
  85. This includes intelligent serial boards such as Cyclades,
  86. Digiboards, etc. These are usually used for systems that need many
  87. serial ports because they serve many terminals or dial-in
  88. connections.
  89. Note that the answer to this question won't directly affect the
  90. kernel: saying N will just cause the configurator to skip all
  91. the questions about non-standard serial boards.
  92. Most people can say N here.
  93. config COMPUTONE
  94. tristate "Computone IntelliPort Plus serial support"
  95. depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
  96. ---help---
  97. This driver supports the entire family of Intelliport II/Plus
  98. controllers with the exception of the MicroChannel controllers and
  99. products previous to the Intelliport II. These are multiport cards,
  100. which give you many serial ports. You would need something like this
  101. to connect more than two modems to your Linux box, for instance in
  102. order to become a dial-in server. If you have a card like that, say
  103. Y here and read <file:Documentation/computone.txt>.
  104. To compile this driver as module, choose M here: the
  105. module will be called ip2.
  106. config ROCKETPORT
  107. tristate "Comtrol RocketPort support"
  108. depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
  109. help
  110. This driver supports Comtrol RocketPort and RocketModem PCI boards.
  111. These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
  112. modems. For information about the RocketPort/RocketModem boards
  113. and this driver read <file:Documentation/rocket.txt>.
  114. To compile this driver as a module, choose M here: the
  115. module will be called rocket.
  116. If you want to compile this driver into the kernel, say Y here. If
  117. you don't have a Comtrol RocketPort/RocketModem card installed, say N.
  118. config CYCLADES
  119. tristate "Cyclades async mux support"
  120. depends on SERIAL_NONSTANDARD && (PCI || ISA)
  121. select FW_LOADER
  122. ---help---
  123. This driver supports Cyclades Z and Y multiserial boards.
  124. You would need something like this to connect more than two modems to
  125. your Linux box, for instance in order to become a dial-in server.
  126. For information about the Cyclades-Z card, read
  127. <file:Documentation/README.cycladesZ>.
  128. To compile this driver as a module, choose M here: the
  129. module will be called cyclades.
  130. If you haven't heard about it, it's safe to say N.
  131. config CYZ_INTR
  132. bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
  133. depends on EXPERIMENTAL && CYCLADES
  134. help
  135. The Cyclades-Z family of multiport cards allows 2 (two) driver op
  136. modes: polling and interrupt. In polling mode, the driver will check
  137. the status of the Cyclades-Z ports every certain amount of time
  138. (which is called polling cycle and is configurable). In interrupt
  139. mode, it will use an interrupt line (IRQ) in order to check the
  140. status of the Cyclades-Z ports. The default op mode is polling. If
  141. unsure, say N.
  142. config DIGIEPCA
  143. tristate "Digiboard Intelligent Async Support"
  144. depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
  145. ---help---
  146. This is a driver for Digi International's Xx, Xeve, and Xem series
  147. of cards which provide multiple serial ports. You would need
  148. something like this to connect more than two modems to your Linux
  149. box, for instance in order to become a dial-in server. This driver
  150. supports the original PC (ISA) boards as well as PCI, and EISA. If
  151. you have a card like this, say Y here and read the file
  152. <file:Documentation/digiepca.txt>.
  153. To compile this driver as a module, choose M here: the
  154. module will be called epca.
  155. config ESPSERIAL
  156. tristate "Hayes ESP serial port support"
  157. depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
  158. help
  159. This is a driver which supports Hayes ESP serial ports. Both single
  160. port cards and multiport cards are supported. Make sure to read
  161. <file:Documentation/hayes-esp.txt>.
  162. To compile this driver as a module, choose M here: the
  163. module will be called esp.
  164. If unsure, say N.
  165. config MOXA_INTELLIO
  166. tristate "Moxa Intellio support"
  167. depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
  168. select FW_LOADER
  169. help
  170. Say Y here if you have a Moxa Intellio multiport serial card.
  171. To compile this driver as a module, choose M here: the
  172. module will be called moxa.
  173. config MOXA_SMARTIO
  174. tristate "Moxa SmartIO support v. 2.0"
  175. depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
  176. help
  177. Say Y here if you have a Moxa SmartIO multiport serial card and/or
  178. want to help develop a new version of this driver.
  179. This is upgraded (1.9.1) driver from original Moxa drivers with
  180. changes finally resulting in PCI probing.
  181. This driver can also be built as a module. The module will be called
  182. mxser. If you want to do that, say M here.
  183. config ISI
  184. tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
  185. depends on SERIAL_NONSTANDARD && PCI
  186. select FW_LOADER
  187. help
  188. This is a driver for the Multi-Tech cards which provide several
  189. serial ports. The driver is experimental and can currently only be
  190. built as a module. The module will be called isicom.
  191. If you want to do that, choose M here.
  192. config SYNCLINK
  193. tristate "Microgate SyncLink card support"
  194. depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
  195. help
  196. Provides support for the SyncLink ISA and PCI multiprotocol serial
  197. adapters. These adapters support asynchronous and HDLC bit
  198. synchronous communication up to 10Mbps (PCI adapter).
  199. This driver can only be built as a module ( = code which can be
  200. inserted in and removed from the running kernel whenever you want).
  201. The module will be called synclink. If you want to do that, say M
  202. here.
  203. config SYNCLINKMP
  204. tristate "SyncLink Multiport support"
  205. depends on SERIAL_NONSTANDARD && PCI
  206. help
  207. Enable support for the SyncLink Multiport (2 or 4 ports)
  208. serial adapter, running asynchronous and HDLC communications up
  209. to 2.048Mbps. Each ports is independently selectable for
  210. RS-232, V.35, RS-449, RS-530, and X.21
  211. This driver may be built as a module ( = code which can be
  212. inserted in and removed from the running kernel whenever you want).
  213. The module will be called synclinkmp. If you want to do that, say M
  214. here.
  215. config SYNCLINK_GT
  216. tristate "SyncLink GT/AC support"
  217. depends on SERIAL_NONSTANDARD && PCI
  218. help
  219. Support for SyncLink GT and SyncLink AC families of
  220. synchronous and asynchronous serial adapters
  221. manufactured by Microgate Systems, Ltd. (www.microgate.com)
  222. config N_HDLC
  223. tristate "HDLC line discipline support"
  224. depends on SERIAL_NONSTANDARD
  225. help
  226. Allows synchronous HDLC communications with tty device drivers that
  227. support synchronous HDLC such as the Microgate SyncLink adapter.
  228. This driver can only be built as a module ( = code which can be
  229. inserted in and removed from the running kernel whenever you want).
  230. The module will be called n_hdlc. If you want to do that, say M
  231. here.
  232. config RISCOM8
  233. tristate "SDL RISCom/8 card support"
  234. depends on SERIAL_NONSTANDARD
  235. help
  236. This is a driver for the SDL Communications RISCom/8 multiport card,
  237. which gives you many serial ports. You would need something like
  238. this to connect more than two modems to your Linux box, for instance
  239. in order to become a dial-in server. If you have a card like that,
  240. say Y here and read the file <file:Documentation/riscom8.txt>.
  241. Also it's possible to say M here and compile this driver as kernel
  242. loadable module; the module will be called riscom8.
  243. config SPECIALIX
  244. tristate "Specialix IO8+ card support"
  245. depends on SERIAL_NONSTANDARD
  246. help
  247. This is a driver for the Specialix IO8+ multiport card (both the
  248. ISA and the PCI version) which gives you many serial ports. You
  249. would need something like this to connect more than two modems to
  250. your Linux box, for instance in order to become a dial-in server.
  251. If you have a card like that, say Y here and read the file
  252. <file:Documentation/specialix.txt>. Also it's possible to say M here
  253. and compile this driver as kernel loadable module which will be
  254. called specialix.
  255. config SX
  256. tristate "Specialix SX (and SI) card support"
  257. depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
  258. help
  259. This is a driver for the SX and SI multiport serial cards.
  260. Please read the file <file:Documentation/sx.txt> for details.
  261. This driver can only be built as a module ( = code which can be
  262. inserted in and removed from the running kernel whenever you want).
  263. The module will be called sx. If you want to do that, say M here.
  264. config RIO
  265. tristate "Specialix RIO system support"
  266. depends on SERIAL_NONSTANDARD
  267. help
  268. This is a driver for the Specialix RIO, a smart serial card which
  269. drives an outboard box that can support up to 128 ports. Product
  270. information is at <http://www.perle.com/support/documentation.html#multiport>.
  271. There are both ISA and PCI versions.
  272. config RIO_OLDPCI
  273. bool "Support really old RIO/PCI cards"
  274. depends on RIO
  275. help
  276. Older RIO PCI cards need some initialization-time configuration to
  277. determine the IRQ and some control addresses. If you have a RIO and
  278. this doesn't seem to work, try setting this to Y.
  279. config STALDRV
  280. bool "Stallion multiport serial support"
  281. depends on SERIAL_NONSTANDARD
  282. help
  283. Stallion cards give you many serial ports. You would need something
  284. like this to connect more than two modems to your Linux box, for
  285. instance in order to become a dial-in server. If you say Y here,
  286. you will be asked for your specific card model in the next
  287. questions. Make sure to read <file:Documentation/stallion.txt> in
  288. this case. If you have never heard about all this, it's safe to
  289. say N.
  290. config STALLION
  291. tristate "Stallion EasyIO or EC8/32 support"
  292. depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
  293. help
  294. If you have an EasyIO or EasyConnection 8/32 multiport Stallion
  295. card, then this is for you; say Y. Make sure to read
  296. <file:Documentation/stallion.txt>.
  297. To compile this driver as a module, choose M here: the
  298. module will be called stallion.
  299. config ISTALLION
  300. tristate "Stallion EC8/64, ONboard, Brumby support"
  301. depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
  302. help
  303. If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
  304. serial multiport card, say Y here. Make sure to read
  305. <file:Documentation/stallion.txt>.
  306. To compile this driver as a module, choose M here: the
  307. module will be called istallion.
  308. config NOZOMI
  309. tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
  310. depends on PCI && EXPERIMENTAL
  311. help
  312. If you have a HSDPA driver Broadband Wireless Data Card -
  313. Globe Trotter PCMCIA card, say Y here.
  314. To compile this driver as a module, choose M here, the module
  315. will be called nozomi.
  316. config A2232
  317. tristate "Commodore A2232 serial support (EXPERIMENTAL)"
  318. depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
  319. ---help---
  320. This option supports the 2232 7-port serial card shipped with the
  321. Amiga 2000 and other Zorro-bus machines, dating from 1989. At
  322. a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
  323. each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
  324. ports were connected with 8 pin DIN connectors on the card bracket,
  325. for which 8 pin to DB25 adapters were supplied. The card also had
  326. jumpers internally to toggle various pinning configurations.
  327. This driver can be built as a module; but then "generic_serial"
  328. will also be built as a module. This has to be loaded before
  329. "ser_a2232". If you want to do this, answer M here.
  330. config SGI_SNSC
  331. bool "SGI Altix system controller communication support"
  332. depends on (IA64_SGI_SN2 || IA64_GENERIC)
  333. help
  334. If you have an SGI Altix and you want to enable system
  335. controller communication from user space (you want this!),
  336. say Y. Otherwise, say N.
  337. config SGI_TIOCX
  338. bool "SGI TIO CX driver support"
  339. depends on (IA64_SGI_SN2 || IA64_GENERIC)
  340. help
  341. If you have an SGI Altix and you have fpga devices attached
  342. to your TIO, say Y here, otherwise say N.
  343. config SGI_MBCS
  344. tristate "SGI FPGA Core Services driver support"
  345. depends on SGI_TIOCX
  346. help
  347. If you have an SGI Altix with an attached SABrick
  348. say Y or M here, otherwise say N.
  349. source "drivers/serial/Kconfig"
  350. config UNIX98_PTYS
  351. bool "Unix98 PTY support" if EMBEDDED
  352. default y
  353. ---help---
  354. A pseudo terminal (PTY) is a software device consisting of two
  355. halves: a master and a slave. The slave device behaves identical to
  356. a physical terminal; the master device is used by a process to
  357. read data from and write data to the slave, thereby emulating a
  358. terminal. Typical programs for the master side are telnet servers
  359. and xterms.
  360. Linux has traditionally used the BSD-like names /dev/ptyxx for
  361. masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
  362. has a number of problems. The GNU C library glibc 2.1 and later,
  363. however, supports the Unix98 naming standard: in order to acquire a
  364. pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
  365. terminal is then made available to the process and the pseudo
  366. terminal slave can be accessed as /dev/pts/<number>. What was
  367. traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
  368. All modern Linux systems use the Unix98 ptys. Say Y unless
  369. you're on an embedded system and want to conserve memory.
  370. config LEGACY_PTYS
  371. bool "Legacy (BSD) PTY support"
  372. default y
  373. ---help---
  374. A pseudo terminal (PTY) is a software device consisting of two
  375. halves: a master and a slave. The slave device behaves identical to
  376. a physical terminal; the master device is used by a process to
  377. read data from and write data to the slave, thereby emulating a
  378. terminal. Typical programs for the master side are telnet servers
  379. and xterms.
  380. Linux has traditionally used the BSD-like names /dev/ptyxx
  381. for masters and /dev/ttyxx for slaves of pseudo
  382. terminals. This scheme has a number of problems, including
  383. security. This option enables these legacy devices; on most
  384. systems, it is safe to say N.
  385. config LEGACY_PTY_COUNT
  386. int "Maximum number of legacy PTY in use"
  387. depends on LEGACY_PTYS
  388. range 0 256
  389. default "256"
  390. ---help---
  391. The maximum number of legacy PTYs that can be used at any one time.
  392. The default is 256, and should be more than enough. Embedded
  393. systems may want to reduce this to save memory.
  394. When not in use, each legacy PTY occupies 12 bytes on 32-bit
  395. architectures and 24 bytes on 64-bit architectures.
  396. config BRIQ_PANEL
  397. tristate 'Total Impact briQ front panel driver'
  398. depends on PPC_CHRP
  399. ---help---
  400. The briQ is a small footprint CHRP computer with a frontpanel VFD, a
  401. tristate led and two switches. It is the size of a CDROM drive.
  402. If you have such one and want anything showing on the VFD then you
  403. must answer Y here.
  404. To compile this driver as a module, choose M here: the
  405. module will be called briq_panel.
  406. It's safe to say N here.
  407. config BFIN_OTP
  408. tristate "Blackfin On-Chip OTP Memory Support"
  409. depends on BLACKFIN && (BF52x || BF54x)
  410. default y
  411. help
  412. If you say Y here, you will get support for a character device
  413. interface into the One Time Programmable memory pages that are
  414. stored on the Blackfin processor. This will not get you access
  415. to the secure memory pages however. You will need to write your
  416. own secure code and reader for that.
  417. To compile this driver as a module, choose M here: the module
  418. will be called bfin-otp.
  419. If unsure, it is safe to say Y.
  420. config BFIN_OTP_WRITE_ENABLE
  421. bool "Enable writing support of OTP pages"
  422. depends on BFIN_OTP
  423. default n
  424. help
  425. If you say Y here, you will enable support for writing of the
  426. OTP pages. This is dangerous by nature as you can only program
  427. the pages once, so only enable this option when you actually
  428. need it so as to not inadvertently clobber data.
  429. If unsure, say N.
  430. config PRINTER
  431. tristate "Parallel printer support"
  432. depends on PARPORT
  433. ---help---
  434. If you intend to attach a printer to the parallel port of your Linux
  435. box (as opposed to using a serial printer; if the connector at the
  436. printer has 9 or 25 holes ["female"], then it's serial), say Y.
  437. Also read the Printing-HOWTO, available from
  438. <http://www.tldp.org/docs.html#howto>.
  439. It is possible to share one parallel port among several devices
  440. (e.g. printer and ZIP drive) and it is safe to compile the
  441. corresponding drivers into the kernel.
  442. To compile this driver as a module, choose M here and read
  443. <file:Documentation/parport.txt>. The module will be called lp.
  444. If you have several parallel ports, you can specify which ports to
  445. use with the "lp" kernel command line option. (Try "man bootparam"
  446. or see the documentation of your boot loader (lilo or loadlin) about
  447. how to pass options to the kernel at boot time.) The syntax of the
  448. "lp" command line option can be found in <file:drivers/char/lp.c>.
  449. If you have more than 8 printers, you need to increase the LP_NO
  450. macro in lp.c and the PARPORT_MAX macro in parport.h.
  451. config LP_CONSOLE
  452. bool "Support for console on line printer"
  453. depends on PRINTER
  454. ---help---
  455. If you want kernel messages to be printed out as they occur, you
  456. can have a console on the printer. This option adds support for
  457. doing that; to actually get it to happen you need to pass the
  458. option "console=lp0" to the kernel at boot time.
  459. If the printer is out of paper (or off, or unplugged, or too
  460. busy..) the kernel will stall until the printer is ready again.
  461. By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
  462. can make the kernel continue when this happens,
  463. but it'll lose the kernel messages.
  464. If unsure, say N.
  465. config PPDEV
  466. tristate "Support for user-space parallel port device drivers"
  467. depends on PARPORT
  468. ---help---
  469. Saying Y to this adds support for /dev/parport device nodes. This
  470. is needed for programs that want portable access to the parallel
  471. port, for instance deviceid (which displays Plug-and-Play device
  472. IDs).
  473. This is the parallel port equivalent of SCSI generic support (sg).
  474. It is safe to say N to this -- it is not needed for normal printing
  475. or parallel port CD-ROM/disk support.
  476. To compile this driver as a module, choose M here: the
  477. module will be called ppdev.
  478. If unsure, say N.
  479. config HVC_DRIVER
  480. bool
  481. help
  482. Generic "hypervisor virtual console" infrastructure for various
  483. hypervisors (pSeries, iSeries, Xen, lguest).
  484. It will automatically be selected if one of the back-end console drivers
  485. is selected.
  486. config HVC_IRQ
  487. bool
  488. config HVC_CONSOLE
  489. bool "pSeries Hypervisor Virtual Console support"
  490. depends on PPC_PSERIES
  491. select HVC_DRIVER
  492. select HVC_IRQ
  493. help
  494. pSeries machines when partitioned support a hypervisor virtual
  495. console. This driver allows each pSeries partition to have a console
  496. which is accessed via the HMC.
  497. config HVC_ISERIES
  498. bool "iSeries Hypervisor Virtual Console support"
  499. depends on PPC_ISERIES
  500. default y
  501. select HVC_DRIVER
  502. select HVC_IRQ
  503. help
  504. iSeries machines support a hypervisor virtual console.
  505. config HVC_RTAS
  506. bool "IBM RTAS Console support"
  507. depends on PPC_RTAS
  508. select HVC_DRIVER
  509. help
  510. IBM Console device driver which makes use of RTAS
  511. config HVC_BEAT
  512. bool "Toshiba's Beat Hypervisor Console support"
  513. depends on PPC_CELLEB
  514. select HVC_DRIVER
  515. help
  516. Toshiba's Cell Reference Set Beat Console device driver
  517. config HVC_XEN
  518. bool "Xen Hypervisor Console support"
  519. depends on XEN
  520. select HVC_DRIVER
  521. select HVC_IRQ
  522. default y
  523. help
  524. Xen virtual console device driver
  525. config VIRTIO_CONSOLE
  526. bool
  527. select HVC_DRIVER
  528. config HVCS
  529. tristate "IBM Hypervisor Virtual Console Server support"
  530. depends on PPC_PSERIES
  531. help
  532. Partitionable IBM Power5 ppc64 machines allow hosting of
  533. firmware virtual consoles from one Linux partition by
  534. another Linux partition. This driver allows console data
  535. from Linux partitions to be accessed through TTY device
  536. interfaces in the device tree of a Linux partition running
  537. this driver.
  538. To compile this driver as a module, choose M here: the
  539. module will be called hvcs.ko. Additionally, this module
  540. will depend on arch specific APIs exported from hvcserver.ko
  541. which will also be compiled when this driver is built as a
  542. module.
  543. config IBM_BSR
  544. tristate "IBM POWER Barrier Synchronization Register support"
  545. depends on PPC_PSERIES
  546. help
  547. This devices exposes a hardware mechanism for fast synchronization
  548. of threads across a large system which avoids bouncing a cacheline
  549. between several cores on a system
  550. source "drivers/char/ipmi/Kconfig"
  551. config DS1620
  552. tristate "NetWinder thermometer support"
  553. depends on ARCH_NETWINDER
  554. help
  555. Say Y here to include support for the thermal management hardware
  556. found in the NetWinder. This driver allows the user to control the
  557. temperature set points and to read the current temperature.
  558. It is also possible to say M here to build it as a module (ds1620)
  559. It is recommended to be used on a NetWinder, but it is not a
  560. necessity.
  561. config NWBUTTON
  562. tristate "NetWinder Button"
  563. depends on ARCH_NETWINDER
  564. ---help---
  565. If you say Y here and create a character device node /dev/nwbutton
  566. with major and minor numbers 10 and 158 ("man mknod"), then every
  567. time the orange button is pressed a number of times, the number of
  568. times the button was pressed will be written to that device.
  569. This is most useful for applications, as yet unwritten, which
  570. perform actions based on how many times the button is pressed in a
  571. row.
  572. Do not hold the button down for too long, as the driver does not
  573. alter the behaviour of the hardware reset circuitry attached to the
  574. button; it will still execute a hard reset if the button is held
  575. down for longer than approximately five seconds.
  576. To compile this driver as a module, choose M here: the
  577. module will be called nwbutton.
  578. Most people will answer Y to this question and "Reboot Using Button"
  579. below to be able to initiate a system shutdown from the button.
  580. config NWBUTTON_REBOOT
  581. bool "Reboot Using Button"
  582. depends on NWBUTTON
  583. help
  584. If you say Y here, then you will be able to initiate a system
  585. shutdown and reboot by pressing the orange button a number of times.
  586. The number of presses to initiate the shutdown is two by default,
  587. but this can be altered by modifying the value of NUM_PRESSES_REBOOT
  588. in nwbutton.h and recompiling the driver or, if you compile the
  589. driver as a module, you can specify the number of presses at load
  590. time with "insmod button reboot_count=<something>".
  591. config NWFLASH
  592. tristate "NetWinder flash support"
  593. depends on ARCH_NETWINDER
  594. ---help---
  595. If you say Y here and create a character device /dev/flash with
  596. major 10 and minor 160 you can manipulate the flash ROM containing
  597. the NetWinder firmware. Be careful as accidentally overwriting the
  598. flash contents can render your computer unbootable. On no account
  599. allow random users access to this device. :-)
  600. To compile this driver as a module, choose M here: the
  601. module will be called nwflash.
  602. If you're not sure, say N.
  603. source "drivers/char/hw_random/Kconfig"
  604. config NVRAM
  605. tristate "/dev/nvram support"
  606. depends on ATARI || X86 || ARM || GENERIC_NVRAM
  607. ---help---
  608. If you say Y here and create a character special file /dev/nvram
  609. with major number 10 and minor number 144 using mknod ("man mknod"),
  610. you get read and write access to the extra bytes of non-volatile
  611. memory in the real time clock (RTC), which is contained in every PC
  612. and most Ataris. The actual number of bytes varies, depending on the
  613. nvram in the system, but is usually 114 (128-14 for the RTC).
  614. This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
  615. on Ataris. /dev/nvram may be used to view settings there, or to
  616. change them (with some utility). It could also be used to frequently
  617. save a few bits of very important data that may not be lost over
  618. power-off and for which writing to disk is too insecure. Note
  619. however that most NVRAM space in a PC belongs to the BIOS and you
  620. should NEVER idly tamper with it. See Ralf Brown's interrupt list
  621. for a guide to the use of CMOS bytes by your BIOS.
  622. On Atari machines, /dev/nvram is always configured and does not need
  623. to be selected.
  624. To compile this driver as a module, choose M here: the
  625. module will be called nvram.
  626. #
  627. # These legacy RTC drivers just cause too many conflicts with the generic
  628. # RTC framework ... let's not even try to coexist any more.
  629. #
  630. if RTC_LIB=n
  631. config RTC
  632. tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
  633. depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
  634. && !ARM && !SUPERH && !S390 && !AVR32
  635. ---help---
  636. If you say Y here and create a character special file /dev/rtc with
  637. major number 10 and minor number 135 using mknod ("man mknod"), you
  638. will get access to the real time clock (or hardware clock) built
  639. into your computer.
  640. Every PC has such a clock built in. It can be used to generate
  641. signals from as low as 1Hz up to 8192Hz, and can also be used
  642. as a 24 hour alarm. It reports status information via the file
  643. /proc/driver/rtc and its behaviour is set by various ioctls on
  644. /dev/rtc.
  645. If you run Linux on a multiprocessor machine and said Y to
  646. "Symmetric Multi Processing" above, you should say Y here to read
  647. and set the RTC in an SMP compatible fashion.
  648. If you think you have a use for such a device (such as periodic data
  649. sampling), then say Y here, and read <file:Documentation/rtc.txt>
  650. for details.
  651. To compile this driver as a module, choose M here: the
  652. module will be called rtc.
  653. config JS_RTC
  654. tristate "Enhanced Real Time Clock Support"
  655. depends on SPARC32 && PCI
  656. ---help---
  657. If you say Y here and create a character special file /dev/rtc with
  658. major number 10 and minor number 135 using mknod ("man mknod"), you
  659. will get access to the real time clock (or hardware clock) built
  660. into your computer.
  661. Every PC has such a clock built in. It can be used to generate
  662. signals from as low as 1Hz up to 8192Hz, and can also be used
  663. as a 24 hour alarm. It reports status information via the file
  664. /proc/driver/rtc and its behaviour is set by various ioctls on
  665. /dev/rtc.
  666. If you think you have a use for such a device (such as periodic data
  667. sampling), then say Y here, and read <file:Documentation/rtc.txt>
  668. for details.
  669. To compile this driver as a module, choose M here: the
  670. module will be called js-rtc.
  671. config SGI_DS1286
  672. tristate "SGI DS1286 RTC support"
  673. depends on SGI_HAS_DS1286
  674. help
  675. If you say Y here and create a character special file /dev/rtc with
  676. major number 10 and minor number 135 using mknod ("man mknod"), you
  677. will get access to the real time clock built into your computer.
  678. Every SGI has such a clock built in. It reports status information
  679. via the file /proc/rtc and its behaviour is set by various ioctls on
  680. /dev/rtc.
  681. config SGI_IP27_RTC
  682. bool "SGI M48T35 RTC support"
  683. depends on SGI_IP27
  684. help
  685. If you say Y here and create a character special file /dev/rtc with
  686. major number 10 and minor number 135 using mknod ("man mknod"), you
  687. will get access to the real time clock built into your computer.
  688. Every SGI has such a clock built in. It reports status information
  689. via the file /proc/rtc and its behaviour is set by various ioctls on
  690. /dev/rtc.
  691. config GEN_RTC
  692. tristate "Generic /dev/rtc emulation"
  693. depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32
  694. ---help---
  695. If you say Y here and create a character special file /dev/rtc with
  696. major number 10 and minor number 135 using mknod ("man mknod"), you
  697. will get access to the real time clock (or hardware clock) built
  698. into your computer.
  699. It reports status information via the file /proc/driver/rtc and its
  700. behaviour is set by various ioctls on /dev/rtc. If you enable the
  701. "extended RTC operation" below it will also provide an emulation
  702. for RTC_UIE which is required by some programs and may improve
  703. precision in some cases.
  704. To compile this driver as a module, choose M here: the
  705. module will be called genrtc.
  706. config GEN_RTC_X
  707. bool "Extended RTC operation"
  708. depends on GEN_RTC
  709. help
  710. Provides an emulation for RTC_UIE which is required by some programs
  711. and may improve precision of the generic RTC support in some cases.
  712. config EFI_RTC
  713. bool "EFI Real Time Clock Services"
  714. depends on IA64
  715. config DS1302
  716. tristate "DS1302 RTC support"
  717. depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
  718. help
  719. If you say Y here and create a character special file /dev/rtc with
  720. major number 121 and minor number 0 using mknod ("man mknod"), you
  721. will get access to the real time clock (or hardware clock) built
  722. into your computer.
  723. endif # RTC_LIB
  724. config DTLK
  725. tristate "Double Talk PC internal speech card support"
  726. depends on ISA
  727. help
  728. This driver is for the DoubleTalk PC, a speech synthesizer
  729. manufactured by RC Systems (<http://www.rcsys.com/>). It is also
  730. called the `internal DoubleTalk'.
  731. To compile this driver as a module, choose M here: the
  732. module will be called dtlk.
  733. config XILINX_HWICAP
  734. tristate "Xilinx HWICAP Support"
  735. depends on XILINX_VIRTEX
  736. help
  737. This option enables support for Xilinx Internal Configuration
  738. Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
  739. FPGA platforms to partially reconfigure the FPGA at runtime.
  740. If unsure, say N.
  741. config R3964
  742. tristate "Siemens R3964 line discipline"
  743. ---help---
  744. This driver allows synchronous communication with devices using the
  745. Siemens R3964 packet protocol. Unless you are dealing with special
  746. hardware like PLCs, you are unlikely to need this.
  747. To compile this driver as a module, choose M here: the
  748. module will be called n_r3964.
  749. If unsure, say N.
  750. config APPLICOM
  751. tristate "Applicom intelligent fieldbus card support"
  752. depends on PCI
  753. ---help---
  754. This driver provides the kernel-side support for the intelligent
  755. fieldbus cards made by Applicom International. More information
  756. about these cards can be found on the WWW at the address
  757. <http://www.applicom-int.com/>, or by email from David Woodhouse
  758. <dwmw2@infradead.org>.
  759. To compile this driver as a module, choose M here: the
  760. module will be called applicom.
  761. If unsure, say N.
  762. config SONYPI
  763. tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
  764. depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
  765. ---help---
  766. This driver enables access to the Sony Programmable I/O Control
  767. Device which can be found in many (all ?) Sony Vaio laptops.
  768. If you have one of those laptops, read
  769. <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
  770. To compile this driver as a module, choose M here: the
  771. module will be called sonypi.
  772. config GPIO_TB0219
  773. tristate "TANBAC TB0219 GPIO support"
  774. depends on TANBAC_TB022X
  775. select GPIO_VR41XX
  776. source "drivers/char/pcmcia/Kconfig"
  777. config MWAVE
  778. tristate "ACP Modem (Mwave) support"
  779. depends on X86
  780. select SERIAL_8250
  781. ---help---
  782. The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
  783. kernel driver and a user level application. Together these components
  784. support direct attachment to public switched telephone networks (PSTNs)
  785. and support selected world wide countries.
  786. This version of the ACP Modem driver supports the IBM Thinkpad 600E,
  787. 600, and 770 that include on board ACP modem hardware.
  788. The modem also supports the standard communications port interface
  789. (ttySx) and is compatible with the Hayes AT Command Set.
  790. The user level application needed to use this driver can be found at
  791. the IBM Linux Technology Center (LTC) web site:
  792. <http://www.ibm.com/linux/ltc/>.
  793. If you own one of the above IBM Thinkpads which has the Mwave chipset
  794. in it, say Y.
  795. To compile this driver as a module, choose M here: the
  796. module will be called mwave.
  797. config SCx200_GPIO
  798. tristate "NatSemi SCx200 GPIO Support"
  799. depends on SCx200
  800. select NSC_GPIO
  801. help
  802. Give userspace access to the GPIO pins on the National
  803. Semiconductor SCx200 processors.
  804. If compiled as a module, it will be called scx200_gpio.
  805. config PC8736x_GPIO
  806. tristate "NatSemi PC8736x GPIO Support"
  807. depends on X86
  808. default SCx200_GPIO # mostly N
  809. select NSC_GPIO # needed for support routines
  810. help
  811. Give userspace access to the GPIO pins on the National
  812. Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
  813. has multiple functional units, inc several managed by
  814. hwmon/pc87360 driver. Tested with PC-87366
  815. If compiled as a module, it will be called pc8736x_gpio.
  816. config NSC_GPIO
  817. tristate "NatSemi Base GPIO Support"
  818. depends on X86_32
  819. # selected by SCx200_GPIO and PC8736x_GPIO
  820. # what about 2 selectors differing: m != y
  821. help
  822. Common support used (and needed) by scx200_gpio and
  823. pc8736x_gpio drivers. If those drivers are built as
  824. modules, this one will be too, named nsc_gpio
  825. config CS5535_GPIO
  826. tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
  827. depends on X86_32
  828. help
  829. Give userspace access to the GPIO pins on the AMD CS5535 and
  830. CS5536 Geode companion devices.
  831. If compiled as a module, it will be called cs5535_gpio.
  832. config GPIO_VR41XX
  833. tristate "NEC VR4100 series General-purpose I/O Unit support"
  834. depends on CPU_VR41XX
  835. config RAW_DRIVER
  836. tristate "RAW driver (/dev/raw/rawN)"
  837. depends on BLOCK
  838. help
  839. The raw driver permits block devices to be bound to /dev/raw/rawN.
  840. Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
  841. See the raw(8) manpage for more details.
  842. Applications should preferably open the device (eg /dev/hda1)
  843. with the O_DIRECT flag.
  844. config MAX_RAW_DEVS
  845. int "Maximum number of RAW devices to support (1-8192)"
  846. depends on RAW_DRIVER
  847. default "256"
  848. help
  849. The maximum number of RAW devices that are supported.
  850. Default is 256. Increase this number in case you need lots of
  851. raw devices.
  852. config HPET
  853. bool "HPET - High Precision Event Timer" if (X86 || IA64)
  854. default n
  855. depends on ACPI
  856. help
  857. If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
  858. open selects one of the timers supported by the HPET. The timers are
  859. non-periodic and/or periodic.
  860. config HPET_RTC_IRQ
  861. bool
  862. default HPET_EMULATE_RTC
  863. depends on RTC && HPET
  864. help
  865. If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
  866. is assumed the platform called hpet_alloc with the RTC IRQ values for
  867. the HPET timers.
  868. config HPET_MMAP
  869. bool "Allow mmap of HPET"
  870. default y
  871. depends on HPET
  872. help
  873. If you say Y here, user applications will be able to mmap
  874. the HPET registers.
  875. In some hardware implementations, the page containing HPET
  876. registers may also contain other things that shouldn't be
  877. exposed to the user. If this applies to your hardware,
  878. say N here.
  879. config HANGCHECK_TIMER
  880. tristate "Hangcheck timer"
  881. depends on X86 || IA64 || PPC64 || S390
  882. help
  883. The hangcheck-timer module detects when the system has gone
  884. out to lunch past a certain margin. It can reboot the system
  885. or merely print a warning.
  886. config MMTIMER
  887. tristate "MMTIMER Memory mapped RTC for SGI Altix"
  888. depends on IA64_GENERIC || IA64_SGI_SN2
  889. default y
  890. help
  891. The mmtimer device allows direct userspace access to the
  892. Altix system timer.
  893. source "drivers/char/tpm/Kconfig"
  894. config TELCLOCK
  895. tristate "Telecom clock driver for ATCA SBC"
  896. depends on EXPERIMENTAL && X86
  897. default n
  898. help
  899. The telecom clock device is specific to the MPCBL0010 and MPCBL0050
  900. ATCA computers and allows direct userspace access to the
  901. configuration of the telecom clock configuration settings. This
  902. device is used for hardware synchronization across the ATCA backplane
  903. fabric. Upon loading, the driver exports a sysfs directory,
  904. /sys/devices/platform/telco_clock, with a number of files for
  905. controlling the behavior of this hardware.
  906. config DEVPORT
  907. bool
  908. depends on !M68K
  909. depends on ISA || PCI
  910. default y
  911. source "drivers/s390/char/Kconfig"
  912. endmenu