Kconfig 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  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_ISERIES
  20. bool "iSeries Hypervisor Virtual Console support"
  21. depends on PPC_ISERIES
  22. default y
  23. select HVC_DRIVER
  24. select HVC_IRQ
  25. select VIOPATH
  26. help
  27. iSeries machines support a hypervisor virtual console.
  28. config HVC_RTAS
  29. bool "IBM RTAS Console support"
  30. depends on PPC_RTAS
  31. select HVC_DRIVER
  32. help
  33. IBM Console device driver which makes use of RTAS
  34. config HVC_BEAT
  35. bool "Toshiba's Beat Hypervisor Console support"
  36. depends on PPC_CELLEB
  37. select HVC_DRIVER
  38. help
  39. Toshiba's Cell Reference Set Beat Console device driver
  40. config HVC_IUCV
  41. bool "z/VM IUCV Hypervisor console support (VM only)"
  42. depends on S390
  43. select HVC_DRIVER
  44. select IUCV
  45. default y
  46. help
  47. This driver provides a Hypervisor console (HVC) back-end to access
  48. a Linux (console) terminal via a z/VM IUCV communication path.
  49. config HVC_XEN
  50. bool "Xen Hypervisor Console support"
  51. depends on XEN
  52. select HVC_DRIVER
  53. select HVC_IRQ
  54. default y
  55. help
  56. Xen virtual console device driver
  57. config HVC_UDBG
  58. bool "udbg based fake hypervisor console"
  59. depends on PPC && EXPERIMENTAL
  60. select HVC_DRIVER
  61. default n
  62. config HVC_DCC
  63. bool "ARM JTAG DCC console"
  64. depends on ARM
  65. select HVC_DRIVER
  66. help
  67. This console uses the JTAG DCC on ARM to create a console under the HVC
  68. driver. This console is used through a JTAG only on ARM. If you don't have
  69. a JTAG then you probably don't want this option.
  70. config HVC_BFIN_JTAG
  71. bool "Blackfin JTAG console"
  72. depends on BLACKFIN
  73. select HVC_DRIVER
  74. help
  75. This console uses the Blackfin JTAG to create a console under the
  76. the HVC driver. If you don't have JTAG, then you probably don't
  77. want this option.
  78. config HVCS
  79. tristate "IBM Hypervisor Virtual Console Server support"
  80. depends on PPC_PSERIES && HVC_CONSOLE
  81. help
  82. Partitionable IBM Power5 ppc64 machines allow hosting of
  83. firmware virtual consoles from one Linux partition by
  84. another Linux partition. This driver allows console data
  85. from Linux partitions to be accessed through TTY device
  86. interfaces in the device tree of a Linux partition running
  87. this driver.
  88. To compile this driver as a module, choose M here: the
  89. module will be called hvcs. Additionally, this module
  90. will depend on arch specific APIs exported from hvcserver.ko
  91. which will also be compiled when this driver is built as a
  92. module.