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 "iSeries Hypervisor Virtual Console support"
24 depends on PPC_ISERIES
30 iSeries machines support a hypervisor virtual console.
33 bool "IBM RTAS Console support"
37 IBM Console device driver which makes use of RTAS
40 bool "Toshiba's Beat Hypervisor Console support"
44 Toshiba's Cell Reference Set Beat Console device driver
47 bool "z/VM IUCV Hypervisor console support (VM only)"
53 This driver provides a Hypervisor console (HVC) back-end to access
54 a Linux (console) terminal via a z/VM IUCV communication path.
57 bool "Xen Hypervisor Console support"
63 Xen virtual console device driver
66 bool "udbg based fake hypervisor console"
67 depends on PPC && EXPERIMENTAL
72 bool "ARM JTAG DCC console"
76 This console uses the JTAG DCC on ARM to create a console under the HVC
77 driver. This console is used through a JTAG only on ARM. If you don't have
78 a JTAG then you probably don't want this option.
81 bool "Blackfin JTAG console"
85 This console uses the Blackfin JTAG to create a console under the
86 the HVC driver. If you don't have JTAG, then you probably don't
90 tristate "IBM Hypervisor Virtual Console Server support"
91 depends on PPC_PSERIES && HVC_CONSOLE
93 Partitionable IBM Power5 ppc64 machines allow hosting of
94 firmware virtual consoles from one Linux partition by
95 another Linux partition. This driver allows console data
96 from Linux partitions to be accessed through TTY device
97 interfaces in the device tree of a Linux partition running
100 To compile this driver as a module, choose M here: the
101 module will be called hvcs. Additionally, this module
102 will depend on arch specific APIs exported from hvcserver.ko
103 which will also be compiled when this driver is built as a