diff options
| author | Timur Tabi <timur@freescale.com> | 2011-07-08 19:06:12 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-08-23 10:32:56 -0700 |
| commit | dcd83aaff1c8cbd5b48c152b559e0af3ea1a7b65 (patch) | |
| tree | 536ce3416fd908f0506899b371d86fb21171078c /block | |
| parent | fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c (diff) | |
| download | linux-3.10-dcd83aaff1c8cbd5b48c152b559e0af3ea1a7b65.tar.gz linux-3.10-dcd83aaff1c8cbd5b48c152b559e0af3ea1a7b65.tar.bz2 linux-3.10-dcd83aaff1c8cbd5b48c152b559e0af3ea1a7b65.zip | |
tty/powerpc: introduce the ePAPR embedded hypervisor byte channel driver
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 <timur@freescale.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions