Kconfig 39 KB

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