linux.git/drivers/char/Makefile, branch v2.6.38

virtio: console: Move file back to drivers/char/

2011-02-03T22:43:12+00:00

Commit 728674a7e466628df2aeec6d11a2ae1ef968fb67 moved virtio_console.c
to drivers/tty/hvc/ under the perception of this being an hvc driver.
It was such once, but these days it has generic communication
capabilities as well, so move it to drivers/char/.

In the future, the hvc part from this file can be split off and moved
under drivers/tty/hvc/.

Signed-off-by: Amit Shah 
CC: Rusty Russell 
Acked-by: Arnd Bergmann 
Signed-off-by: Greg Kroah-Hartman

tty: move hvc drivers to drivers/tty/hvc/

2011-01-13T20:03:00+00:00

As requested by Arnd Bergmann, the hvc drivers are now
moved to the drivers/tty/hvc/ directory.  The virtio_console.c driver
was also moved, as it required the hvc_console.h file to be able to be
built, and it really is a hvc driver.

Cc: Arnd Bergmann 
Signed-off-by: Greg Kroah-Hartman

cs5535: deprecate older cs5535_gpio driver

2011-01-13T16:03:13+00:00

The newer drivers/gpio/cs5535-gpio.c replaces drivers/misc/cs5535_gpio.c.
The new driver has been in the tree for a little while, and has received
some testing; it's time to mark the old one as deprecated.  I'm thinking
removal around 2.6.40 would be good, provided we're not missing critical
functionality in the newer driver.

Signed-off-by: Andres Salomon 
Cc: Daniel Drake 
Acked-by: Ben Gardner 
Cc: Greg KH 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drivers: char: hvc: add arm JTAG DCC console support

2010-12-01T01:27:13+00:00

This driver adds a basic console that uses the arm JTAG
DCC to transfer data back and forth. It has support for
ARMv6 and ARMv7.

This console is created under the HVC driver, and should be named
/dev/hvcX (or /dev/hvc0 for example).

Cc: Tony Lindgren 
Acked-by: Arnd Bergmann 
Acked-by: Nicolas Pitre 
Cc: Mike Frysinger 
Signed-off-by: Daniel Walker 
Signed-off-by: Greg Kroah-Hartman

TTY: create drivers/tty/vt and move the vt code there

2010-11-05T15:16:52+00:00

The vt and other related code is moved into the drivers/tty/vt directory.

Acked-by: Arnd Bergmann 
Cc: Jiri Slaby 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

TTY: create drivers/tty and move the tty core files there

2010-11-05T15:10:33+00:00

The tty code should be in its own subdirectory and not in the char
driver with all of the cruft that is currently there.

Based on work done by Arnd Bergmann 

Acked-by: Arnd Bergmann 
Cc: Jiri Slaby 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

add ttyprintk driver

2010-10-22T17:20:02+00:00

Ttyprintk is a pseudo TTY driver, which allows users to make printk
messages, via output to ttyprintk device. It is possible to store
"console" messages inline with kernel messages for better analyses of
the boot process, for example.

Signed-off-by: Samo Pogacnik 
Acked-by: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

tty: implement BTM as mutex instead of BKL

2010-08-10T20:47:44+00:00

The tty locking now follows the rules for mutexes, so
we can replace the BKL usage with a new subsystem
wide mutex.

Using a regular mutex here will change the behaviour
when blocked on the BTM from spinning to sleeping,
but that should not be visible to the user.

Using the mutex also means that all the BTM is now
covered by lockdep.

Signed-off-by: Arnd Bergmann 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

arch/tile: core support for Tilera 32-bit chips.

2010-06-04T21:11:18+00:00

This change is the core kernel support for TILEPro and TILE64 chips.
No driver support (except the console driver) is included yet.

This includes the relevant Linux headers in asm/; the low-level
low-level "Tile architecture" headers in arch/, which are
shared with the hypervisor, etc., and are build-system agnostic;
and the relevant hypervisor headers in hv/.

Signed-off-by: Chris Metcalf 
Acked-by: Arnd Bergmann 
Acked-by: FUJITA Tomonori 
Reviewed-by: Paul Mundt

char drivers: RAM oops/panic logger

2010-05-27T16:12:50+00:00

Ramoops, like mtdoops, can log oops/panic information but in RAM.  It can
be used with persistent RAM for systems without flash support.  In
addition, for this systems, with this driver, it's no more needed add to
the kernel the mtd subsystem with advantage in footprint.

It can be used in a very easy way with persistent RAM for systems without
flash support.  For these systems, with this driver, it is no longer
required to cinlude mtd subsystem with an advantage in footprint.  In
addition, you can save flash space and store this information only in RAM.

Signed-off-by: Marco Stornelli 
Cc: Simon Kagstrom 
Cc: David Woodhouse 
Cc; Anders Grafstrom 
Cc: Yuasa Yoichi 
Cc: Jamie Lokier 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds