Kconfig.char 8.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238
  1. menu "Character Devices"
  2. config STDERR_CONSOLE
  3. bool "stderr console"
  4. default y
  5. help
  6. console driver which dumps all printk messages to stderr.
  7. config STDIO_CONSOLE
  8. bool
  9. default y
  10. config SSL
  11. bool "Virtual serial line"
  12. help
  13. The User-Mode Linux environment allows you to create virtual serial
  14. lines on the UML that are usually made to show up on the host as
  15. ttys or ptys.
  16. See <http://user-mode-linux.sourceforge.net/input.html> for more
  17. information and command line examples of how to use this facility.
  18. Unless you have a specific reason for disabling this, say Y.
  19. config NULL_CHAN
  20. bool "null channel support"
  21. help
  22. This option enables support for attaching UML consoles and serial
  23. lines to a device similar to /dev/null. Data written to it disappears
  24. and there is never any data to be read.
  25. config PORT_CHAN
  26. bool "port channel support"
  27. help
  28. This option enables support for attaching UML consoles and serial
  29. lines to host portals. They may be accessed with 'telnet <host>
  30. <port number>'. Any number of consoles and serial lines may be
  31. attached to a single portal, although what UML device you get when
  32. you telnet to that portal will be unpredictable.
  33. It is safe to say 'Y' here.
  34. config PTY_CHAN
  35. bool "pty channel support"
  36. help
  37. This option enables support for attaching UML consoles and serial
  38. lines to host pseudo-terminals. Access to both traditional
  39. pseudo-terminals (/dev/pty*) and pts pseudo-terminals are controlled
  40. with this option. The assignment of UML devices to host devices
  41. will be announced in the kernel message log.
  42. It is safe to say 'Y' here.
  43. config TTY_CHAN
  44. bool "tty channel support"
  45. help
  46. This option enables support for attaching UML consoles and serial
  47. lines to host terminals. Access to both virtual consoles
  48. (/dev/tty*) and the slave side of pseudo-terminals (/dev/ttyp* and
  49. /dev/pts/*) are controlled by this option.
  50. It is safe to say 'Y' here.
  51. config XTERM_CHAN
  52. bool "xterm channel support"
  53. help
  54. This option enables support for attaching UML consoles and serial
  55. lines to xterms. Each UML device so assigned will be brought up in
  56. its own xterm.
  57. If you disable this option, then CONFIG_PT_PROXY will be disabled as
  58. well, since UML's gdb currently requires an xterm.
  59. It is safe to say 'Y' here.
  60. config NOCONFIG_CHAN
  61. bool
  62. default !(XTERM_CHAN && TTY_CHAN && PTY_CHAN && PORT_CHAN && NULL_CHAN)
  63. config CON_ZERO_CHAN
  64. string "Default main console channel initialization"
  65. default "fd:0,fd:1"
  66. help
  67. This is the string describing the channel to which the main console
  68. will be attached by default. This value can be overridden from the
  69. command line. The default value is "fd:0,fd:1", which attaches the
  70. main console to stdin and stdout.
  71. It is safe to leave this unchanged.
  72. config CON_CHAN
  73. string "Default console channel initialization"
  74. default "xterm"
  75. help
  76. This is the string describing the channel to which all consoles
  77. except the main console will be attached by default. This value can
  78. be overridden from the command line. The default value is "xterm",
  79. which brings them up in xterms.
  80. It is safe to leave this unchanged, although you may wish to change
  81. this if you expect the UML that you build to be run in environments
  82. which don't have X or xterm available.
  83. config SSL_CHAN
  84. string "Default serial line channel initialization"
  85. default "pty"
  86. help
  87. This is the string describing the channel to which the serial lines
  88. will be attached by default. This value can be overridden from the
  89. command line. The default value is "pty", which attaches them to
  90. traditional pseudo-terminals.
  91. It is safe to leave this unchanged, although you may wish to change
  92. this if you expect the UML that you build to be run in environments
  93. which don't have a set of /dev/pty* devices.
  94. config UNIX98_PTYS
  95. bool "Unix98 PTY support"
  96. ---help---
  97. A pseudo terminal (PTY) is a software device consisting of two
  98. halves: a master and a slave. The slave device behaves identical to
  99. a physical terminal; the master device is used by a process to
  100. read data from and write data to the slave, thereby emulating a
  101. terminal. Typical programs for the master side are telnet servers
  102. and xterms.
  103. Linux has traditionally used the BSD-like names /dev/ptyxx for
  104. masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
  105. has a number of problems. The GNU C library glibc 2.1 and later,
  106. however, supports the Unix98 naming standard: in order to acquire a
  107. pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
  108. terminal is then made available to the process and the pseudo
  109. terminal slave can be accessed as /dev/pts/<number>. What was
  110. traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
  111. All modern Linux systems use the Unix98 ptys. Say Y unless
  112. you're on an embedded system and want to conserve memory.
  113. config LEGACY_PTYS
  114. bool "Legacy (BSD) PTY support"
  115. default y
  116. ---help---
  117. A pseudo terminal (PTY) is a software device consisting of two
  118. halves: a master and a slave. The slave device behaves identical to
  119. a physical terminal; the master device is used by a process to
  120. read data from and write data to the slave, thereby emulating a
  121. terminal. Typical programs for the master side are telnet servers
  122. and xterms.
  123. Linux has traditionally used the BSD-like names /dev/ptyxx
  124. for masters and /dev/ttyxx for slaves of pseudo
  125. terminals. This scheme has a number of problems, including
  126. security. This option enables these legacy devices; on most
  127. systems, it is safe to say N.
  128. config RAW_DRIVER
  129. tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
  130. help
  131. The raw driver permits block devices to be bound to /dev/raw/rawN.
  132. Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
  133. See the raw(8) manpage for more details.
  134. The raw driver is deprecated and will be removed soon.
  135. Applications should simply open the device (eg /dev/hda1)
  136. with the O_DIRECT flag.
  137. config MAX_RAW_DEVS
  138. int "Maximum number of RAW devices to support (1-8192)"
  139. depends on RAW_DRIVER
  140. default "256"
  141. help
  142. The maximum number of RAW devices that are supported.
  143. Default is 256. Increase this number in case you need lots of
  144. raw devices.
  145. config LEGACY_PTY_COUNT
  146. int "Maximum number of legacy PTY in use"
  147. depends on LEGACY_PTYS
  148. default "256"
  149. ---help---
  150. The maximum number of legacy PTYs that can be used at any one time.
  151. The default is 256, and should be more than enough. Embedded
  152. systems may want to reduce this to save memory.
  153. When not in use, each legacy PTY occupies 12 bytes on 32-bit
  154. architectures and 24 bytes on 64-bit architectures.
  155. config WATCHDOG
  156. bool "Watchdog Timer Support"
  157. config WATCHDOG_NOWAYOUT
  158. bool "Disable watchdog shutdown on close"
  159. depends on WATCHDOG
  160. config SOFT_WATCHDOG
  161. tristate "Software Watchdog"
  162. depends on WATCHDOG
  163. config UML_WATCHDOG
  164. tristate "UML watchdog"
  165. depends on WATCHDOG
  166. config UML_SOUND
  167. tristate "Sound support"
  168. help
  169. This option enables UML sound support. If enabled, it will pull in
  170. soundcore and the UML hostaudio relay, which acts as a intermediary
  171. between the host's dsp and mixer devices and the UML sound system.
  172. It is safe to say 'Y' here.
  173. config SOUND
  174. tristate
  175. default UML_SOUND
  176. config HOSTAUDIO
  177. tristate
  178. default UML_SOUND
  179. #It is selected elsewhere, so kconfig would warn without this.
  180. config HW_RANDOM
  181. tristate
  182. default n
  183. config UML_RANDOM
  184. tristate "Hardware random number generator"
  185. help
  186. This option enables UML's "hardware" random number generator. It
  187. attaches itself to the host's /dev/random, supplying as much entropy
  188. as the host has, rather than the small amount the UML gets from its
  189. own drivers. It registers itself as a standard hardware random number
  190. generator, major 10, minor 183, and the canonical device name is
  191. /dev/hwrng.
  192. The way to make use of this is to install the rng-tools package
  193. (check your distro, or download from
  194. http://sourceforge.net/projects/gkernel/). rngd periodically reads
  195. /dev/hwrng and injects the entropy into /dev/random.
  196. config MMAPPER
  197. tristate "iomem emulation driver"
  198. help
  199. This driver allows a host file to be used as emulated IO memory inside
  200. UML.
  201. endmenu