Kconfig 38 KB

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