Kconfig 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127
  1. config HVC_DRIVER
  2. bool
  3. help
  4. Generic "hypervisor virtual console" infrastructure for various
  5. hypervisors (pSeries, iSeries, Xen, lguest).
  6. It will automatically be selected if one of the back-end console drivers
  7. is selected.
  8. config HVC_IRQ
  9. bool
  10. config HVC_CONSOLE
  11. bool "pSeries Hypervisor Virtual Console support"
  12. depends on PPC_PSERIES
  13. select HVC_DRIVER
  14. select HVC_IRQ
  15. help
  16. pSeries machines when partitioned support a hypervisor virtual
  17. console. This driver allows each pSeries partition to have a console
  18. which is accessed via the HMC.
  19. config HVC_OLD_HVSI
  20. bool "Old driver for pSeries serial port (/dev/hvsi*)"
  21. depends on HVC_CONSOLE
  22. default n
  23. config HVC_ISERIES
  24. bool "iSeries Hypervisor Virtual Console support"
  25. depends on PPC_ISERIES
  26. default y
  27. select HVC_DRIVER
  28. select HVC_IRQ
  29. select VIOPATH
  30. help
  31. iSeries machines support a hypervisor virtual console.
  32. config HVC_OPAL
  33. bool "OPAL Console support"
  34. depends on PPC_POWERNV
  35. select HVC_DRIVER
  36. select HVC_IRQ
  37. default y
  38. help
  39. PowerNV machines running under OPAL need that driver to get a console
  40. config HVC_RTAS
  41. bool "IBM RTAS Console support"
  42. depends on PPC_RTAS
  43. select HVC_DRIVER
  44. help
  45. IBM Console device driver which makes use of RTAS
  46. config HVC_BEAT
  47. bool "Toshiba's Beat Hypervisor Console support"
  48. depends on PPC_CELLEB
  49. select HVC_DRIVER
  50. help
  51. Toshiba's Cell Reference Set Beat Console device driver
  52. config HVC_IUCV
  53. bool "z/VM IUCV Hypervisor console support (VM only)"
  54. depends on S390
  55. select HVC_DRIVER
  56. select IUCV
  57. default y
  58. help
  59. This driver provides a Hypervisor console (HVC) back-end to access
  60. a Linux (console) terminal via a z/VM IUCV communication path.
  61. config HVC_XEN
  62. bool "Xen Hypervisor Console support"
  63. depends on XEN
  64. select HVC_DRIVER
  65. select HVC_IRQ
  66. default y
  67. help
  68. Xen virtual console device driver
  69. config HVC_XEN_FRONTEND
  70. bool "Xen Hypervisor Multiple Consoles support"
  71. depends on HVC_XEN
  72. select XEN_XENBUS_FRONTEND
  73. default y
  74. help
  75. Xen driver for secondary virtual consoles
  76. config HVC_UDBG
  77. bool "udbg based fake hypervisor console"
  78. depends on PPC && EXPERIMENTAL
  79. select HVC_DRIVER
  80. default n
  81. config HVC_DCC
  82. bool "ARM JTAG DCC console"
  83. depends on ARM
  84. select HVC_DRIVER
  85. help
  86. This console uses the JTAG DCC on ARM to create a console under the HVC
  87. driver. This console is used through a JTAG only on ARM. If you don't have
  88. a JTAG then you probably don't want this option.
  89. config HVC_BFIN_JTAG
  90. bool "Blackfin JTAG console"
  91. depends on BLACKFIN
  92. select HVC_DRIVER
  93. help
  94. This console uses the Blackfin JTAG to create a console under the
  95. the HVC driver. If you don't have JTAG, then you probably don't
  96. want this option.
  97. config HVCS
  98. tristate "IBM Hypervisor Virtual Console Server support"
  99. depends on PPC_PSERIES && HVC_CONSOLE
  100. help
  101. Partitionable IBM Power5 ppc64 machines allow hosting of
  102. firmware virtual consoles from one Linux partition by
  103. another Linux partition. This driver allows console data
  104. from Linux partitions to be accessed through TTY device
  105. interfaces in the device tree of a Linux partition running
  106. this driver.
  107. To compile this driver as a module, choose M here: the
  108. module will be called hvcs. Additionally, this module
  109. will depend on arch specific APIs exported from hvcserver.ko
  110. which will also be compiled when this driver is built as a
  111. module.