Kconfig 7.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247
  1. config CCW
  2. bool
  3. default y
  4. source "drivers/block/Kconfig"
  5. source "drivers/md/Kconfig"
  6. menu "Character device drivers"
  7. config UNIX98_PTYS
  8. bool "Unix98 PTY support"
  9. ---help---
  10. A pseudo terminal (PTY) is a software device consisting of two
  11. halves: a master and a slave. The slave device behaves identical to
  12. a physical terminal; the master device is used by a process to
  13. read data from and write data to the slave, thereby emulating a
  14. terminal. Typical programs for the master side are telnet servers
  15. and xterms.
  16. Linux has traditionally used the BSD-like names /dev/ptyxx for
  17. masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
  18. has a number of problems. The GNU C library glibc 2.1 and later,
  19. however, supports the Unix98 naming standard: in order to acquire a
  20. pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
  21. terminal is then made available to the process and the pseudo
  22. terminal slave can be accessed as /dev/pts/<number>. What was
  23. traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
  24. The entries in /dev/pts/ are created on the fly by a virtual
  25. file system; therefore, if you say Y here you should say Y to
  26. "/dev/pts file system for Unix98 PTYs" as well.
  27. If you want to say Y here, you need to have the C library glibc 2.1
  28. or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
  29. Read the instructions in <file:Documentation/Changes> pertaining to
  30. pseudo terminals. It's safe to say N.
  31. config UNIX98_PTY_COUNT
  32. int "Maximum number of Unix98 PTYs in use (0-2048)"
  33. depends on UNIX98_PTYS
  34. default "256"
  35. help
  36. The maximum number of Unix98 PTYs that can be used at any one time.
  37. The default is 256, and should be enough for desktop systems. Server
  38. machines which support incoming telnet/rlogin/ssh connections and/or
  39. serve several X terminals may want to increase this: every incoming
  40. connection and every xterm uses up one PTY.
  41. When not in use, each additional set of 256 PTYs occupy
  42. approximately 8 KB of kernel memory on 32-bit architectures.
  43. config HANGCHECK_TIMER
  44. tristate "Hangcheck timer"
  45. help
  46. The hangcheck-timer module detects when the system has gone
  47. out to lunch past a certain margin. It can reboot the system
  48. or merely print a warning.
  49. source "drivers/char/watchdog/Kconfig"
  50. comment "S/390 character device drivers"
  51. config TN3270
  52. tristate "Support for locally attached 3270 terminals"
  53. help
  54. Include support for IBM 3270 terminals.
  55. config TN3270_TTY
  56. tristate "Support for tty input/output on 3270 terminals"
  57. depends on TN3270
  58. help
  59. Include support for using an IBM 3270 terminal as a Linux tty.
  60. config TN3270_FS
  61. tristate "Support for fullscreen applications on 3270 terminals"
  62. depends on TN3270
  63. help
  64. Include support for fullscreen applications on an IBM 3270 terminal.
  65. config TN3270_CONSOLE
  66. bool "Support for console on 3270 terminal"
  67. depends on TN3270=y && TN3270_TTY=y
  68. help
  69. Include support for using an IBM 3270 terminal as a Linux system
  70. console. Available only if 3270 support is compiled in statically.
  71. config TN3215
  72. bool "Support for 3215 line mode terminal"
  73. help
  74. Include support for IBM 3215 line-mode terminals.
  75. config TN3215_CONSOLE
  76. bool "Support for console on 3215 line mode terminal"
  77. depends on TN3215
  78. help
  79. Include support for using an IBM 3215 line-mode terminal as a
  80. Linux system console.
  81. config CCW_CONSOLE
  82. bool
  83. depends on TN3215_CONSOLE || TN3270_CONSOLE
  84. default y
  85. config SCLP
  86. bool "Support for SCLP"
  87. help
  88. Include support for the SCLP interface to the service element.
  89. config SCLP_TTY
  90. bool "Support for SCLP line mode terminal"
  91. depends on SCLP
  92. help
  93. Include support for IBM SCLP line-mode terminals.
  94. config SCLP_CONSOLE
  95. bool "Support for console on SCLP line mode terminal"
  96. depends on SCLP_TTY
  97. help
  98. Include support for using an IBM HWC line-mode terminal as the Linux
  99. system console.
  100. config SCLP_VT220_TTY
  101. bool "Support for SCLP VT220-compatible terminal"
  102. depends on SCLP
  103. help
  104. Include support for an IBM SCLP VT220-compatible terminal.
  105. config SCLP_VT220_CONSOLE
  106. bool "Support for console on SCLP VT220-compatible terminal"
  107. depends on SCLP_VT220_TTY
  108. help
  109. Include support for using an IBM SCLP VT220-compatible terminal as a
  110. Linux system console.
  111. config SCLP_CPI
  112. tristate "Control-Program Identification"
  113. depends on SCLP
  114. help
  115. This option enables the hardware console interface for system
  116. identification. This is commonly used for workload management and
  117. gives you a nice name for the system on the service element.
  118. Please select this option as a module since built-in operation is
  119. completely untested.
  120. You should only select this option if you know what you are doing,
  121. need this feature and intend to run your kernel in LPAR.
  122. config S390_TAPE
  123. tristate "S/390 tape device support"
  124. help
  125. Select this option if you want to access channel-attached tape
  126. devices on IBM S/390 or zSeries.
  127. If you select this option you will also want to select at
  128. least one of the tape interface options and one of the tape
  129. hardware options in order to access a tape device.
  130. This option is also available as a module. The module will be
  131. called tape390 and include all selected interfaces and
  132. hardware drivers.
  133. comment "S/390 tape interface support"
  134. depends on S390_TAPE
  135. config S390_TAPE_BLOCK
  136. bool "Support for tape block devices"
  137. depends on S390_TAPE
  138. help
  139. Select this option if you want to access your channel-attached tape
  140. devices using the block device interface. This interface is similar
  141. to CD-ROM devices on other platforms. The tapes can only be
  142. accessed read-only when using this interface. Have a look at
  143. <file:Documentation/s390/TAPE> for further information about creating
  144. volumes for and using this interface. It is safe to say "Y" here.
  145. comment "S/390 tape hardware support"
  146. depends on S390_TAPE
  147. config S390_TAPE_34XX
  148. tristate "Support for 3480/3490 tape hardware"
  149. depends on S390_TAPE
  150. help
  151. Select this option if you want to access IBM 3480/3490 magnetic
  152. tape subsystems and 100% compatibles.
  153. It is safe to say "Y" here.
  154. config S390_TAPE_3590
  155. tristate "Support for 3590 tape hardware"
  156. depends on S390_TAPE
  157. help
  158. Select this option if you want to access IBM 3590 magnetic
  159. tape subsystems and 100% compatibles.
  160. It is safe to say "Y" here.
  161. config VMLOGRDR
  162. tristate "Support for the z/VM recording system services (VM only)"
  163. depends on IUCV
  164. help
  165. Select this option if you want to be able to receive records collected
  166. by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
  167. *SYMPTOM.
  168. This driver depends on the IUCV support driver.
  169. config VMCP
  170. tristate "Support for the z/VM CP interface (VM only)"
  171. help
  172. Select this option if you want to be able to interact with the control
  173. program on z/VM
  174. config MONREADER
  175. tristate "API for reading z/VM monitor service records"
  176. depends on IUCV
  177. help
  178. Character device driver for reading z/VM monitor service records
  179. config MONWRITER
  180. tristate "API for writing z/VM monitor service records"
  181. default "m"
  182. help
  183. Character device driver for writing z/VM monitor service records
  184. endmenu
  185. menu "Cryptographic devices"
  186. config ZCRYPT
  187. tristate "Support for PCI-attached cryptographic adapters"
  188. select ZCRYPT_MONOLITHIC if ZCRYPT="y"
  189. default "m"
  190. help
  191. Select this option if you want to use a PCI-attached cryptographic
  192. adapter like:
  193. + PCI Cryptographic Accelerator (PCICA)
  194. + PCI Cryptographic Coprocessor (PCICC)
  195. + PCI-X Cryptographic Coprocessor (PCIXCC)
  196. + Crypto Express2 Coprocessor (CEX2C)
  197. + Crypto Express2 Accelerator (CEX2A)
  198. config ZCRYPT_MONOLITHIC
  199. bool "Monolithic zcrypt module"
  200. depends on ZCRYPT="m"
  201. help
  202. Select this option if you want to have a single module z90crypt.ko
  203. that contains all parts of the crypto device driver (ap bus,
  204. request router and all the card drivers).
  205. endmenu