linux.git/drivers/char/vt.c, branch master

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

vcs: invoke the vt update callback when /dev/vcs* is written to

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

A notifier chain is called whenever the vt code modifies a terminal
content, except for one case which is when the modification comes
through writes to /dev/vcs* devices.  Let's add the missing notifier
invocation at the end of vcs_write() for that case too.

Signed-off-by: Nicolas Pitre 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

vt: Fix console corruption on driver hand-over.

2010-09-04T00:29:03+00:00

After 02f0777a0d6560eb995aade34a1b82f95c0452da "vc_origin" is no
longer reset to the screen buffer before calling the con_init() hook
of the new console driver.

If the old driver wasn't using a fixed scanout buffer (e.g. the case
of vgacon) "vc_origin" may be a pointer to a VRAM location, and its
contents aren't guaranteed to be preserved after calling con_deinit()
on the old driver and con_init() on the new driver, i.e. the
subsequent console resize may fill the framebuffer with garbage.

It can be reproduced in the transition from vgacon to the nouveau
framebuffer driver: in that case the legacy VGA aperture "vc_origin"
points to becomes unreadable after fbcon_init().

This patch reverts the mentioned commit. To avoid the problem it
intended to fix, stop using "vc_scr_end" in vc_do_resize() to
calculate how many rows we have to copy (actually the code looks
simpler this way without the help of "vc_scr_end").

Signed-off-by: Francisco Jerez 
Cc: qiaochong 
Cc: Greg Kroah-Hartman 
Cc: Andrew Morton 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

vt,console,kdb: preserve console_blanked while in kdb

2010-08-16T20:58:31+00:00

Commit b45cfba4e9005d64d419718e7ff7f7cab44c1994 (vt,console,kdb:
implement atomic console enter/leave functions) introduced the ability
to atomically change the console mode with kernel mode setting but did
not preserve the state of the console_blanked variable.

The console_blanked variable must be restored when executing the
con_debug_leave() or further kernel mode set changes (such as using
chvt X) will fail to correctly set the state of console.

Signed-off-by: Jason Wessel 
Reviewed-by: Jesse Barnes 
CC: Andrew Morton

vt: fix regression warnings from KMS merge

2010-08-16T20:58:30+00:00

Fix the following new sparse warnings in vt.c introduced by the commit
b45cfba4e9005d64d419718e7ff7f7cab44c1994 (vt,console,kdb: implement
atomic console enter/leave functions):

drivers/char/vt.c:197:5: warning: symbol 'saved_fg_console' was not declared. Should it be static?
drivers/char/vt.c:198:5: warning: symbol 'saved_last_console' was not declared. Should it be static?
drivers/char/vt.c:199:5: warning: symbol 'saved_want_console' was not declared. Should it be static?
drivers/char/vt.c:200:5: warning: symbol 'saved_vc_mode' was not declared. Should it be static?

Signed-off-by: Jason Wessel 
Reviewed-by: Jesse Barnes 
CC: Andrew Morton

tty: Move the vt_tty field from the vc_data into the standard tty_port

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

This takes all the tty references through the expected interface points so
we can refcount them.

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

tty: Make vt's have a tty_port

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

The vt layer isn't safely handling reference counts to tty object on the input
side. Add a tty port structure to the vt layer in order to implement this using
the standard helpers.

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

vc: Locking clean up

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

The virtual console layer uses the BKL for various things that don't really
need it. Clean them out.

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

vt/console: try harder to print output when panicing

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

Jesse's initial patch commit said:

"At panic time (i.e.  when oops_in_progress is set) we should try a bit
harder to update the screen and make sure output gets to the VT, since
some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a
panic context."

I've enhanced this to add a flag to the vc that console layer can set to
indicate they want this behaviour to occur.  This also adds support to
fbcon for that flag and adds an fb flag for drivers to indicate they want
to use the support.  It enables this for KMS drivers.

Signed-off-by: Dave Airlie 
Signed-off-by: Jesse Barnes 
Acked-by: James Simmons 
Cc: Alan Cox 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

vt: clean up the code - use kernel library

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

Signed-off-by: Andy Shevchenko 
Cc: Andrew Morton 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman