1config 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
  9config HVC_IRQ
 10	bool
 11
 12config HVC_CONSOLE
 13	bool "pSeries Hypervisor Virtual Console support"
 14	depends on PPC_PSERIES
 15	select HVC_DRIVER
 16	select HVC_IRQ
 17	help
 18	  pSeries machines when partitioned support a hypervisor virtual
 19	  console. This driver allows each pSeries partition to have a console
 20	  which is accessed via the HMC.
 21
 22config HVC_OLD_HVSI
 23	bool "Old driver for pSeries serial port (/dev/hvsi*)"
 24	depends on HVC_CONSOLE
 25	default n
 26
 27config HVC_OPAL
 28	bool "OPAL Console support"
 29	depends on PPC_POWERNV
 30	select HVC_DRIVER
 31	select HVC_IRQ
 32	default y
 33	help
 34	  PowerNV machines running under OPAL need that driver to get a console
 35
 36config HVC_RTAS
 37	bool "IBM RTAS Console support"
 38	depends on PPC_RTAS
 39	select HVC_DRIVER
 40	help
 41	  IBM Console device driver which makes use of RTAS
 42
 43config HVC_BEAT
 44	bool "Toshiba's Beat Hypervisor Console support"
 45	depends on PPC_CELLEB
 46	select HVC_DRIVER
 47	help
 48	  Toshiba's Cell Reference Set Beat Console device driver
 49
 50config HVC_IUCV
 51	bool "z/VM IUCV Hypervisor console support (VM only)"
 52	depends on S390
 53	select HVC_DRIVER
 54	select IUCV
 55	default y
 56	help
 57	  This driver provides a Hypervisor console (HVC) back-end to access
 58	  a Linux (console) terminal via a z/VM IUCV communication path.
 59
 60config HVC_XEN
 61	bool "Xen Hypervisor Console support"
 62	depends on XEN
 63	select HVC_DRIVER
 64	select HVC_IRQ
 65	default y
 66	help
 67	  Xen virtual console device driver
 68
 69config 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
 77config HVC_UDBG
 78       bool "udbg based fake hypervisor console"
 79       depends on PPC && EXPERIMENTAL
 80       select HVC_DRIVER
 81       default n
 82       help
 83         This is meant to be used during HW bring up or debugging when
 84	 no other console mechanism exist but udbg, to get you a quick
 85	 console for userspace. Do NOT enable in production kernels. 
 86
 87config HVC_DCC
 88       bool "ARM JTAG DCC console"
 89       depends on ARM
 90       select HVC_DRIVER
 91       help
 92         This console uses the JTAG DCC on ARM to create a console under the HVC
 93	 driver. This console is used through a JTAG only on ARM. If you don't have
 94	 a JTAG then you probably don't want this option.
 95
 96config HVC_BFIN_JTAG
 97	bool "Blackfin JTAG console"
 98	depends on BLACKFIN
 99	select HVC_DRIVER
100	help
101	 This console uses the Blackfin JTAG to create a console under the
102	 the HVC driver.  If you don't have JTAG, then you probably don't
103	 want this option.
104
105config HVCS
106	tristate "IBM Hypervisor Virtual Console Server support"
107	depends on PPC_PSERIES && HVC_CONSOLE
108	help
109	  Partitionable IBM Power5 ppc64 machines allow hosting of
110	  firmware virtual consoles from one Linux partition by
111	  another Linux partition.  This driver allows console data
112	  from Linux partitions to be accessed through TTY device
113	  interfaces in the device tree of a Linux partition running
114	  this driver.
115
116	  To compile this driver as a module, choose M here: the
117	  module will be called hvcs.  Additionally, this module
118	  will depend on arch specific APIs exported from hvcserver.ko
119	  which will also be compiled when this driver is built as a
120	  module.
121