linux.git/drivers/char/vt_ioctl.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

drivers/char/vt_ioctl.c: fix VT_OPENQRY error value

2010-10-28T01:03:05+00:00

When all VT's are in use, VT_OPENQRY casts -1 to unsigned char before
returning it to userspace as an int.  VT255 is not the next available
console.

Signed-off-by: Graham Gower 
Cc: Greg KH 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Input: use PIT_TICK_RATE in vt beep ioctl

2010-08-29T04:39:09+00:00

The KIOCSOUND and KDMKTONE ioctls are based on the CLOCK_TICK_RATE,
which is architecture and sometimes configuration specific.

In practice, most user applications assume that it is actually defined
as the i8253 PIT base clock of 1193182 Hz, which is true on some
architectures but not on others.

This patch makes the vt code use the PIT frequency on all
architectures, which is much more well-defined.  It will change the
behavior of user applications sending the beep ioctl on all
architectures that define CLOCK_TICK_RATE different from
PIT_TICK_RATE.

The original breakage was introduced in commit bcc8ca099 "Adapt
drivers/char/vt_ioctl.c to non-x86".  Hopefully, reverting this change
will make the frequency correct in more cases than it will make it
incorrect.

Signed-off-by: Arnd Bergmann 
Acked-by: Alan Cox 
Signed-off-by: Dmitry Torokhov

tty: introduce wait_event_interruptible_tty

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

Calling wait_event_interruptible implicitly
releases the BKL when it sleeps, but we need
to do this explcitly when we have converted
it to a mutex.

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

tty: replace BKL with a new tty_lock

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

As a preparation for replacing the big kernel lock
in the TTY layer, wrap all the callers in new
macros tty_lock, tty_lock_nested and tty_unlock.

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

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

vt_ioctl: return -EFAULT on copy_from_user errors

2010-06-04T20:37:18+00:00

copy_from_user() returns the number of bytes remaining but we want to
return a negative error code here.

Signed-off-by: Dan Carpenter 
Signed-off-by: Greg Kroah-Hartman

Revert "tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call"

2010-03-19T14:17:52+00:00

This reverts commit eec9fe7d1ab4a0dfac4cb43047a7657fffd0002f.

Ari writes as the reason this should be reverted:
	The problems with this patch include:
	1. There's at least one subtlety I overlooked - switching
	between X servers (i.e. from one X VT to another) still requires
	the cooperation of both X servers. I was assuming that KMS
	eliminated this.
	2. It hasn't been tested at all (no X server patch exists which
	uses the new mode).

As he was the original author of the patch, I'll revert it.

Cc: Ari Entlich 
Cc: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

tty: Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call

2010-03-02T22:43:23+00:00

This new VT mode (VT_PROCESS_AUTO) does everything that VT_PROCESS does
except that it doesn't wait for a VT_RELDISP ioctl before switching
away from a VT with that mode.

If the X server eventually uses this new mode, debugging and crash
recovery should become easier. This is because even when currently in
the VT of a frozen X server it would still be possible to switch out
by doing SysRq-r and then CTRL-, sshing in and
doing chvt , or any other method of VT switching.
The general concensus on #xorg-devel seems to be that it should be
safe to use this with X now that we have KMS.

This also moves the VT_ACKACQ define to a more appropriate place,
for clarity's sake.

Signed-off-by: Ari Entlich 
Acked-by: Alan Cox 
Signed-off-by: Greg Kroah-Hartman

vt: Fix use of "new" in a struct field

2009-11-19T21:43:06+00:00

As this struct is exposed to user space and the API was added for this
release it's a bit of a pain for the C++ world and we still have time to
fix it. Rename the fields before we end up with that pain in an actual
release.

Signed-off-by: Alan Cox 
Reported-by: Olivier Goffart
Signed-off-by: Linus Torvalds