Kconfig 39 KB

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