Kconfig 40 KB

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