Kconfig 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166
  1. comment "S/390 character device drivers"
  2. depends on S390
  3. config TN3270
  4. tristate "Support for locally attached 3270 terminals"
  5. depends on CCW
  6. help
  7. Include support for IBM 3270 terminals.
  8. config TN3270_TTY
  9. tristate "Support for tty input/output on 3270 terminals"
  10. depends on TN3270
  11. help
  12. Include support for using an IBM 3270 terminal as a Linux tty.
  13. config TN3270_FS
  14. tristate "Support for fullscreen applications on 3270 terminals"
  15. depends on TN3270
  16. help
  17. Include support for fullscreen applications on an IBM 3270 terminal.
  18. config TN3270_CONSOLE
  19. bool "Support for console on 3270 terminal"
  20. depends on TN3270=y && TN3270_TTY=y
  21. help
  22. Include support for using an IBM 3270 terminal as a Linux system
  23. console. Available only if 3270 support is compiled in statically.
  24. config TN3215
  25. bool "Support for 3215 line mode terminal"
  26. depends on CCW
  27. help
  28. Include support for IBM 3215 line-mode terminals.
  29. config TN3215_CONSOLE
  30. bool "Support for console on 3215 line mode terminal"
  31. depends on TN3215
  32. help
  33. Include support for using an IBM 3215 line-mode terminal as a
  34. Linux system console.
  35. config CCW_CONSOLE
  36. bool
  37. depends on TN3215_CONSOLE || TN3270_CONSOLE
  38. default y
  39. config SCLP
  40. bool "Support for SCLP"
  41. depends on S390
  42. help
  43. Include support for the SCLP interface to the service element.
  44. config SCLP_TTY
  45. bool "Support for SCLP line mode terminal"
  46. depends on SCLP
  47. help
  48. Include support for IBM SCLP line-mode terminals.
  49. config SCLP_CONSOLE
  50. bool "Support for console on SCLP line mode terminal"
  51. depends on SCLP_TTY
  52. help
  53. Include support for using an IBM HWC line-mode terminal as the Linux
  54. system console.
  55. config SCLP_VT220_TTY
  56. bool "Support for SCLP VT220-compatible terminal"
  57. depends on SCLP
  58. help
  59. Include support for an IBM SCLP VT220-compatible terminal.
  60. config SCLP_VT220_CONSOLE
  61. bool "Support for console on SCLP VT220-compatible terminal"
  62. depends on SCLP_VT220_TTY
  63. help
  64. Include support for using an IBM SCLP VT220-compatible terminal as a
  65. Linux system console.
  66. config SCLP_CPI
  67. tristate "Control-Program Identification"
  68. depends on SCLP
  69. help
  70. This option enables the hardware console interface for system
  71. identification. This is commonly used for workload management and
  72. gives you a nice name for the system on the service element.
  73. Please select this option as a module since built-in operation is
  74. completely untested.
  75. You should only select this option if you know what you are doing,
  76. need this feature and intend to run your kernel in LPAR.
  77. config S390_TAPE
  78. tristate "S/390 tape device support"
  79. depends on CCW
  80. help
  81. Select this option if you want to access channel-attached tape
  82. devices on IBM S/390 or zSeries.
  83. If you select this option you will also want to select at
  84. least one of the tape interface options and one of the tape
  85. hardware options in order to access a tape device.
  86. This option is also available as a module. The module will be
  87. called tape390 and include all selected interfaces and
  88. hardware drivers.
  89. comment "S/390 tape interface support"
  90. depends on S390_TAPE
  91. config S390_TAPE_BLOCK
  92. bool "Support for tape block devices"
  93. depends on S390_TAPE
  94. help
  95. Select this option if you want to access your channel-attached tape
  96. devices using the block device interface. This interface is similar
  97. to CD-ROM devices on other platforms. The tapes can only be
  98. accessed read-only when using this interface. Have a look at
  99. <file:Documentation/s390/TAPE> for further information about creating
  100. volumes for and using this interface. It is safe to say "Y" here.
  101. comment "S/390 tape hardware support"
  102. depends on S390_TAPE
  103. config S390_TAPE_34XX
  104. tristate "Support for 3480/3490 tape hardware"
  105. depends on S390_TAPE
  106. help
  107. Select this option if you want to access IBM 3480/3490 magnetic
  108. tape subsystems and 100% compatibles.
  109. It is safe to say "Y" here.
  110. config S390_TAPE_3590
  111. tristate "Support for 3590 tape hardware"
  112. depends on S390_TAPE
  113. help
  114. Select this option if you want to access IBM 3590 magnetic
  115. tape subsystems and 100% compatibles.
  116. It is safe to say "Y" here.
  117. config VMLOGRDR
  118. tristate "Support for the z/VM recording system services (VM only)"
  119. depends on IUCV
  120. help
  121. Select this option if you want to be able to receive records collected
  122. by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
  123. *SYMPTOM.
  124. This driver depends on the IUCV support driver.
  125. config VMCP
  126. tristate "Support for the z/VM CP interface (VM only)"
  127. depends on S390
  128. help
  129. Select this option if you want to be able to interact with the control
  130. program on z/VM
  131. config MONREADER
  132. tristate "API for reading z/VM monitor service records"
  133. depends on IUCV
  134. help
  135. Character device driver for reading z/VM monitor service records
  136. config MONWRITER
  137. tristate "API for writing z/VM monitor service records"
  138. depends on S390
  139. default "m"
  140. help
  141. Character device driver for writing z/VM monitor service records