27 Sep, 2011
1 commit
-
The ePAPR hypervisor byte channel console driver only supports one byte
channel as a console, and the byte channel handle is stored in a global
variable. It doesn't make any sense to pass that handle as a parameter
to the console functions, since these functions already have access to the
global variable.Signed-off-by: Timur Tabi
Signed-off-by: Greg Kroah-Hartman
27 Aug, 2011
1 commit
-
The ePAPR hypervisor byte channel driver is supposed to work on all
ePAPR-compliant embedded PowerPC systems, but it had a reference to the MSR_GS
bit, which is available only on Book-E systems.Also fix a couple integer-to-pointer typecast problems.
Reported-by: Stephen Rothwell
Signed-off-by: Timur Tabi
Signed-off-by: Greg Kroah-Hartman
24 Aug, 2011
1 commit
-
The ePAPR embedded hypervisor specification provides an API for "byte
channels", which are serial-like virtual devices for sending and receiving
streams of bytes. This driver provides Linux kernel support for byte
channels via three distinct interfaces:1) An early-console (udbg) driver. This provides early console output
through a byte channel. The byte channel handle must be specified in a
Kconfig option.2) A normal console driver. Output is sent to the byte channel designated
for stdout in the device tree. The console driver is for handling kernel
printk calls.3) A tty driver, which is used to handle user-space input and output. The
byte channel used for the console is designated as the default tty.Signed-off-by: Timur Tabi
Signed-off-by: Greg Kroah-Hartman