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
13 bool "pSeries Hypervisor Virtual Console support"
14 depends on PPC_PSERIES
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.
23 bool "Old driver for pSeries serial port (/dev/hvsi*)"
24 depends on HVC_CONSOLE
28 bool "iSeries Hypervisor Virtual Console support"
29 depends on PPC_ISERIES
35 iSeries machines support a hypervisor virtual console.
38 bool "IBM RTAS Console support"
42 IBM Console device driver which makes use of RTAS
45 bool "Toshiba's Beat Hypervisor Console support"
49 Toshiba's Cell Reference Set Beat Console device driver
52 bool "z/VM IUCV Hypervisor console support (VM only)"
58 This driver provides a Hypervisor console (HVC) back-end to access
59 a Linux (console) terminal via a z/VM IUCV communication path.
62 bool "Xen Hypervisor Console support"
68 Xen virtual console device driver
71 bool "udbg based fake hypervisor console"
72 depends on PPC && EXPERIMENTAL
77 bool "ARM JTAG DCC console"
81 This console uses the JTAG DCC on ARM to create a console under the HVC
82 driver. This console is used through a JTAG only on ARM. If you don't have
83 a JTAG then you probably don't want this option.
86 bool "Blackfin JTAG console"
90 This console uses the Blackfin JTAG to create a console under the
91 the HVC driver. If you don't have JTAG, then you probably don't
95 tristate "IBM Hypervisor Virtual Console Server support"
96 depends on PPC_PSERIES && HVC_CONSOLE
98 Partitionable IBM Power5 ppc64 machines allow hosting of
99 firmware virtual consoles from one Linux partition by
100 another Linux partition. This driver allows console data
101 from Linux partitions to be accessed through TTY device
102 interfaces in the device tree of a Linux partition running
105 To compile this driver as a module, choose M here: the
106 module will be called hvcs. Additionally, this module
107 will depend on arch specific APIs exported from hvcserver.ko
108 which will also be compiled when this driver is built as a